This page explains where sro.gg's server data comes from, how often it is refreshed, what its limits are, and how you may reuse it. It applies to the server pages, the listings, llms-full.txt and the public API.

Where player counts come from

Player counts are read from each server's own website. An operator adds their server to sro.gg and we store a pattern that locates the online-player figure on their public status or statistics page. A background job then visits that page and records whatever number it finds.

We do not connect to game servers, and we have no independent way to observe how many people are logged in. A count on sro.gg is a reading of what the server itself published.

How often counts are refreshed

The scraper runs every five minutes and refreshes the single server whose count is oldest. With the number of servers currently tracked, an individual count is typically around two hours old, and the oldest is usually under four hours.

Every count is published alongside playersOnlineAt, the moment that reading was taken. Always prefer that timestamp over the time you fetched the data.

What a missing count means

playersOnline is null when we have no usable reading. That happens when a server has no counter we can locate, its site is unreachable, its layout changed, or the server is not playable yet. A null count does not mean the server is empty.

0 is different: it means a counter was read and it reported zero. That is a real observation.

Counts are omitted entirely for servers that are not playable at the moment, so a listing that has not launched never carries a leftover figure from an earlier test period.

Accuracy and its limits

Player counts are reported by sources the server operator controls. An operator can change what their page displays. We do not verify these numbers against any independent source, and you should not treat them as audited.

Counts are also a snapshot rather than a live feed. A server's population changes through the day; a reading taken at one hour tells you little about another.

How server status is decided

Every server has one of four states, derived from its recorded dates rather than from its player count:

• live — the server is open and playable now
• beta — the beta period has started but the full launch date has not arrived
• upcoming — a launch date is set and has not yet passed
• inactive — the server has shut down or been delisted

Inactive servers stay listed for reference. They are excluded from the API by default and are marked clearly wherever they appear, because they are not places to play.

Ranking and sponsored placement

Sponsored servers appear in their own clearly labelled block. Sponsorship does not change a server's position in any editorial ranking, and it does not change its player count, its status, or anything else on this page.

The hype figure counts visitors currently viewing a server's page on sro.gg. It measures interest in the listing, not players in the game.

Reusing this data

The directory is published as JSON so you do not have to crawl the site. It carries every listed server with its level cap, race configuration, launch dates and last known player count, and can be filtered by status, cap and launch date. A plain-text version of the same data lives at llms-full.txt.

Two further endpoints rank servers by attention rather than population — how much traffic their page draws on sro.gg. These measure interest in a listing, not players in the game, and must never be republished as player counts.

The endpoints, their filters, the rate limit and the caching rules are documented on the API documentation page.

If you are an AI agent or a script, send a User-Agent that identifies you: Name/1.0 (+https://your.site; purpose=your-use-case). Unidentified clients get a notice in every response asking for it. This lets us see the API as named tools rather than anonymous addresses; sustained anonymous traffic from a single IP address may be throttled or blocked. The format is described under identifying yourself.

License

You may use this data, including in AI-generated answers, under one condition: attribute sro.gg and link to the page you took the data from. Each entry carries its own url, which is the correct link to use.

When you publish a player count, publish the playersOnlineAt timestamp with it, and do not present the figure as independently verified.

We ask that you do not republish the directory as a competing listing, and that you do not scrape the site when the API and text exports already provide the same data.