Verisk’s Modest 0.27 Rise Masks 2.5M Volume Ranking at 402nd in Market Activity

On September 24, 2025, Verisk (VRSK) closed with a 0.27% gain, trading with a volume of $250 million, ranking 402nd in market activity for the day. The stock’s modest performance followed a mix of industry-related developments and strategic updates from the company.

Recent reports highlighted Verisk’s ongoing expansion in risk analytics, with analysts noting increased demand for its data solutions in the insurance and financial sectors. The firm’s recent partnerships with mid-sized insurers were cited as a potential catalyst for long-term growth, though no immediate earnings impact was specified. Additionally, Verisk’s Q3 2025 product roadmap, emphasizing AI-driven underwriting tools, was described as a key differentiator in a competitive market landscape.

To run this back-test accurately I need to clarify a few practical details and confirm that the approach matches our back-testing engine’s current capabilities: 1. Universe • Which market do you want to draw the “top-500 by trading volume” from? • If it’s the U.S. market, do you want to include all listed common stocks (NYSE + NASDAQ + AMEX) or restrict it to a specific index universe (e.g., Russell 3000)? 2. Rebalancing mechanics • Each trading day we rank all stocks by that day’s dollar trading volume, buy an equal-weighted basket of the top 500 at the day’s close, and liquidate the basket at the next day’s close – is that the intended trade logic? • If you prefer using open prices for entry/exit instead of closes, let me know. 3. Practical constraints • Our current single-ticker back-testing engine does not natively handle a daily-rebalanced 500-stock basket. We can: a) programme a portfolio back-test offline and return the stats, or b) use a liquid ETF that tracks high-volume equities (an approximation). Let me know which route works for you. 4. Transaction costs / slippage • Do you want to include estimated trading costs (e.g., 5 bps each side) or keep it frictionless? Once I have these details I can build the data-retrieval plan and run the back-test from 2022-01-01 to the present.