Consolidated PAT Jumps 165% YoY on Neemrana Ramp; Beats Street, Prior Guidance

KRN's consolidated Q1FY27 print — revenue ₹252.32 Cr (+118.9% YoY, +40.6% QoQ) and PAT ₹32.90 Cr (+164.9% YoY, +40.8% QoQ) — clears the pre-result Street bar comfortably. Our preview had flagged ₹125–150 Cr revenue and 9–12% NPM/13–16% OPM as the expectation going in; the actual print (OPM 19.4%, NPM 12.9%) beats every metric in that range, and revenue alone is 68–100% above the top of the expected band. Against management's own Q4FY26 guidance — 50% utilisation at the new facility, doubling export revenue, and only "slight" margin improvement — the company has already overshot on exports (₹52.38 Cr this quarter vs ₹18.89 Cr a year ago, +177% YoY, well past a doubling) and on margins (OPM +418bps YoY, not slight) inside the very first quarter of the guided year. The margin bridge sits mostly on operating leverage from the new Neemrana subsidiary rather than the parent: standalone OPM is 13.6% and NPM 10.1%, both well below the consolidated 19.4%/12.9%, meaning the higher-margin incremental volume is coming from the group's new capacity, not the existing standalone business. That also explains why standalone growth (+59% revenue, +19% PAT YoY) looks far more ordinary than the headline consolidated numbers — readers should anchor on the group figure as primary but not mistake it for organic parent-level growth. Corporate developments this quarter tie directly into the ramp story: both the ₹311.12 Cr IPO proceeds and the ₹341.79 Cr QIP raised in May–June 2026 are now fully utilised with no deviation flagged, funding the Neemrana facility and subsidiary working capital that are already showing up in this quarter's output. The board also appointed new cost and internal auditors for FY27, a routine governance item. No standalone management press release/commentary was available beyond the board-outcome filing, so there is no separate management framing to reconcile against the numbers this quarter. What carries forward: the filing doesn't disclose an explicit capacity-utilisation percentage or a data-center-cooling revenue split, so the next print needs to make that ramp trajectory and mix explicit rather than inferred from segment/subsidiary totals.