Nebius grew revenue 454 percent and signed four deals averaging a billion dollars each. It also lost 190 million dollars in the same quarter, and its own management did not raise guidance.
Every number in the headline is a chosen number. Percentage growth hides the small base, TCV hides the duration, adjusted EBITDA hides the depreciation. The unchosen number is the loss.
"Nebius grew revenue 454% year over year to $582.3 million in Q2 2026 and closed four AI cloud deals with an average total contract value exceeding $1 billion each, with adjusted EBITDA swinging to a positive $236.2 million." [SOURCE ↗]

THE CLAIM. Nebius reported Q2 2026 revenue of $582.3 million, up 454% year over year, closed four AI cloud deals with average total contract value exceeding $1 billion each, and swung adjusted EBITDA positive to $236.2 million. The stock jumped 28%.
THE CHECK. the same quarter produced a GAAP net loss from continuing operations of $190.4 million. The 454% is measured against a year-ago quarter roughly one sixth the size. The billion-dollar deals are total contract value with no disclosed duration. The adjusted EBITDA excludes depreciation on the GPUs that earn the revenue, which for a GPU landlord is the cost of goods. And management, looking at all of it from the inside, reaffirmed rather than raised full-year guidance.
THE PATTERN. the neocloud earnings kit is standardized now: a triple-digit percentage, a TCV, an adjusted profit metric, and a GAAP loss in the appendix.
On August 12, Nebius Group, the Amsterdam-headquartered AI cloud company built from the remains of Yandex's international assets, reported Q2 2026 revenue of $582.3 million, up 454 percent year over year and ahead of the roughly $574 million consensus. The core AI cloud business rose sixfold and now
🔒 THE FULL AUTOPSY · FREE WITH AN ACCOUNTYou just read the free check. Sign in free, a code by email, no passwords, and the rest unlocks: the evidence trail, the steelman and the rebuttal, all 3 sources with quotes and screenshots, and our on-record call.
Couldn't verify your access — this looks like our error, not yours.