Both FiveM Player Numbers Are Frozen Files, and We Used One

FiveM publishes two player numbers in public, and both of them are frozen files. The homepage says 120,520. A JSON endpoint says 297,210. The homepage file has not changed for 22 days. The JSON file has not changed for 402 days. Neither is a live count, and one of them is a number this site has printed as though it were. That last part is why this article exists. The correction to this site's own reporting is in the third section, stated plainly. The second frozen file, which is the new finding CONFIRMED. This desk's editor fetched https://runtime.fivem.net/counts.json and received HTTP 200 at 19 bytes at 2026-09-25T03:17:47Z. The entire body, verbatim: [null,297210,null] The response header, verbatim: last-modified: Mon, 18 Aug 2025 13:23:01 GMT That is a last-modified date of 18 August 2025. This desk's own arithmetic: the file has been unchanged for 402 days and about 14 hours as of the fetch timestamp above. A three element array with two nulls and one integer, served with a last-modified header from last August, is a static artefact. It is not a counter. The homepage file CONFIRMED. https://fivem.net/ answered HTTP 200 at 36,711 bytes at 2026-09-25T03:17:47Z, with this response header verbatim: last-modified: Wed, 02 Sep 2026 09:08:05 GMT The page hardcodes the string "120,520 online now" directly into its markup. This desk's editor computed the md5 of the body as 9fd3479480306f1ab33638907be8befc, which is also the prefix of the etag the server itself sent, etag "9fd3479480306f1ab33638907be8befc:1788340123.205313". The server's own cache identifier and this desk's own hash of the delivered bytes agree, which is a useful independent check that the file served is the file measured. This desk's own arithmetic: the homepage file has been unchanged for 22 days and about 18 hours. SourceNumber shownLast-ModifiedUnchanged for, this desk's own arithmeticBytes fivem.net homepage120,520Wed, 02 Sep 2026 09:08:05 GMT22 days, about 18 hours36,711 runtime.fivem.net/counts.json297,210Mon, 18 Aug 2025 13:23:01 GMT402 days, about 14 hours19 This desk's own arithmetic: the 297,210 in counts.json is 2.47 times the 120,520 on the homepage. Two public numbers from the same organisation differ by a factor of nearly two and a half, and neither has moved in weeks or months. Correcting this site's own reporting This site has published the 120,520 figure as a FiveM population number, including in the platform snapshot piece. That was wrong in a specific way, and the specific way matters. That digit string is hardcoded into a static page whose last-modified header reads 2 September 2026. So it was already about three weeks stale at the point this site printed it, and it was never a live count at any moment during this site's use of it. Presenting it beside same-day Steam and Twitch samples implied a currency it did not have. This desk is recording that plainly rather than quietly dropping the figure from future pieces. This site has separately covered the homepage number being a static file, in the static file piece. What is new today is the second frozen file, the 402 day figure, and the collision between the 120,520 this site printed and the 297,210 the platform's own JSON endpoint has been serving since August 2025. So what is the real number This desk does not know, and that is the honest answer. No live FiveM population figure was obtainable. REPORTED, not confirmed. A researcher on this desk reported five further endpoints, tried in search of a live counter, all returning HTTP 404. This desk's editor did not re-run those five, so they are carried as reported. What the editor did confirm is the two files above, and neither of them is live. The position this desk is taking, and stating so that nobody has to guess: this desk cannot currently give a reader a verified live FiveM player count. The correct response to that is to say so, not to substitute whichever of these two frozen numbers looks most plausible. A stale number presented as current is worse than no number, because it travels and gets cited. How to check a number like this yourself The technique in this article is simple and generalises to any figure on any website. Request the page or endpoint and read the last-modified and etag response headers. If the header is weeks or months old and the number is baked into the delivered bytes rather than fetched by a script after load, the number is as old as the file. A live counter will either arrive from a separate request that you can watch in a network inspector, or it will change when the file changes. A second check, for the sceptical: hash the body yourself and compare it against the etag the server sent. If they match, as they did here, you know the bytes you measured are the bytes the origin intends to serve, rather than something a cache mangled on the way to you. Why this matters before 19 November With 55 days to 19 November 2026, which is this desk's own arithmetic, FiveM population figures are going to be quoted constantly, in arguments about whether roleplay players will move to Grand Theft Auto VI, in arguments about whether the platform is declining, and in coverage of the Enhanced build migration. Two of the most quotable numbers available are static files. Anyone building a trend line out of them is building it out of nothing. Limits, and what this desk could not check A last-modified header describes the file as the CDN serves it, and it is not proof about what the underlying service knows or measures internally. Cfx.re may well have accurate live telemetry that it does not publish through either of these two routes. Nothing above speaks to that. Neither number is labelled on FiveM's own pages as live or as a snapshot. The homepage phrasing is "online now", which reads as current, but the page does not claim the figure updates and this desk did not find such a claim. counts.json carries no label at all, being a bare array. This desk is not alleging that Cfx.re is misrepresenting anything. Stale marketing copy on a homepage is an extremely common condition of the web, and an old JSON file on a runtime host is more likely a leftover than a deception. The error this article corrects is this site's own, for treating a static figure as a measurement. The five additional endpoints are reported rather than confirmed, so this desk cannot say that no public live counter exists. It can say only that it did not find one, and that the two public numbers it did find are both frozen. Finally, the 22 day and 402 day figures are computed against the fetch timestamp of 2026-09-25T03:17:47Z. They grow by one day per day, and any reader repeating them later should recompute rather than reprint.