Summary
- Nebius Group N.V. reports annualised run-rate revenue of $6.4 billion at the end of September, a figure its own May shareholder letter defines as AI-cloud revenue from the last month of the quarter multiplied by twelve.
- A third of that quarter's AI-cloud revenue, $325.1 million, came from strategic partnerships the company describes as non-recurring by nature, and none of the six documents read here prints how much of the specific annualised month was partnership revenue.
The sentence that does the work
The November shareholder letter leads with the number: "Annualized run-rate revenue (ARR) of $6.4 billion as of the end of September was up 1,062% year-over-year and up 113% from the $3.0 billion reported at the end of June" (Nebius Group letter to shareholders, Q3 2026). The same letter adds one caution in its own words: "ARR annualizes a single month, and does not reflect the scale of our business."
What it does not do is print the arithmetic. The operative definition sits in the May 2026 letter, four pages of quarters earlier: "Annualized run-rate (ARR) is calculated by taking Nebius AI cloud revenue from the last month of the quarter multiplied by 12" (Nebius Group letter to shareholders, Q1 2026). Read that twice. The base is one month. The month is the last one of the quarter. The multiplier is twelve. This is not a trailing-twelve-month figure, not a full-quarter figure, and not a forecast.
Divide the headline by twelve and you get the month the company has annualised: $6.4 billion ÷ 12 = $533.3 million. That division is mine, not the company's; no reviewed page prints the month's revenue. Set it against the quarter and the shape of the thing appears. AI-cloud revenue for the three months was $973.8 million, up 643% from $131.1 million, according to the operating and financial review carried with the same Form 6-K (Form 6-K, Q3 2026 operating and financial review). A mean month would be $324.6 million. The month implied by the annualised figure is 1.64 times that average. One month out of three, in other words, is doing more work than the other two combined.
That is legitimate if the quarter ended on a run of strong weeks. Whether it did is exactly what a reader cannot check, because no page in this set prints AI-cloud revenue by month. The annualisation substitutes one thirtieth of a year for the year and asks you to accept the substitution on trust.
The tranche inside the base
Now the part that is printed, and printed by the company rather than inferred by anyone: "In addition, Nebius AI cloud revenues included revenue from strategic partnerships of $325.1 million and $409.1 million for the three and nine months ended September 30, 2026, respectively" (Form 6-K, Q3 2026 operating and financial review). The next sentence removes the ambiguity: "Although we expect further revenues from strategic partners in future periods, such revenues are by their nature non-recurring and the timing and amounts of such revenues are hard to predict."
$325.1 million against $973.8 million is 33.4% of quarterly AI-cloud revenue, which is my percentage computed from two printed amounts. A third of the base is a tranche the filer will not stand behind into next year. If those dollars fell evenly across the three months, an assumption nothing in these documents supplies, they would be $108.4 million of the $533.3 million month, or 20.3% of it. The honest form of the finding is smaller than the temptation: whether the month being annualised was a partnership month is not printed anywhere in the six documents read for this piece.
There is a second printed perimeter. Group revenue for the quarter was $980.8 million against $973.8 million of AI-cloud revenue, so $7.0 million sat outside the line the annualisation samples; that subtraction is mine (Q3 2026 results release). The annualised figure is taken from a segment, not from the company, and the segment is 99.3% of the company this quarter. That is a narrow gap and worth one line rather than a paragraph. Every gap in this story is narrow. The point is that each one narrows the population without anyone printing the narrowed population.
Four gigawatts of a noun
The same letter reports capacity in the same breath as the revenue: "We continue to expect to have 5 GW of contracted power by year-end 2026. We now have more than 4 GW contracted", followed by a 300 MW expansion in Missouri that takes one site to 1.1 GW under contract.
What "contracted" means is not stated in the November letter as retrieved. It is stated in May's, in a passage that defines three rungs: contracted power, "power secured by contracted land and power commitments"; connected power, "power connected into fully built and equipped data centers"; active power, "power being consumed by installed, operational IT equipment and available for revenue generation" (Q1 2026 letter). The ladder is precise. It is also three-quarters of a year old and not reprinted where the current figure is printed.
So the November disclosure gives the rung with the lightest evidentiary burden, the one that attests a signature rather than a building, and gives no connected or active total to anchor it. In the November letter's text as retrieved, no such total appears. The consequence is arithmetic anybody can attempt and nobody can finish: $6.4 billion ÷ 4 GW = $1.60 billion of annualised run-rate revenue per contracted gigawatt, mine, presented as a ratio and not as a capability claim. It divides dollars already earned against power signed and not yet energised, and no document in this set prints a conversion from one to the other.
Nobody has published GPUs per megawatt, hours per GPU, or the utilisation that turns the second into the first.
The hour nobody defined
The unit actually sold is printed plainly, and it is where the audit lands. Nebius prices GPU capacity per GPU-hour under two column headings, "Preemptible, GPU-hour" and "On-demand, GPU-hour" (Nebius GPU pricing), with CPU-only instances priced per CPU-hour and storage per GiB/month. What the hour is, whether a partial hour bills in seconds or rounds up, and what the minimum increment is: none of it appears in that page's text as retrieved.
The one granularity the page does state is about the other axis: "Spot prices are dynamic and may increase or decrease based on available capacity, cluster utilization, customer demand and customer pricing preferences", and current spot prices "may vary during the active use, including as frequently as every 15 minutes." Read that literally and the billed unit is an hour whose price is not fixed inside the hour it bills. A customer can hold the same instance and pay a different rate in each quarter of it. The page prints a unit of time and a rate, and does not print the multiplication between them.
Two names for one capex
The capital story splits on the same fault line. The release prints a cash-flow line: "Purchases of property and equipment and intangible assets (955.5) (7,300.4) 664% (2,010.0) (15,430.7) 668%" (Q3 2026 results release), which is $7,300.4 million of property-and-equipment and intangible purchases in the quarter and $15,430.7 million across nine months, my reading of the column order. The letter uses a different noun and a different scale: "Capital expenditures: Approximately $27 billion, above our $20-25 billion range, as we invest in capacity for 2027, in particular at our owned sites." In the retrieved passage, the period that figure covers is not printed beside it.
Two quantities, one of them a cash-flow line and one a guide, both called capital spending in ordinary conversation. Divide the cash line by the quarter and you get $2,433.5 million a month, 4.56 times the $533.3 million month the run-rate annualises; divide the cash line by quarterly revenue and you get 7.44, mine in both cases. Those two ratios need no commentary.
A company spending seven dollars of property-and-equipment cash per dollar of quarterly revenue and annualising a single month of that revenue is a company whose financing is doing the talking about its growth, and the arithmetic that shows it is available to anyone with the two printed numbers.
Where this reading stops
The stop is documentary and specific. Both Nebius PDFs were read as extracted page text rather than rendered layout, so a phrase missing from the text as retrieved is a finding about that text and not a certificate about the document. Three things I wanted and did not get: a month-by-month AI-cloud revenue table, since none of the six documents prints one; a connected-power or active-power total for the quarter, since the November letter's text as retrieved prints neither; and any page defining the GPU-hour's billing increment or the conversion from megawatts to billable compute, since the price page defines neither.
That is the whole perimeter. The Form 6-K cover confirms the structure that causes most of the confusion: the release is Exhibit 99.1 and the shareholder letter Exhibit 99.2 to the same filing (Form 6-K cover page). The number everyone quotes from "the results" is letter language, defined in a May letter that is not the one in front of them.
A final note on the company itself, for readers who arrive from the directory: Nebius is tracked there as an AI-cloud operator, and this piece is about the paper trail behind one sentence of its disclosure, not about whether the business is real. It is real enough to book $973.8 million of AI-cloud revenue in thirteen weeks. The question is what an annualised rate built from one unnamed month, a third of it flagged as non-recurring, tells you that the quarterly figure does not. The answer is that it tells you faster, and that speed is the product.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






