- Public profile sample
- 371Season 2 profiles used for progression and ownership
- Median Wardog level
- 50Average 52.5; highest recorded 147
- Recorded matches
- 10One connected community server; separate sample
- Distinct match participants
- 1,282Anonymous participant totals, not tracked public profiles
Season 2 progression: the middle of this sample was level 50
146 of 371 profiles (39.4%) were below Wardog level 40, while 30 (8.1%) had reached level 100 or higher. The average level, 52.5, sat above the median of 50. That describes the spread of this tracking sample; it does not show how quickly a typical WARDOGS player levels up.
Median recorded career XP was 176,426. Wardog level and career XP are separate recorded profile fields; the class XP calculator should not be applied to this Wardog-level histogram. The sample's top-10% level threshold was 96, but ties mean this is not an exact count of players above a fixed percentile.
Each percentage below uses all 371 sampled public profiles. Counts are exact to the saved aggregate response; percentages are rounded to one decimal place.
| Wardog level | Public profiles | Share of sample |
|---|---|---|
| 0–19 | 70 | 18.9% |
| 20–39 | 76 | 20.5% |
| 40–59 | 70 | 18.9% |
| 60–79 | 72 | 19.4% |
| 80–99 | 53 | 14.3% |
| 100–119 | 21 | 5.7% |
| 120–139 | 7 | 1.9% |
| 140–159 | 2 | 0.5% |
Sources: [1] WD Stats public Season 2 progression and ownership aggregates
Main classes reflect accumulated XP, not current class picks
Assault led with 112 mains (30.2% of all sampled profiles). Recon followed with 79 (21.3%). A main is the class with a profile's highest positive recorded class XP. Equal XP is resolved by internal role name order.
8 profiles (2.2%) had no positive class XP and therefore no main. They remain in the percentage denominator. The positive-XP column counts profiles with any recorded XP in each class, so one profile can appear in several class rows.
These figures do not measure current playtime, loadout choices, class strength or win rate. They cannot establish that a class is overpowered or preferred in every mode.
| Class | Main profiles | Share of all profiles | Profiles with positive class XP |
|---|---|---|---|
| Assault | 112 | 30.2% | 353 |
| Recon | 79 | 21.3% | 331 |
| Support | 61 | 16.4% | 331 |
| Medic | 47 | 12.7% | 355 |
| Driver | 35 | 9.4% | 288 |
| Pilot | 29 | 7.8% | 233 |
| No positive class XP | 8 | 2.2% | Not applicable |
Sources: [1] WD Stats public Season 2 progression and ownership aggregates
Weapon unlock ownership: what the recorded rates mean
Galil was recorded on 139 of 371 profiles (37.5%), followed by MP5 on 120 (32.3%). The table shows the ten most widely recorded weapon unlocks, ordered by owner count; these item identities were checked against the site's progression catalog.
Here, an ownership rate means owners divided by all 371 sampled profiles, including profiles with no recorded items. It does not mean acquisition speed, purchase conversion, equipped share or usage. A single snapshot cannot show how long an unlock takes or whether an update changed demand.
The complete download contains 225 observed item identifiers, including cosmetics and other equipment. The public ownership endpoint only lists items recorded on at least one profile; an absent item is not evidence that it is unobtainable. No unobserved item was assigned a zero rate.
| Weapon unlock | Recorded owners | Recorded ownership rate |
|---|---|---|
| Galil | 139 | 37.5% |
| MP5 | 120 | 32.3% |
| SKS | 116 | 31.3% |
| Mosin Nagant | 109 | 29.4% |
| T-21 | 81 | 21.8% |
| RPG-7 | 80 | 21.6% |
| GGX 17 | 77 | 20.8% |
| Judge | 58 | 15.6% |
| TCX-SPR | 45 | 12.1% |
| SVD | 44 | 11.9% |
Sources: [1] WD Stats public Season 2 progression and ownership aggregates
Community matches: a separate, limited Season 2 observation
The season-specific public endpoint for one connected UK community server records 10 matches, 1,282 distinct participants and 8,096 scoreboard kills. That is 809.6 recorded kills per match across this sample. It is not a per-player kill rate.
The earliest recorded match started on 2026-10-15 11:36:04 UTC; the latest started on 2026-10-17 01:03:33 UTC. The gap between that latest match and this report's capture means these figures do not describe a complete first week or activity through 22 October. They do not establish that no matches occurred after the last recorded start.
Summed participant time was 1,226.5 participant-hours. This adds time across participants and is not match duration, server uptime or unique hours of observation. Distinct participants cannot be divided by match count to estimate average attendance.
Anonymous server aggregates can include participants without a WD Stats account and people whose profile or combat details are hidden. Deleted participant data is removed while match records can remain. No player identifiers, individual match records or cross-sample identities are included in this report.
Only season-specific totals for the listed server are used here. The discovery endpoint also returns cumulative network totals that can include historical servers; those totals were deliberately excluded from the Season 2 calculations. This is not a census of official or community servers.
| Measurement | Observed value |
|---|---|
| Connected servers in this sample | 1 |
| Recorded matches | 10 |
| Distinct retained participants | 1,282 |
| Recorded scoreboard kills | 8,096 |
| Recorded kills per match | 809.6 |
| Summed participant time | 1,226.5 participant-hours |
| Earliest match start (UTC) | 2026-10-15 11:36:04 UTC |
| Latest match start (UTC) | 2026-10-17 01:03:33 UTC |
Sources: [2] WD Stats season-specific connected-server aggregates; [3] WD Stats connected-server discovery response
What this snapshot can and cannot tell us
The progression and ownership tables describe a self-selected tracking sample. Profiles must be public and have fetched statistics for the reported season. Hidden profiles are excluded; paused or older fetched profiles can remain. There is no random sampling or known coverage percentage of the total game population.
The newest included profile sync was 2026-10-22 21:52:19 UTC. This is the maximum profile timestamp, not the time every profile was refreshed. Aggregates can be cached for up to ten minutes, and the source endpoints were fetched sequentially; their individual retrieval times are recorded below.
Career progression uses the season recorded with each fetched profile. Community match attribution uses configured UTC season boundaries and the match start time. These sources cannot be joined into a single player sample from the aggregates provided.
This report offers a reproducible baseline for later observations. It makes no claim about growth, population-wide preferences, balance changes or cause and effect. Later comparisons must use the same definitions and disclose changes in sample membership, visibility, collection coverage and freshness.
Sources: [1] WD Stats public Season 2 progression and ownership aggregates; [2] WD Stats season-specific connected-server aggregates
Calculation and reuse notes
Level share = profiles in the level band ÷ 371 × 100. Main-class share = profiles whose highest positive class XP is that class ÷ 371 × 100. Item ownership rate = recorded owners of the item ÷ 371 × 100.
Recorded kills per match = 8,096 ÷ 10. Participant-hours = 4,415,257 participant-seconds ÷ 3,600. Fractions are calculated from counts, not by averaging rounded source percentages. The CSV preserves raw counts and unrounded derived values.
The JSON download contains only public aggregate endpoint responses, their retrieval times and SHA-256 hashes of each normalized JSON payload. The CSV uses one row per metric, with its unit, denominator, source and observation window. The saved files are the reproducible source for this article; live source links may now show different values.
For a wiki, community post or video, link the report and state the season, capture date, sample size and relevant coverage limits. Keep the progression and community samples separate. If quoting a percentage, retain its denominator. The citation below identifies this fixed observation.
Sources: [1] WD Stats public Season 2 progression and ownership aggregates; [2] WD Stats season-specific connected-server aggregates
Sources
- WD Stats public Season 2 progression and ownership aggregates
Retrieved: .
Public tracked profiles only. The saved response includes the returned season, sample count, newest sync, histogram, classes and observed item ownership.
- WD Stats season-specific connected-server aggregates
Retrieved: .
Season 2 match and retained participant totals for one public server. Timestamp bounds are match starts, and seconds are summed participant time.
- WD Stats connected-server discovery response
Retrieved: .
Used to identify the server cohort. Cumulative network totals are retained for provenance but excluded from every Season 2 calculation.
Downloads
How to cite
WD Stats. “WARDOGS Season 2 in numbers: 22 October 2026.” Aggregate snapshot captured 2026-10-22 21:55:49 UTC. Progression sample: 371 public profiles; community sample: 10 recorded matches on one server, 2026-10-15 11:36:04 UTC to 2026-10-17 01:03:33 UTC. https://wdstats.co.uk/reports/season-2-2026-10-22