SHOOTERATLAS
20 readings · individual UTC times

01 / Reference

WARDOGS Steam charts: 233,859 at 15:49 UTC on 4 Oct 2026, and the readings behind it

Five reads of one endpoint, Valve's own count for app 1867240, each kept with the minute it was taken. The lowest of them is 103,208 at 08:33 UTC on 1 October 2026; the highest is 233,859 at 15:49 UTC on 4 October 2026. Between those two moments the game had a morning and three evenings behind it, and that is the whole difficulty of this keyword: a chart is a claim about a line, and a reading is one point on it.

233,859our highest of five reads, 15:49 UTC on 4 Oct 2026official
103,208our lowest of five, 08:33 UTC on 1 Oct 2026official
44,560rise inside one UTC day, 00:15 UTC to 15:49 UTC on 4 Oct 2026calculated
6reads one minute apart on 4 Oct 2026, all 233,859official
232,158 / 232,970 / 233,859one hour, three instruments, three readingsthird-party

Every reading on this page, and the minute it was taken

Five moments, one endpoint, no averaging and no rounding. Four of them were taken while this site was doing something else — writing the player count page, checking the daily refresh — and the fifth is the start of a burst you can see further down.

Read from api.steampowered.com/ISteamUserStats/GetNumberOfCurrentPlayers/v1/?appid=1867240, one read per line, nothing interpolated between them.
Read atDayAccountsWhat that read was
08:33 UTC1 Oct 2026103,208Taken while the player count page was being written; that page still carries this reading.
17:19 UTC3 Oct 2026225,824The first of two reads that Saturday afternoon, taken while the daily refresh was being checked.
17:49 UTC3 Oct 2026229,586The reading the daily job wrote into this data file, thirty minutes after the one above it.
00:15 UTC4 Oct 2026189,299The first reading on the daily 00:15 UTC clock, and the one every player count page now shows.
15:49 UTC4 Oct 2026233,859The first of six reads a minute apart, all of them this same number.

All five are Valve's figure, taken from this machine, and all five are the same thing: accounts with the game running, which includes the menu, the trader, the deployment screen and the login queue. What that does and does not count against the server browser's tally is set out on the player count page — this page stays on the line, not on the definition.

is wardogs dying

That is a real thing people type, and the honest answer starts with arithmetic. Our lowest read and our highest read are 103,208 at 08:33 UTC on 1 October 2026 and 233,859 at 15:49 UTC on 4 October 2026. They sit three days and seven hours apart, and they are not the same hour of the game's day. Subtract them and you get a number; what you do not get is a direction, because a quiet Tuesday morning and a Saturday evening are two different questions wearing the same units.

The one directional figure anybody publishes for this game comes from SteamCharts, and it is a comparison it makes itself. Its own table, opened on 5 October 2026, reads 212,552.33 as the 30-day average, a change of 11,365.1 on the window before it, which is −5.08% (SteamCharts, read 5 October 2026).

Two things about that figure belong next to it. It is built out of one sample an hour rather than out of a full history — that is SteamCharts' own description of its collector, quoted below. And it is an average over a window, so it moves slowly by construction. A falling 30-day average and an evening that reads higher than the morning are both true at once, and neither one refutes the other.

Inference, ours, and labelled as inference: this page will not print a direction for WARDOGS from its own readings. Five points, taken at four different hours across four days, can show you the shape of a day. They cannot show you a month.

wardogs peak players

