Server Season Clock — which season and week is your server in?

One server number in, one page of calendar out. Hard facts get a countdown; estimates are labelled as estimates.

"What week is your server on?" gets asked in alliance chat far more often than you'd expect — when people plan hero awakenings, when they shop for a migration target, when a new R4 is trying to line up the calendar. And it is weirdly hard to answer. The game shows you the season name and event timers, but nowhere does it print "you are in week 7 of this season" in big letters. I've personally miscounted it by a week once, early in Season 6, right when I was trying to time an awakening.

So here's a clock that does the counting. It runs on the tracker's open dates for 2,304 servers, plus the actual season-start timestamps for every Season 5 and 6 server. One rule shaped the whole thing: no countdowns to dates nobody knows. Nobody outside the studio knows when the next season drops, and any site that shows you a ticking timer for it is making the number up.

What's a fact, what's data, what's a guess

Every number on the result card falls into one of three buckets, and that split is really the point of this page.

1. Facts — shown as countdowns. The daily reset (02:00 UTC), the weekday, and anything that follows mechanically from the open date. Shining Mission runs on a 3-day cycle counted from the server's opening day, so it never drifts. Same for the weekly A/B event (General's Trial or Zombie Invasion Wed–Fri, Doomsday or Rampage Bosses on Sunday). When we checked both rules against an outside calendar for all 2,304 servers, they matched every single one.

2. Data — exact weeks. For Season 5 and 6 servers we hold the actual timestamp the game flipped the season. Their week number is measured, not guessed. What we don't know is when a Season 5 server will move to Season 6 — so instead of a date you get the span earlier waves actually spent in Season 5 (126–168 days). It's "here's how long it took everyone before you", not a prophecy.

3. Rule-of-thumb — marked "(est.)". Seasons 0–4 have no start timestamps in our data, so the season comes from an age rule: 148 days after opening → S1, 219 → S2, 336 → S3, 464 → S4, 576 → S5, 668 → S6. That reproduces an outside calendar's season labels 99.8% of the time. It is also a moving target — the thresholds we derived in mid-August (134/220/340/457/561/693) had drifted to today's values three weeks later, because seasons don't all run the same length. So for S0–S4 servers the next season is shown as a ±3-week window, never a date.

Seasons move in waves, not one server at a time

This was the fun part of digging through the data. Line up the Season 5 and 6 start timestamps and you'll see blocks of servers sharing the exact same second. The game promotes whole server-number blocks together. Early blocks are lumpy (3–68, 69–196…) and after that it settles into almost perfectly 128-server chunks. Here's every Season 5 wave on record:

Servers	Count	S5 start	Age at S5 (days)	S6 start	S5 length
#3–#68	64	2025-11-03	688–866	2026-04-13	161 d
#69–#196	128	2025-11-17	666–702	2026-05-04	168 d
#197–#420	224	2025-11-24	602–673	2026-05-04	161 d
#421–#676	256	2025-12-01	525–609	2026-05-11	161 d
#677–#804	128	2026-01-12	519–566	2026-06-01	140 d
#805–#932	128	2026-02-23	518–561	2026-06-29	126 d
#933–#1060	128	2026-04-06	523–559	2026-08-24	140 d
#1061–#1188	128	2026-05-25	520–571	2026-09-28	126 d
#1189–#1316	128	2026-07-06	519–562	still S5	—
#1317–#1444	128	2026-09-07	533–581	still S5	—

Two things jump out. The age at which a server gets Season 5 has converged — recent waves all land around 518–533 days, while the very first block waited more than 688. And Season 5 length swings from 126 to 168 days — about six weeks between the shortest and the longest wave. Same game, same season, a month and a half of wobble. That's why this clock refuses to print a date for the next season.

One more thing the table hides: the first block into Season 6 (servers 3–68) started it on 13 April 2026 and is still in it. Our Season 6 week-by-week guide covers eight weeks; clearly there's a long tail after that. When your week count runs past the plan, the card labels it "late season" instead of inventing events.

How I actually use it

Timing awakenings. On a Season 6 server the card tells you whether this is Kimberly's awakening week, DVA's, or a Global Expedition week. Awakening needs the exclusive weapon at Lv20 first, so I work backwards from the unlock week — showing up on unlock day with a Lv14 weapon is how you lose a week.

Picking a migration target. Servers in the same wave change seasons together. Move within your wave and your season rhythm carries over; move across waves and you may repeat or skip part of a season. Look at the "same wave" range and migration group together — and use the migration finder to actually shortlist targets.

Writing the Monday post. As an R4 this is my most common use: "A week — General's Trial Wed–Fri, Doomsday Sunday." Copy it straight off the card.

Limits

The studio can and does move schedules, and server merges or special events can break any rule here. No new server has opened since #2308 on 7 August 2026, so the list covers #3–#2308 (#4 and #7 don't exist). The in-game calendar always wins. If this clock disagrees with it, that's a sign a rule changed — tell us and we'll re-derive the thresholds in the next snapshot.