NukeGryd
Track record

Scored against what actually happened

Scored against what actually happened, refreshed daily, and published in full. Two questions, answered separately: how firm the near-term schedule is, and how long the outage really runs once it starts.
Start date score
99.7 / 100
100 = called within two days, fleet-weighted
Overrun score
83 / 100
100 = the projected extension landed exactly
Beats the operator's own date
59.6%
of the time, on the return-to-service date
Forced-outage duration
83 / 100
mean error 4.3 days across 956 trips
Units scored
94
every operating reactor, rescored daily

1 · The near term: the schedule we source

Refueling dates are not public. Utilities do not announce them, no regulator filing carries them, and they cannot be scraped. We source them through the outage network NukeWorker has run inside this industry since 1999, corroborate them across independent sources, and publish them as a firm schedule. Published here means published by us.

Scored against the day each reactor actually dropped power, the dates we published run 99.7 out of 100 fleet-wide. That is the front of the curve, and it is the part no one else can rebuild from public data.

2 · Once it starts: how long it really runs

Outages run past their published end date, and the published number does not tell you which ones or by how much. NukeGryd projects the extension per unit, in days, from fleet-wide history blended with that unit's own recent overrun record.

Our projected end date beats the utility's published one 59.6% of the time, and scores 83 out of 100 on overrun fleet-wide. That is the difference between knowing a unit is scheduled back and knowing when it is actually coming back.

See which units are projected to run long
End-date projection, head to head
NukeGryd overrun score 83 / 100
We are closer than the utility 59.6% of outages
Start-date score 99.7 / 100

Rescored 14 Sep 2026.

3 · Out to 18 months: the model

Beyond the dates we already hold, the model takes over, and it is not a fuel-cycle countdown. It scores every US reactor on more than thirty signals: its own cycle length and how tightly it holds to it, the month it habitually goes down and even the day of the week it prefers, how its owner sequences outages across the rest of their fleet, reactor supplier and containment type, capacity factor, forced-outage and scram rate, unit age and license runway, and how long that unit's recent outages have actually run. Owner-specific weights are fitted on top of that.

That is why it still holds up a year and a half out, where a cycle calculation does not. The forward curve publishes it as a P10 to P90 band, so the uncertainty is on the screen rather than hidden inside a single date.

Advance projection, average error
Start date 4.1d
Duration 7.5d
Start date, all years on record 5.4d
Duration, all years on record 7.3d

The first two rows cover outages from 2023 onward; the two beneath them cover every outage on record. The recent window is better because the model is, and both are published so the difference is ours to explain rather than yours to discover. Scored out-of-fold: every projection graded by a model that never saw that outage.

How this is scored

Against actuals, not against ourselves. Every score compares a date we published in advance with the day the reactor actually changed power in the NRC daily record.
The scale. 100 means the call landed within two days, decrementing as the miss grows. The same scale is used for start dates and for overrun, so the two are comparable.
The head-to-head. The win rate counts outages where our projected end date was closer to reality than the utility's published one, on the outages where both existed.
One source of truth. These are the same live figures as the full unit-by-unit scorecard, which lists every reactor's score individually.

This is the data behind the forward curve.

Sourced dates carried through verbatim, overrun projected per unit, and the model filling every unit we do not yet hold a date for, out to 18 months, by market.
See pricing and subscribe