Every peak you meet for this game is one instrument's catch, and Valve is the reason. The company publishes a list of its own Web API methods; the list it serves without a key carries 63 of them, and exactly one returns a player count — GetNumberOfCurrentPlayers, present tense. The only entry whose name mentions anything like a history is IPlayerService.RecordOfflinePlaytime, which writes a signed-in player's own offline play time (Valve's API list, read 5 October 2026). There is no peak to look up and no series to redraw.

So the trackers do the only thing available: they read the same live endpoint on a schedule and keep the highest number they catch. wardogshub.gg describes its own method on the page it publishes it on, and the sentence is worth having in its own words:

"The highest count this site has read from Steam since Early Access opened at 16:00 UTC on 10 September, checked on every load of this page. It is a first-hand reading of Valve's figure rather than a chart's intraday high, so a tracker sampling every minute may show a few thousand more." (wardogshub.gg, read 5 October 2026)

The two all-time figures in circulation are 428,666, which that page dates to 19:44 UTC on 13 September 2026, and 402,686 on SteamCharts. Both are labelled all-time peak, and they are 25,980 apart (428,666 − 402,686, our subtraction, both re-read on 5 October 2026). The same two figures are carried on the player count page from a reading taken on 1 October 2026. This page re-read both on 5 October 2026 and they had not moved — which is the useful part: an all-time peak is not a number that drifts, it is a number that somebody has to beat.

Who samples this game, and how often they say they do

Three instruments read this game, and each one publishes how it works. That is unusual enough to spell out, because the interval is the thing that decides what a chart can show.

  • SteamCharts collects hourly, and says so in two clauses: "The collector queries the number of concurrent players on an hourly interval for every single game in the Steam catalog, and has been collecting data since July of 2012." (SteamCharts about page, read 5 October 2026) Twenty-four samples an hour-by-hour day, and the earlier two clauses together mean the peak printed there is the highest of those samples, not the highest moment.
  • wardogshub.gg reads the endpoint on every load of its own player count page, keeps the highest it has seen, and tells you how fresh what you are looking at is: its page printed "read 15:49 UTC" next to a stated 60-second cache when we opened it on 5 October 2026. How often that fires depends on how many people open the page, which is not a published number.
  • This site reads the same endpoint once a day, at 00:15 UTC, and writes the result into one data file that every player-count page reads (method and reading dates on the player count page). One sample a day is a poor chart and an excellent baseline, which is the trade this page is honest about.
  • SteamDB is the fourth name people search for, and this machine cannot read it: its chart page returned HTTP 403 on 5 October 2026, as it did on 2 October 2026. Its figures are therefore quoted nowhere on this site, and its sampling policy is not described here either — we could not open the page that might state it.

Six reads in five minutes, and three numbers in one hour

The last of our five readings was not one read. Between 15:49 UTC on 4 October 2026 and 15:54 UTC on 4 October 2026 we read the same endpoint six times, one minute apart, and every single read returned 233,859. At that hour on that day the game's population did not move at minute resolution at all.

That is worth knowing before trusting either half of the usual argument about charts. A number that holds still for five minutes will survive a ten-minute sampler intact; the dangerous gap is not inside the minute, it is in the hours between two samples, and nobody has published a reading at that resolution for this game.

Meanwhile the other hub's page, opened on 5 October 2026, displayed 232,970 with "read 15:49 UTC on 4 October 2026" printed beside it and a 60-second cache it states itself. Ours, taken in that same minute, was 233,859. The difference is 889 (233,859 − 232,970, our subtraction). Inference, ours: at least some of that gap is the cache rather than the game, since a 60-second cache can serve a reading taken up to a minute earlier, and a minute earlier the number was lower.

Add SteamCharts, whose page showed 232,158 when we opened it on 5 October 2026, and you have three figures for one game inside one hour: 232,158, 232,970 and 233,859. The distance between the lowest and the highest of them is 233,859 − 232,158 (our subtraction), and it opens up for a reason that has nothing to do with the game — an hourly collector, a 60-second cache and a live endpoint were all describing the same hour in three different ways. None of the three is wrong. Which one a chart draws depends on which instrument drew it.

What this page can be re-read on tomorrow

The reason the five readings above are worth printing at all is that they carry minutes. Anyone can take the same five and get different numbers, but not the same minutes — and a chart is only ever as good as the sampling that made it.

What it will take to turn this record into a line is patience rather than a better source: the same clock, 00:15 UTC, on one day after another. That has been running since 4 October 2026, and its first reading was 189,299 at 00:15 UTC on 4 October 2026 — which is the low end of the day, not the interesting end. Come back in a fortnight and the daily reads will say something the five on this page cannot.

Still not on the record

  • An official concurrency history. The count endpoint answers in the present tense only, and Valve's own keyless API list contains no method that returns a past player count (checked 5 October 2026). Every peak in circulation is somebody's sample.
  • SteamDB's sampling policy. Their chart page returned HTTP 403 from this machine on 5 October 2026 and on 2 October 2026, so the interval behind their numbers is not something this page can quote.
  • An hour-by-hour profile of an ordinary day. Nobody publishes one for this game. Our own record has five moments in it, and the longest continuous stretch is the five minutes described above.
  • What app 1867240 reported during the two closed beta weekends. The betas ran on a second application — app 4809930, listed as "WARDOGS Playtest" (Valve's appdetails, read 5 October 2026) — and that a main-app chart stays blank across those weekends is wardogshub.gg's account of its own readings, which this page did not re-check against a Valve series, because Valve publishes none.
  • Any per-team or per-match figure for a day's play. The two counts on the player count page, and the server-browser tally behind the second of them, are as close as the published material gets.

Every claim on this page, sorted

Every claim on this page, sorted. The five readings are ours and carry their own minutes; every third-party line carries the day it was read, 5 October 2026.
LayerWhat is in it
Confirmed officially103,208 at 08:33 UTC on 1 October 2026, 225,824 at 17:19 UTC on 3 October 2026, 229,586 at 17:49 UTC on 3 October 2026, 189,299 at 00:15 UTC on 4 October 2026 and 233,859 at 15:49 UTC on 4 October 2026, all from Valve's endpoint for app 1867240. Valve's keyless API list contains no player-count history method. App 4809930 is a separate listing named "WARDOGS Playtest".
Read off third parties232,158 live, 259,433 as the 24-hour peak, 212,552.33 as the 30-day average and −5.08% as the change on the window before it (SteamCharts, read 5 October 2026). 232,970 with a stated 60-second cache at 15:49 UTC on 4 October 2026, and the 428,666 peak set 19:44 UTC on 13 September 2026 (wardogshub.gg, read 5 October 2026). The hourly-interval description of SteamCharts' collector and the per-load description of the hub's are their own words, quoted above.
Calculated here, not published anywhere23.5% = (233,859 − 189,299) ÷ 189,299, the rise inside 4 October. 889 = 233,859 − 232,970, our burst against the hub's cached reading in the same minute. 25,980 = 428,666 − 402,686, the distance between the two all-time peaks. The reading of the three-in-one-hour spread as an instrument difference rather than a game difference.
Not confirmedAny direction for the game's population: five readings at four different hours cannot produce one. SteamDB's sampling interval, unreachable from this machine. What app 1867240 reported during the closed beta weekends. An hour-by-hour profile of an ordinary day.
Card for the WARDOGS steam charts page: 233,859 at 15:49 UTC on 4 Oct 2026, against 103,208 on 1 Oct 2026
Drawn for this page, dark or light to match. All five readings are Valve's own count for app 1867240, each at the minute printed beside it.

Common questions

Is there a WARDOGS Steam chart?

Not from Valve. The only live figure Valve publishes for the game is a present-tense count, and there is no official chart, peak or history to go with it: the API list Valve serves without a key carries 63 methods, and the only one that returns a player count is GetNumberOfCurrentPlayers, present tense (read 5 October 2026). Third-party charts exist — SteamCharts draws one — but they are built from one site's own samples rather than from a Valve series.

What is the WARDOGS peak player count?

The two trackers carry two different all-time peaks, both re-read on 5 October 2026: 428,666, set at 19:44 UTC on 13 September 2026 (wardogshub.gg), and 402,686 (SteamCharts). They are 25,980 apart, and neither can be re-checked, because Valve keeps no history for this number. The same two figures are carried on the player count page from a reading taken on 1 October 2026, and this page re-read them on 5 October 2026 and got the same numbers.

Is WARDOGS dying?

Our own record cannot say, and it is worth being exact about why. The lowest of our five readings is 103,208 at 08:33 UTC on 1 October 2026 and the highest is 233,859 at 15:49 UTC on 4 October 2026 — three days apart, and not the same hour of the day, so the two cannot be subtracted into a direction (read 5 October 2026). The only directional figure anybody publishes for this game comes from SteamCharts, whose own 30-day row read 212,552.33 average and a change of −5.08% when we opened it on 5 October 2026; that is built out of one sample an hour, which is its own limit.

Does the WARDOGS playtest count on the Steam chart?

The playtest is a different Steam application: app 4809930, listed as "WARDOGS Playtest" (Valve's appdetails, read 5 October 2026). Any chart of app 1867240 is a chart of the main game, and the two closed beta weekends are not in it — that is wardogshub.gg's own account of its readings, not something this page verified against a Valve series, because there is no series to check.

Why is the number on SteamCharts different from the number on the endpoint?

Because they are not the same reading. SteamCharts' own about page says its collector queries each game on an hourly interval, so the figure its page showed when we opened it on 5 October 2026 — 232,158 — is that collector's most recent hourly sample rather than the current minute (wardogshub.gg's page, read in the same minute, displayed 232,970 and states its own 60-second cache; reading the endpoint ourselves in that minute gave 233,859). Every one of those is a real reading. None of them is "the" number.

Where the figures come from: the Steam Web API count for app 1867240 for all five readings and the burst; Valve's published API list for what does and does not exist; the appdetails call for app 4809930 for the playtest listing; SteamCharts' about page and its app page; and wardogshub.gg's player count page. Third-party pages read on 5 October 2026, as printed beside each figure.

How many people play WARDOGS, and how many are actually in a match →

The live reading, and what the store page states →

The day it opened, and the hour →

The hub: scoring, kit prices and what runs the game →

On this page