How many people play FiveM?

FiveM’s population peaks at 19:00 UTC (224,497 players on an average day) and bottoms out at 08:00 UTC (89,496). The whole network is therefore roughly 2.5× busier in the evening than it is in the European morning. The climb is gradual and the fall is slow: there is no single “rush hour”, just a long plateau from mid-afternoon to late evening UTC as one region after another comes online.

“Average players” is the mean network-wide concurrent population during that hour, across every complete UTC day in the window. “Best observed” is the single highest 5-minute observation ever recorded in that hour — the ceiling, not the norm. Averaging is done per day first and then across days, so a day that happened to be sampled more often cannot outvote the others.

Be careful with this chart, and so are we. It currently covers 102 complete days. That is enough to state what the network did on those days and nothing else — it is not enough to claim a weekly rhythm, a trend, or a direction of travel, and we are not going to pretend otherwise while the series is this short. The underlying rollup is permanent and grows by one row per server per night, so this is the chart that will be worth reading in six months.

2 days are deliberately missing. 2026-07-11, 2026-09-14 fell across a change in our own sampling cadence (15-minute observations to 5-minute), which leaves the day unevenly sampled: more observations in the evening than in the morning. A mean over those buckets would report a population roughly 10% higher than the day actually had. We cannot repair it after the fact, so we do not publish it — the bar is left empty rather than filled with a number we do not believe.

• Framework and gametype tags are self-declared

  Nothing in FiveM verifies what a server is running. The framework split below is built from the tags server owners type into their own server.cfg, so it measures what operators SAY they run. Thousands of servers declare nothing at all — we show that bucket at full size rather than dropping it or quietly redistributing it across the frameworks, which would inflate every share you see.

• Most of the directory is empty test servers

  The Cfx list is dominated by one-click deployments that were switched on and never configured. Any average taken across all live servers is therefore mostly a measurement of how many empty boxes are running. Where it changes the story, we publish a second cut restricted to servers that have demonstrably held a real population (a recorded peak of 25+ concurrent players), and we always say which cut you are looking at.

• “root-AQ” is not Antarctica

  It is the default locale string an unconfigured fxserver ships with, and it is one of the largest single values in the whole directory. Presenting it as a region would put Antarctica in the top three countries in FiveM. It is folded into a “no region declared” bucket, together with servers that set no locale and servers whose locale is not a real country code.

• A server’s recorded history starts when we first saw it

  We can tell you when our crawler first observed a server. We cannot tell you when that server launched — those are different facts, and we never present the first as if it were the second. Nothing on this page describes server age, lifespan or churn.

• Player counts are what the server reports

  Concurrent players come from the server's own response to the Cfx directory. A server that misreports its population to look busier will misreport it to us too. This is the same number the in-game FiveM server browser shows you, which is exactly why it is the number worth tracking — but it is a report, not an audit.

What we deliberately do not publish

These are the FiveM statistics people ask for most often. We could generate plausible-looking figures for all three today. We do not, because our data cannot support them yet — and a number that looks right but is not is worse than no number.

• Uptime percentages

  Until recently the crawler only stored a row for a server when it had at least one player on it, so a missing observation is ambiguous: it means either “offline” or “online and empty”. Distinguishing those two is the entire job of an uptime figure, so we cannot compute one honestly yet. We are now recording zero-player observations, which makes uptime computable in the future — not retroactively.

• Month-over-month growth and trends

  The permanent daily rollup is days old, not months. There is no previous month to compare against, so there is no growth rate to report. Every trend line you see here is labelled with the exact window it covers, and none of them is extrapolated past it.

• Churn, survival and “% of servers still alive after 90 days”

  This needs both a reliable signal for a server dying (see uptime) and 90 days of it. We have neither. When we do, it will appear here with the window stated.

The sync, ranking and moderation rules behind every figure are documented on the methodology page.