Built by a player.
For players.

The PUBG API only serves match data for about 14 days. Every other stat site I tried treated that as the natural ceiling — you’d open a profile two weeks later and the last great squad wipe was just… gone.

I wanted a place where the data never expires. Where the kill at 312m you’ll be retelling next year still has the receipt. Where your full season — not a rolling 14-day window — counts.

That’s what PUBG.ARMY is. A collector that runs every 15 minutes, pulls each match while PUBG still serves it, and writes the kill-by-kill telemetry into a database that won’t roll it off. The longer the site runs, the harder it is to copy.

One person. Solo developer, PUBG player, runs the servers, writes the code, answers the bug reports, watches the cron at 4am.

AI tools (specifically Claude Code) accelerate the work — I’m transparent about that on the AI Transparency page. Every feature, every database schema decision, every production deploy is reviewed and shipped by a human. The buck stops with me.

No team means I move fast. It also means if something breaks at 2am, it stays broken until I’m awake. The status page is honest about it.

Most stat sites stop at what happened. The interesting questions are why — why you lose 60% of your fights inside 50m, why your squad keeps getting third-partied on Erangel, why Miramar punishes the blue zone more than any other map.

That’s where the archive gets used. Heatmaps. Squad analytics. Per-clan reports. The S42 Blue Zone Report is a first taste — 15M+ telemetry events distilled into one counterintuitive finding the official PUBG site doesn’t show you.

The roadmap lives in the changelog going forward, not backwards. Everything that ships shows up there, with a date, on the same day.