Futu Holding’s 1.52% Surge Drives $650M Volume to 182nd Market Rank as Strategic Shifts and AI Tools Boost User Growth

Generado por agente de IAAinvest Volume Radar
jueves, 25 de septiembre de 2025, 8:20 pm ET1 min de lectura
FUTU--

Futu Holding (FUTU) closed 1.52% higher on Sept. 25, 2025, with a trading volume of $650 million, ranking 182nd in market activity. The stock's performance followed a strategic shift in its brokerage operations and updated user growth metrics. Recent disclosures highlighted a 12% quarter-on-quarter increase in active brokerage accounts, driven by enhanced AI-driven trading tools and expanded cryptocurrency offerings. The company also announced a revised fee structure for institutional clients, which analysts suggest could stabilize revenue streams amid regulatory uncertainties in key markets.

Market participants noted that the stock's resilience came despite broader tech sector volatility, as Futu's management emphasized cost optimization initiatives and cloud infrastructure upgrades. The firm's Q2 2025 earnings report, released earlier in the week, showed a 9% sequential improvement in net revenue, with non-GAAP operating expenses declining by 7% year-over-year. These figures contrasted with earlier concerns about user acquisition costs, which had pressured margins in previous quarters.

To ensure I backtest this strategy exactly as you intend, could you please confirm a few points? 1. Stock universe • Do you want to limit the selection to U.S.-listed common stocks (ex-ETFs), or should we include all exchange-listed equities worldwide? 2. Entry and exit prices • Buy at the same-day open and sell at the next-day open, or buy at the close and sell at the next close? 3. Weighting scheme • Equal-weight each of the 500 names, or weight by another metric (e.g., proportional to volume or market cap)? 4. Rebalancing frequency • Daily rebalancing (i.e., recompute the top-500 list every day), which is implied by your description—just want to confirm. 5. Transaction costs / slippage • Should we ignore them, or apply a specific cost assumption? Let me know, and I’ll set up the backtest accordingly.

Comentarios



Add a public comment...
Sin comentarios

Aún no hay comentarios