Inotiv shares fall 10.83% after-hours as Q1 2026 earnings miss and revenue shortfall disappoint investors.
ByAinvest
Monday, Feb 9, 2026 4:11 pm ET1min read
NOTV--
Inotiv (NOTV) fell 10.83% in after-hours trading following a significant earnings miss and revenue shortfall in Q1 2026. The company reported an EPS of -$0.83, missing forecasts by 62.75%, and revenue of $120.9 million, below the expected $126.53 million. Despite 12% year-over-year growth in DSA revenue, RMS revenue declined 5.4%, driven by a 25% drop in NHP sales. High debt levels and a $28.4 million net loss further weighed on sentiment. The stock had already fallen 19.27% in premarket trading after the earnings call, reflecting investor disappointment over the financial performance and debt concerns. The key driver of the post-market decline was the unmet earnings and revenue expectations, overshadowing positive DSA segment growth.
Stay ahead of the market.
Get curated U.S. market news, insights and key dates delivered to your inbox.
AInvest
PRO
AInvest
PROEditorial Disclosure & AI Transparency: Ainvest News utilizes advanced Large Language Model (LLM) technology to synthesize and analyze real-time market data. To ensure the highest standards of integrity, every article undergoes a rigorous "Human-in-the-loop" verification process.
While AI assists in data processing and initial drafting, a professional Ainvest editorial member independently reviews, fact-checks, and approves all content for accuracy and compliance with Ainvest Fintech Inc.’s editorial standards. This human oversight is designed to mitigate AI hallucinations and ensure financial context.
Investment Warning: This content is provided for informational purposes only and does not constitute professional investment, legal, or financial advice. Markets involve inherent risks. Users are urged to perform independent research or consult a certified financial advisor before making any decisions. Ainvest Fintech Inc. disclaims all liability for actions taken based on this information. Found an error?Report an Issue

Comments
No comments yet