One job: tell players exactly when the season ends.
Game publishers move season end dates. They extend them for live events, shift them around launch windows, and sometimes leave the in-game timer ambiguous on purpose. We exist to be the single, plain-language source that says: this is when the Battle Pass closes, this is when ranked resets, this is when your unclaimed rewards disappear.
We do not write reviews, leak skins, predict metas, or run news. The site is a focused utility. Every page is a countdown plus the minimum context you need to plan around it — and a record of how we know.
Where every date on the site actually comes from.
We use a strict source hierarchy. A date does not appear on the site until at least one Tier 1 or Tier 2 source confirms it. Forum posts, Reddit threads, leaker accounts, and unofficial Discords are reference material at most — they never become the published date.
Tier 1 — Official publisher channels
- In-game countdown timers and season panels — the most authoritative source when present, because it's what the publisher tells the player directly inside their own product.
- Official patch notes and developer blog posts — the standard source for confirmed end dates and roadmap windows.
- Verified publisher social accounts — Epic Games, Riot, Activision, Blizzard, Valve, and the verified game accounts they operate. Used when an official date is announced on social before it hits the in-game panel.
Tier 2 — Quoted publisher staff
- Direct quotes from a developer or publisher representative on a podcast, livestream, or interview, where the date is stated unambiguously.
- We always link to the original quote and timestamp it. If the quote is later contradicted by a Tier 1 source, the Tier 1 source wins immediately.
Reference only — never published as a date
- Datamines, leakers, fan wikis, Reddit threads, third-party stat trackers.
- These can inform our cadence-based estimates (see next section) but do not produce a confirmed date on the site.
What "confirmed" and "estimated" actually mean.
Every season on the site is tagged with one of two statuses. The difference is concrete and we don't blur it.
Tier 1 source has named the date.
The end date is taken directly from the publisher — in-game timer, patch notes, or a verified social post. The countdown is locked to that timestamp.
No publisher date yet — we project from cadence.
The end date is calculated from the past 4–6 seasons of the same game. We disclose the projection, label it visibly, and replace it the moment a Tier 1 source publishes the real date.
We do not estimate quietly. If you're looking at a countdown without an EST. tag, the date is straight from the publisher. If the EST. tag is there, treat the number as a planning aid, not a deadline you would bet money on.
How fast a date change reaches your screen.
Two things drive update speed: how often we check sources, and how the site rebuilds when a date changes.
- The countdown itself ticks every second in your browser. It's pure clock arithmetic — no network round trip — so it stays accurate even if your connection drops.
- The underlying end timestamp is checked against Tier 1 sources at least twice daily for actively-tracked games, and within minutes when a publisher posts a major announcement.
- When a date changes, the site rebuilds and the new timestamp propagates on the next page load. Most users see the corrected countdown within 5–15 minutes of the publisher's announcement.
- If a season transition is happening live, we monitor the publisher's channels in real time and push the corrected date as soon as it's verified.
What we do when we get something wrong.
We will get things wrong. A publisher will announce a date on a regional account we missed, a server-time offset will be off by an hour, a cadence projection will turn out to be a week early. Here is what happens when that happens.
- Same-day fix. Any error in a published end date is corrected within 24 hours of being identified, and usually within 1 hour.
- Visible record. When a confirmed date changes after publication — for any reason — the page shows the previous value and the date we updated it. Nothing gets silently rewritten.
- Reader corrections welcome. If you spot a date that doesn't match an official source, email us. Every correction submitted via the channel below is read by a human within 24 hours.
We do not work for any publisher.
SeasonTimer.live is operated by an independent team. We have no contracts, sponsorships, content partnerships, affiliate deals, or non-disclosure agreements with any game publisher, developer, or platform — and we never have. No publisher reviews this page or any countdown before it goes live, and no publisher has the ability to delay, suppress, or rewrite a date we publish.
We do not take money to feature games, change the running order on the homepage, or apply visual emphasis. The order on the homepage is sorted by the same criteria for everyone: deadline, alphabetically, or by elapsed percentage — your choice, in the toolbar.
How advertising works on this site.
The site is supported by display advertising served through automated networks (currently Google AdSense). Ads are placed in fixed slots that are clearly distinguishable from editorial content. They are labelled, never woven into prose, and never shown above a countdown.
Advertisers cannot influence which games we cover, which dates we publish, or where any game appears on the site. We do not run sponsored countdowns and we do not accept money to feature a specific season, Battle Pass, or game.
Spotted something off? Tell us.
Corrections, source links, or "you're missing this game" notes are the most useful messages we get. We read everything, even when we don't reply.
- Corrections & source tips: salvadorjesus.seo@gmail.com
- Press & partnerships: salvadorjesus.seo@gmail.com — note that we do not accept paid placements.
- Privacy & data requests: salvadorjesus.seo@gmail.com