How a Backtest Engine May Handle Stocks After Delisting

Summary

The post raises a backtesting concern: a user observes that a stock delisted on one date still appears sellable on a later scheduled rebalance date. A reply explains the platform behavior as a special backtest-engine rule: when a strategy does not handle a delisted holding itself, the engine automatically sells it on the delisting date, preventing the account from retaining the position indefinitely.

This is a narrow explanation of platform mechanics, not a general account of delisting economics or a strategy. The example and reply illustrate why apparent post-delisting trades may reflect engine-level handling rather than a feasible market transaction. The post does not document the engine’s exact pricing assumptions, treatment of proceeds, or behavior across different delisting scenarios. Researchers should therefore consult platform specifications and inspect event handling when evaluating results that involve delisted securities; this note alone does not establish how other backtesting systems behave.

Key ideas

• The post describes a platform rule that automatically closes holdings on a stock's delisting date.
• The stated purpose is to prevent a simulated account from holding a delisted stock indefinitely.
• A displayed sale may result from backtest-engine handling rather than an ordinary market transaction.
• The post does not specify execution pricing or how other engines handle delistings.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.