Reactor Status Timeline
Online NRC data, Mon to Fri ? Actual daily reactor status from NRC reports (Mon to Fri), the current state, and what is coming: the utility's published Scheduled outage plus, for subscribers, NukeWorker's model Projection. Colored by status. How far ahead you can see depends on your plan.OnlineReduced PowerCoastdownPower AscensionRefueling OutageForced Outage
?
Composite Operational Excellence Score (0-100) — average percentile rank across 7 dimensions in three sub-scores: Reliability (capacity factor, forced outage days, B2B avg streak), Efficiency (fuel utilization, refuel duration), and Discipline (startup duration, scram count). 5-year window. Higher = more operationally excellent. Click to see the full breakdown.
49
Excellence
#50 of 93 ↑13
Mid Quartile
?
Days of continuous operation since the last outage ended. Clean run (no forced outages since last refueling).
60
Current Run
days ✔
?
Longest recorded period of continuous operation between outages (2018-04-07 to 2020-03-30).
723
Record Run
days
?
Breaker-to-Breaker runs — continuous operation exceeding the cycle-adjusted threshold (626 days for this 24-month cycle unit) with no trips to 0% power.
4
B2B Runs
?
Lifetime capacity factor: average power level across all recorded days (100% = always at full power).
92%
Capacity Factor
?
Net electricity actually generated over the most recent 12 months reported by the U.S. EIA (Form EIA-923), summed across every unit at this plant. Authoritative actuals, not an estimate.
15.19 TWh
Net Generation
EIA-923 · 12 mo to 2026-04 · plant total
?
Total number of scheduled refueling outages detected in the historical data.
14
Outages
since 1999
?
Average time from first power generation (>0%) to sustained full power (≥95% for 2+ days) across the last 3 scheduled outages. Click to compare against the fleet on the Operator Efficiency Leaderboard.
3
Avg Startup
days (last 3)
?
Average fuel utilization — percent of the designed fuel cycle that this unit consumes before refueling, derived from the historical burn-down trajectory. Higher = more efficient operator (refuels with less margin remaining; closer to coastdown). Computed as 100% minus the unit's average refuel-point fuel %, using the last 3 years where available, otherwise lifetime average. Click to compare against the fleet on the Operator Efficiency Leaderboard.
100.0%
Fuel Utilization
3yr avg
?
NukeWorker's Operational Excellence Score is a composite 0–100 ranking of every active US nuclear unit across 7 publicly observable performance metrics, grouped into three sub-scores:
• Reliability — capacity factor, forced outage days, B2B avg streak
• Efficiency — fuel utilization, refuel duration
• Discipline — startup duration, scram count
Each unit's metric is converted to a percentile across the active fleet. Sub-score = average of its components; composite = average of the three sub-scores. Use the time-window toggle below to switch between 3yr / 5yr / lifetime.
• Reliability — capacity factor, forced outage days, B2B avg streak
• Efficiency — fuel utilization, refuel duration
• Discipline — startup duration, scram count
Each unit's metric is converted to a percentile across the active fleet. Sub-score = average of its components; composite = average of the three sub-scores. Use the time-window toggle below to switch between 3yr / 5yr / lifetime.
Time window
— change how far back we look
NukeWorker's
Operational
Excellence Score
Operational
Excellence Score
49/100
Mid Quartile · #50/93
5-year window
Quad Cities 2 ranks #50 of 93 active US units on NukeWorker's Operational Excellence Score over the 5-year window. Strongest area: B2B Avg Streak (81th percentile). Weakest: Scrams (5-year) (15th percentile).
Reliability
56
Capacity factor + Forced outages + B2B streaks
Efficiency
55
Fuel utilization + Refuel duration
Discipline
36
Startup duration + Scram count
Cohort Rankings
apples-to-apples comparison within each peer group
Reactor type:
#15 of 31
BWR
Containment:
#10 of 19
Mark I (BWR)
Cycle length:
#22 of 40
24-month cycle
Fleet rank above (50 of 93) compares all active US units; cohort ranks compare only against units sharing this property.
Per-dimension breakdown (7 metrics)
Capacity Factor
54th
92.1% (higher better, Reliability)
Forced Outage Days/yr
34th
5.2d (lower better, Reliability)
B2B Avg Streak
81th
696d (higher better, Reliability)
Fuel Utilization
31th
97.2% (higher better, Efficiency)
Refuel Duration
79th
24d (lower better, Efficiency)
Startup Duration
56th
4.1d (lower better, Discipline)
Scrams (5-year)
15th
0.8/yr (lower better, Discipline)
Each dimension's percentile is computed across the active US fleet (93 units with sufficient history). Sub-score = average of its component percentiles. Composite = average of the three sub-scores. 5-year window. View full leaderboard →
Methodology
NukeWorker's Operational Excellence Score is a composite ranking that combines 7 publicly observable performance metrics into a single 0-100 number per US nuclear unit.
How it's computed: Each unit's raw value is converted to a percentile (0-100) within the 93 active US units that have at least 2 completed refueling cycles. The 7 percentiles are averaged into 3 sub-scores (Reliability, Efficiency, Discipline), and those are averaged into the final composite.
Active window — 5-year:
- Reliability — Capacity factor (5yr), forced outage days/yr (5yr), B2B avg streak (lifetime)
- Efficiency — in-cycle fuel utilization (3yr), median refuel duration (5yr)
- Discipline — robust mean startup duration, scrams/yr (5yr, annualised)
Cohort rankings: alongside the fleet rank, each unit gets ranked within its reactor type (PWR/BWR), containment design (Ice Condenser, Mark I, etc.), and cycle length (12/18/24-month). Useful for apples-to-apples comparisons.
What's excluded: subjective community ratings, confidential INPO ratings, financial metrics. We only use publicly available NRC + cycle data.
Why three windows? 5yr (default) is the industry standard. 3yr captures recent operational changes and post-pandemic recovery. Lifetime gives newer units a fair comparison and reveals long-term consistency.
Edge cases: units with fewer than 2 cycles (e.g., Vogtle 4) show "Provisional". Decommissioned units excluded.
Refresh cadence: recomputed daily. Each window cached separately.
A data-derived proxy for operational performance; not affiliated with INPO. INPO ratings are confidential and qualitative — ours is public and quantitative.
5-yr trend:
↑ +4.9 pts vs 2025
Compare Quad Cities 2 head-to-head with up to 3 other units.
Compare now
?
Duration of each outage in days, shown chronologically. Green bars are scheduled refueling outages, red bars are forced/unscheduled. The orange dashed line marks the average duration. Extended outages (>180 days) and D&D periods are excluded.
Outage Duration Trend
Quad Cities 2 has 43 outages plotted here, averaging 12 days each. The most recent, in May 2026, was a unplanned outage lasting 8 days.
?
Days between consecutive scheduled refueling outage starts, showing operating cycle regularity. The purple dashed line marks the average cycle length. Most U.S. reactors operate on 18-month (547 day) or 24-month (730 day) cycles.
Cycle Length History
Between refueling outages, Quad Cities 2 runs about 736 days, or roughly 24 months, per cycle. That average comes from 13 completed cycles, the most recent lasting 742 days.
?
Time in days from first power generation (>0%) to sustained full power (≥95% for 2+ consecutive days) after each scheduled refueling outage. The dashed line marks the average. Includes startup testing holds and power dips.
Startup Duration Trend
After a refueling outage, Quad Cities 2 takes about 5 days to climb from first power back to full power. That average is drawn from 13 startups on record, and the most recent took 3 days.
?
Estimated fuel remaining in the current cycle, expressed as a percentage of the unit's typical cycle. Starts at 100% when the unit returns to power post-refuel and drops as full-power-days are burned. Days at reduced power burn fuel proportionally — so a unit with significant downtime (high burn deficit) drops slower and ends up with MORE fuel left than its calendar position would suggest. Coastdown threshold around 15%. Toggle to overlay past cycles on a normalized "days into cycle" axis to see how aggressively this unit historically burns down before refuel.
Fuel Burn Down Cycle since Apr 25, 2026
89.9% remaining
81 / 703 days
10.0 FPD margin
Quad Cities 2 is 81 days into its current fuel cycle with an estimated 89.9% of its fuel left. This cycle is set up to run about 703 days. Across its last 13 cycles, it has refueled with an average of 3.7% remaining.
Avg refuel: 3.7%
Avg refuel (3yr): 0.0%
Deepest burn: 0.0% (2018-04 → 2020-03)
Most margin: 11.5% (2004-03 → 2006-03)
?
Monthly capacity factor with outage events overlaid as red bands. Green bars show average power level per month. Toggle to Daily view for raw daily data.
Power History
Over its operating life, Quad Cities 2 has run at about 92% of its rated capacity. Across the last 12 reported months it averaged 88.5%. On the chart, flat stretches near the top are full-power running and drops to zero are outages.
This table logs every recorded outage for Quad Cities 2, 43 in all since 1999. Of those, 14 were scheduled refueling outages and 29 were unplanned or forced. The typical outage lasted about 12 days. Where the Scheduled column shows (Model), the date is a NukeWorker projection because the utility had not published one.
| Type ⇅ | Actual Start ⇅ | Actual End ⇅ | Duration ⇅ | Days Online ⇅ | Scheduled | Delta |
|---|---|---|---|---|---|---|
|
Unscheduled
|
2026-05-09 | 2026-05-16 | 8 | 16d | - | - |
|
Scheduled
|
2026-03-30 | 2026-04-23 | 25 | 674d | 2026-03-30 | 0d |
|
Scram
# 57141
|
2024-05-24 | 2024-05-25 | 2 | 44d | - | - |
|
Scheduled
|
2024-03-18 | 2024-04-10 | 24 | 218d | 2024-03-17 | +1d |
|
Scram
# 56676
|
2023-08-12 | 2023-08-13 | 2 | 88d | - | - |
|
Unscheduled
|
2023-05-10 | 2023-05-16 | 7 | 185d | - | - |
|
Scram
# 56210
|
2022-11-05 | 2022-11-06 | 2 | 123d | - | - |
|
Scram
# 55975
|
2022-07-04 | 2022-07-05 | 2 | 72d | - | - |
|
Scheduled
|
2022-03-21 | 2022-04-23 | 34 | 707d | 2022-03-21 | 0d |
|
Scheduled
|
2020-03-30 | 2020-04-13 | 15 | 723d | 2020-03-30 | 0d |
|
Scheduled
|
2018-03-19 | 2018-04-07 | 20 | 220d | 2018-03-19 | 0d |
|
Unscheduled
|
2017-08-06 | 2017-08-11 | 6 | 486d | - | - |
|
Scheduled
|
2016-03-21 | 2016-04-07 | 18 | 685d | 2016-03-21 | 0d |
|
Scheduled
# 49988
|
2014-04-01 | 2014-05-06 | 36 | 429d | 2014-04-07 | -6d |
|
Unscheduled
|
2013-01-27 | 2013-01-27 | 1 | 282d | - | - |
|
Scram
# 47847
|
2012-04-19 | 2012-04-20 | 2 | 3d | - | - |
|
Scheduled
|
2012-03-19 | 2012-04-16 | 29 | 577d | 2012-03-19 | 0d |
|
Unscheduled
|
2010-08-18 | 2010-08-20 | 3 | 122d | - | - |
|
Unscheduled
|
2010-04-16 | 2010-04-18 | 3 | 2d | - | - |
|
Scheduled
|
2010-03-15 | 2010-04-14 | 31 | 450d | 2010-03-15 | 0d |
|
Unscheduled
|
2008-12-13 | 2008-12-20 | 8 | 6d | - | - |
|
Unscheduled
|
2008-12-06 | 2008-12-07 | 2 | 252d | - | - |
|
Scheduled
|
2008-03-03 | 2008-03-29 | 27 | 368d | 2008-03-03 | 0d |
|
Unscheduled
|
2007-02-28 | 2007-03-01 | 2 | 316d | - | - |
|
Scheduled
|
2006-03-25 | 2006-04-18 | 25 | 66d | 2006-03-24 | +1d |
|
Unscheduled
|
2006-01-14 | 2006-01-18 | 5 | 13d | - | - |
|
Unscheduled
|
2005-12-31 | 2006-01-01 | 2 | 229d | - | - |
|
Unscheduled
|
2005-05-09 | 2005-05-16 | 8 | 408d | - | - |
|
Scheduled
|
2004-02-24 | 2004-03-27 | 33 | 241d | 2004-02-24 | 0d |
|
Unscheduled
|
2003-06-11 | 2003-06-28 | 18 | 32d | - | - |
|
Unscheduled
|
2003-05-09 | 2003-05-10 | 2 | 19d | - | - |
|
Unscheduled
|
2003-04-17 | 2003-04-20 | 4 | 270d | - | - |
|
Unscheduled
|
2002-07-12 | 2002-07-21 | 10 | 97d | - | - |
|
Unscheduled
|
2002-04-06 | 2002-04-06 | 1 | 5d | - | - |
|
Unscheduled
|
2002-03-30 | 2002-04-01 | 3 | 26d | - | - |
|
Scheduled
|
2002-02-12 | 2002-03-04 | 21 | 170d | 2002-02-12 | 0d |
|
Unscheduled
|
2001-08-03 | 2001-08-26 | 24 | 138d | - | - |
|
Unscheduled
|
2001-03-17 | 2001-03-18 | 2 | 241d | - | - |
|
Unscheduled
|
2000-07-19 | 2000-07-19 | 1 | 56d | - | - |
|
Unscheduled
|
2000-05-23 | 2000-05-24 | 2 | 17d | - | - |
|
Unscheduled
|
2000-05-06 | 2000-05-06 | 1 | 86d | - | - |
|
Scheduled
|
2000-01-22 | 2000-02-10 | 20 | 328d | 2000-01-22 | 0d |
|
Unscheduled
|
1999-02-20 | 1999-02-28 | 9 | - | - | - |
Page created in 0.084 seconds with 8 queries.