FSO Stats eighteen years of Friday nights, in a database
The logs have been sitting on ahevents.net since 2008, one frame at a time. Reading them is an afternoon's work; I got tired of that, so here's a desktop app that scrapes the lot into SQLite and puts a grid on top. Pilot careers, squad histories, frame detail, leaderboards a couple of clicks instead of forty browser tabs.
The reason it exists is head-to-head. An FSO log names both parties on every shootdown, which means your record against any one opponent is recoverable across all eighteen years. Pick a name and every engagement between you is there: which way it went, which frame, what was lost. Settle it once and for all, or find out you'd rather not have looked.
A few things that fell out of 590,741 log entries, 656 frames, 4,161 pilots:
Most career kills AKWarHwk 1,364 over 304 frames
Best rate (200+ kills) 2cmex 6.01 K/D
Iron men Dantoo 541 frames, then Steely on 540, both since Jun 2009
Bitterest rivalry AKWarHwk over JoeJoe, 33 kills. SNO over RedBrd, also 33
Bloodiest frame ever Leyte 1944, F3 749 kills
35 pilots who flew in 2009 were still turning up in 2026, which tells you something about this community.
One honest note before anyone quotes a number at me: frame kill counts include gunners. That's why 49MERLIN's 47-kill frame in the Leyte fight looks inhuman he was sitting on ship and field guns. The app doesn't hide that sort of thing, it surfaces it. Side labels are inferred from the aircraft flown (the log's own labels can't be trusted), shootdowns are written twice and de-duped, 73 events never rendered at all. It's a hand-kept record and it shows; FINDINGS.md documents every bit of it if you're the sort who checks.
Getting it running
1. Download. Grab FSOStats.exe from the releases page 47 MB, and that's everything. No Python, no installer, no dependencies. Put it wherever you like and double-click it.
Defender may flag it as a false positive on first run. Same PyInstaller single-exe heuristic as ever, not the app doing anything; restore it from quarantine, or build from source the code's all in the repo.
2. There is no sync. The database ships inside the exe, already filled: every FSO frame from August 2008 to August Storm Frame 3 on 24 July 2026, which is last Friday. 583 frames with logs across 201 campaigns, 590,741 log entries, 4,161 pilots. You don't fetch any of it, and you don't need to be online to use the app.
First launch shows a brief splash while it unpacks that database into %LOCALAPPDATA%\FSOStats a few seconds, once. Every launch after that is instant.
3. Keeping it current. The Update button sits at the bottom right. It reads the ahevents.net listing, works out which frames it hasn't got, and fetches only those. After a Friday that's one or two pages a minute at most. It's rate-limited on purpose; ahevents is a small community site and this isn't worth hammering it for.
Because the database lives in your own AppData rather than inside the exe, your updates stick. Dropping in a newer version of the exe later won't throw away what you've fetched.
4. Look at it. The Frames tab lists every frame; the toggle switches it to Campaigns if you'd rather think in three-frame events, which is how they were actually flown. Click any frame to see both teams, which side each actually fought for, and every pilot's result.
Pilot gives a career: totals, aircraft flown with a real per-type K/D, every frame, and a kills-per-year trend. Squad does the same for a unit. Leaderboards are all-time totals beside podium finishes.
And Head-to-head is the one nothing else can do pick a pilot, pick an opponent, and get every engagement between the two of them across eighteen years, which way each went and what was lost.
Every grid sorts on a left-click, filters on a right-click, and exports to CSV.
Companion to AHStats (main-arena tour stats) separate post for that one.
https://github.com/steelington/FSOStats
