McKesson Shares Rally 1.19% as Revised Healthcare Pact Boosts Institutional Bets and Retail Frenzy Propel Stock to 230th in U.S. Trading Volume

On October 7, 2025, McKesson (MCK) closed with a 1.19% gain, trading on a volume of $0.49 billion, ranking 230th in daily trading activity across U.S. equities. The move followed a surge in institutional interest linked to a revised distribution contract with a major healthcare provider, which analysts noted could expand the company’s mid-term revenue visibility. Short-term momentum was further bolstered by a 15% increase in retail investor participation, as reflected in elevated options activity and retail trading platform data.

Market observers highlighted the stock’s resilience despite broader sector underperformance, attributing the divergence to positive earnings guidance from a key pharmacy benefit manager client. This development offset concerns over rising inventory costs in the pharmaceutical supply chain. However, volatility remained elevated as algorithmic trading patterns indicated mixed sentiment, with momentum strategies rotating in and out of the position throughout the session.

To run a proper back-test we need to pin down a few implementation details that aren’t fully specified yet: 1. Market universe • Should we limit ourselves to U.S.-listed equities only? • If so, do we include ETFs, ADRs, penny stocks, etc.? 2. “Top 500 by daily trading volume” • Do you want to rank by share volume or by dollar turnover (volume × price)? • Is the ranking re-balanced every trading day at the day’s close and the portfolio entered at the next day’s open (and then exited at the next day’s close)? 3. Transaction assumptions • Commissions / bid-ask slippage: ignore, fixed per share, or a % of notional? 4. Execution details • Equal-weight each of the 500 names? • Any capacity or liquidity constraint (e.g., cap each position at X % of that day’s dollar volume)? Our back-testing engine currently handles one ticker at a time, so to emulate a 500-stock, daily-turnover portfolio we’ll have to aggregate individual security results into a composite. That’s doable, but it’s computationally intensive, so confirming the points above will help keep the run-time and data pulls reasonable. Once we lock these parameters in, I can generate the data-retrieval plan and kick off the back-test automatically.