THE MOSAIC LEDGER

ICHR

MISS :: earnings event :: tier RESOLVED

Registered claim

ICHR Q2 2026 (reports 2026-08-04) prints revenue at least 2% above Street consensus AND reports revenue at or above $310M (the high end of the $290-310M guide issued 2026-05-04) rather than landing inside the range as a post-surprise re-anchoring would imply.

Registered 2026-07-27.

Resolution spec

Spec registered 2026-07-27.

Verdict rule: HIT if leg A and leg B. PARTIAL if leg A and not leg B. MISS if not leg A.

As frozen: HIT = A && B; PARTIAL = A && !B; MISS = !A

Tier history

Evaluated daily since registration: 8 evaluations. The 2 that moved the tier are listed above.

Resolution receipt

Verdict: MISS. Resolved 2026-08-04.

Rule: HIT if leg A and leg B. PARTIAL if leg A and not leg B. MISS if not leg A.

As frozen: HIT = A && B; PARTIAL = A && !B; MISS = !A

Autopsy

Read the full autopsy
Resolved MISS on 2026-08-04. Both legs failed. The core leg asked for revenue at least 2% above the consensus snapshot frozen before the print; Ichor reported $294.8M against a frozen baseline of $306.17M, 3.7% below it. The confirm leg asked for revenue at or above $310M, the high end of the $290M to $310M guidance issued on 2026-05-04; the company landed inside its own range rather than above it, which is exactly the outcome the call was written to rule out. It is the only clean double failure among this cycle's resolutions.

The business did not disappoint. Revenue rose 24% year over year and roughly 15% sequentially, non-GAAP earnings of $0.34 beat the $0.31 estimate, third-quarter earnings were guided to $0.40 to $0.50, and the balance sheet took on $195.4M of equity-offering proceeds. On the call, finance chief Greg Barros said isolated supply-chain constraints late in the quarter kept Ichor from recognising its full revenue forecast before the June 26 quarter end, and that the company passed $300M for the thirteen weeks ending July 3. Part of the shortfall is a fiscal-cutoff artifact rather than demand. Management also guided the full year to at least 30% revenue growth. None of that changes the verdict; all of it changes what the miss means.

The harder complication is that consensus was not one number. At least four second-quarter revenue figures were in circulation at the print: $306.17M from the aggregation this call froze, $306.2M from a second aggregator, $300.3M from a three-analyst compilation, and $268.2M from a service used by several outlets. Reported revenue of $294.78M sits 3.7% below the first, 1.8% below the third, and 9.9% above the fourth. Against that last baseline the core leg would have passed, and a material share of the trade press did report the quarter as a revenue beat. The frozen choice was the conservative one and it was recorded with its rationale before the print, which is the entire reason a baseline is frozen in advance. But the plain-language summary that Ichor missed against consensus is true under one of at least three circulating consensus prints rather than as an unambiguous fact, and this record should say so. The confirm leg is immune to the ambiguity: $294.8M fails a fixed $310M threshold on every baseline in circulation, so the verdict itself does not depend on the choice.

For the thesis this is a narrow contradiction rather than a structural one. Ichor beat on earnings and missed on revenue against consensus, so a cohort reading that names it in a sequence of beats holds on the looser reading and not on the stricter one. The claim that subsystem suppliers lead their equipment customers is about direction, and direction was never in question here.

The lesson is about calibration rather than about the company. Consensus had already marked Ichor to the top of its guided range, so demanding a further 2% beat required the company to exceed a Street number that itself sat above the guidance midpoint. The call mistook a strong quarter for a surprising one. A beat-against-consensus leg is only meaningful when the consensus it names is both singular and identified. Where several are in circulation, the threshold should name its source explicitly, or be written against the company's own guidance instead.