CrowdStrike Rises 0.63% on Strong Buy Rating and Onum Acquisition as Trading Volume Ranks 60th

CrowdStrike Holdings (CRWD) rose 0.63% on September 12, 2025, with a trading volume of 1.21 billion shares, ranking 60th in market activity. Recent developments highlight strategic moves and analyst insights shaping investor sentiment. The company’s acquisition of Onum, a data processing firm, is expected to enhance its Falcon platform by enabling real-time threat detection and reducing operational costs. This move addresses inefficiencies in cybersecurity data workflows, positioning CrowdStrike to improve scalability and response times.

Earnings estimates for CrowdStrike show mixed trends. For the current quarter, the Zacks Consensus Estimate projects $0.94 per share, reflecting a 1.1% year-over-year increase. However, the consensus for the current fiscal year stands at $3.67, a 6.6% decline from prior estimates. Analysts note that while near-term revenue growth remains robust—projected at 20.2% for the current quarter—long-term earnings forecasts are tempered by market competition. The Zacks Rank #1 (Strong Buy) underscores confidence in near-term performance, driven by upward revisions in earnings estimates over the past month.

Analyst sentiment remains divided. Following the Onum acquisition and recent earnings, price targets range widely, from $285 to $555, with an average of $460.10. Positive momentum is supported by technical indicators, including support near $430, alignment with the 20-day simple moving average, and a neutral RSI. However, bearish voices have lowered targets, citing valuation concerns. Strategic partnerships, such as collaborations with Veza and ColorTokens, further emphasize CrowdStrike’s focus on identity security and platform integration.

The current back-testing engine supports single-security strategies but lacks multi-asset capabilities. Alternative approaches include testing high-liquidity ETFs as benchmarks or evaluating specific high-volume tickers. For full portfolio analysis, users must implement custom data workflows locally.