Reports

How we measure

Where the numbers in GameSentry reports come from, how servers are grouped and the rules every figure follows. The numbers on this page are read from the same definitions the reports use.

01

What we measure, and where the data comes from

GameSentry queries public game servers around the clock and records each server's player count, settings and wipes. Reports are built from that history: the players online on each server, hour by hour, and the wipes we observed.

We keep hourly history for 8 days and daily history for 400 days. Analyses of a week read the hourly history; longer trends read the daily history.

All times and dates are in UTC.

02

How servers are grouped

Each server falls into one group per dimension, with two exceptions: in game modes a server can sit in several groups or none, and servers whose map size is unknown sit outside the map size dimension.

Group size
The team size limit the server sets. 8 is the game's default, so those servers never set their own limit.
Solo, Duo, Trio, Quad, Groups of 5 to 7, Default limit (8), No limit
Server type
How the server describes itself. Unclassified when it does not say.
Community, Modded, Unclassified
Wipe schedule
The schedule the server advertises, or the one we observed. See wipe cadence below.
Weekly, Biweekly, Monthly, Weekly (observed), Biweekly (observed), Monthly (observed), Not advertised
Map size
The size of the current map. Servers whose map size is unknown are left out of this dimension only.
Under 3,000, 3,000 to 3,499, 3,500 to 3,999, 4,000 to 4,499, 4,500 and up
Game modes
Game modes the server flags.
Battle royale, Aim training, Minigames, Creative, Build servers, Battlefield, Roleplay, Premium, PvE
Mod framework
The mod framework we detect on the server.
Oxide, Carbon, No mod framework
Region
The region of the country the server is hosted in. CIS servers form their own region.
Europe, CIS, North America, South America, Asia, Oceania, Middle East and Africa, Other
03

Minimum samples

A group is published only when at least 25 servers are behind it. Smaller groups are too noisy to compare, so they are left out rather than shown with a warning.

An hour counts only when the servers reporting in it reach 50% of the best covered hour in the same period. This keeps quiet night hours and drops hours with missing history, so a gap in collection never reads as a drop in players.

04

Retention after a wipe

Retention compares a server's busiest moment on each day after a wipe with its busiest moment on wipe day. Day 0 is the 24 hours starting at the hour of the wipe, and each later day is the next 24 hours. A server's retention on a day is its peak players that day as a percentage of its day 0 peak. Values above 100% mean a slow start, and are kept.

We measure day 0 to day 7. A day counts only when every one of its hours has history and the server did not wipe again before the day ended.

A group's retention on a day is the median of its servers' retention, so one very large server cannot move it. It is published only for days with at least 25 servers behind it, and a curve stops at the first day below that rather than bridging a gap.

05

Wipe cadence: advertised and observed

A server's wipe schedule is the one it advertises, such as weekly, biweekly or monthly. A blank schedule counts as none.

When a server advertises no schedule, we look at the wipes we observed over the last 70 days. Wipes less than 12 hours apart count as one. With at least 2 gaps between wipes, the median gap sets the cadence: up to 9 days is weekly, up to 18 days is biweekly and up to 35 days is monthly. These servers are marked as observed.

Servers with neither an advertised schedule nor a clear observed cadence are shown as not advertised.

06

What we exclude

Server counts, the groups on this page and the hype board count only public servers that were online during the period. Private listings, deleted servers and servers whose owners hide them from the server list are left out.

Player totals hour by hour, peak hours, retention after a wipe and wipe timing are measured across every server we track for the game, including private, hidden and offline ones, so they reflect all the players and wipes we saw.

The most played servers list follows the same rules as server counts. The biggest wipe day crowds and biggest climbers lists leave out private listings and deleted servers.

Groups below the minimum sample and hours without enough history are left out, as described above.

07

Editions do not change

Each dated edition, such as a weekly report, is published once and never changes afterwards. Its link stays the same. When the method changes, the change applies to new editions and to the live report, and earlier editions keep the method they were published with.

08

What we never do

  • Group figures, such as a segment's players per server or its retention, are published only for groups of at least 25 servers.
  • Lists that name servers show positive or neutral facts only, such as the most players or the biggest climb. We never rank a named server negatively.
  • Server report cards, when they launch, are public only when the owner chooses to share them.
  • We never edit a published edition.

Questions about a number?

Tell us what you found and where. Write to [email protected]

Open the Rust report