SOURCES · FILTERS · LIMITS

Methodology: how the numbers are made.

Every figure on this site comes from a named source with stated filters. This page documents what is requested, when it is captured, and what happens when a request fails.

01 · PLAYER COUNT

Current-player service

The GetNumberOfCurrentPlayers response for app 3393110 supplies the live count. Each successful response gets its own UTC capture time, shown next to the number. When you open a page on this site, the count is requested once and then every five minutes while the tab stays open.

  • Scope: Steam only. Players on NC's PURPLE platform are not measured by this endpoint.
  • Missing data: a failed request preserves the previous reading with its original time. Unavailable counts are never shown as zero and never interpolated.
  • Session observations: readings captured while you browse are stored locally in your browser only — no server-side history is collected on this static site.

02 · REVIEWS

Review summary service

Steam's review summary service supplies aggregate positive and negative counts. The displayed percentage is positive divided by all counted reviews at capture time, rounded to one decimal place. These reviews are cumulative — not limited to release day.

  • Filters requested: all languages, all purchase types, with Steam's off-topic activity filter applied. A store page using narrower settings can legitimately show a different score.
  • Independent capture time: reviews are a separate data request from the player count, so their timestamps can differ.

03 · EXTERNAL RECORDS

Launch peak and release dates

The 397,905 launch-day peak and its date come from SteamDB's published chart for AION 2. We cite the record as published — we do not scrape SteamDB automatically or label it as our own observation. Release milestones come from the NC announcement and the official Steam store page.

04 · WHAT WE DO NOT DO

Missing data is a gap, not a zero.

We do not fill an unavailable value with zero, interpolate between observations, or work backward from today's count to invent first-week history. A gap in observations is a gap. Sampling every five minutes can also miss a higher count between requests, so a session maximum is never substituted for the launch-day record.

Concurrent counts describe simultaneous Steam activity. They cannot measure unique players, cohort retention, revenue, or cross-platform population. Where a claim depends on those, this site stays silent.