Infosys Dips to 500th in U.S. Trading Volume Amid Tech Sector Weakness

On October 10, 2025, Infosys (INFY) closed with a 2.81% decline, marking its weakest performance in recent weeks. Trading volume dropped 29.7% to $250 million, ranking the stock 500th in market activity across U.S. exchanges. The underperformance followed a mixed earnings report released earlier in the week, where the Indian IT services firm reported revenue growth below analyst estimates despite improved operating margins. Short-term technical indicators showed bearish momentum, with the 20-day moving average crossing below key support levels.

Analysts noted that market sentiment was further pressured by broader sector weakness in global technology stocks. Institutional selling activity intensified during afternoon trading, with large-cap tech funds reducing exposure to cyclical plays. The stock's liquidity profile worsened as bid-ask spreads widened to 0.6% by market close, reflecting reduced institutional interest in the name. Options traders also showed reduced volatility expectations, with at-the-money put volumes declining 43% compared to the previous week.

To build a back-test that matches your idea precisely, I need to clarify a few practical details: 1. Market universe • Do we limit the search for the “top-500 by trading volume” to U.S. listed equities (NASDAQ + NYSE), or is it a global universe? 2. Weighting & capital deployment • Equal-weight each of the 500 names every day? • Deploy 100% of capital daily (full rebalance), or overlay a cash buffer / turnover cap? 3. Transaction-cost assumptions • Zero, fixed (e.g., 1 bp per side), or a specific schedule? 4. Data coverage • My current tool set supports single-ticker and event-based tests. A true 500-stock daily-rebalanced portfolio is possible, but it involves aggregating thousands of individual signals. • If a broad proxy (e.g., S&P 500 ETF “SPY” or another high-volume ETF) is acceptable, we can execute the back-test immediately. • Otherwise, I can outline the full multi-asset workflow and the additional data ingestion steps required. Let me know your preference on the above points and I’ll proceed with the most appropriate implementation.