We built the timing for our own league before we hosted anyone else’s.

Pitwall didn’t start as a hosting company. It started as a Discord, a Bathurst server on Saturday nights, and a growing pile of arguments about what actually happened at turn 2 that nobody could settle, because nobody could see it.

1. 1

   enum.gg was a community first

   enum.gg started as a small Australian sim-racing community: a Discord full of people who’d rather run their own grid than wait in a matchmaking queue. We rented a box, put up a Bathurst server and ran league nights for whoever showed up. Once a session ended, the only record was whoever took a screenshot.

2. 2

   AC EVO has no timing API

   AC EVO ships no official timing or results API. No live positions, no sector splits, no way to settle who hit who at the Chase other than scrolling back through voice chat. Every league we knew ran results off a spreadsheet, a screen recording and a lot of goodwill.

3. 3

   We read the server ourselves

   Our engine reads what the server already sends to drivers, plus its own logs and result files, and turns that into positions, laps, sectors and results for every session, whether or not anyone remembered to hit record. Driver inputs (throttle, brake) are next.

4. 4

   Other admins wanted the same thing

   Once our server had live timing, real results and lap-against-lap telemetry, other league runners asked how to get it on theirs. “Decode a binary protocol yourself” isn’t an answer, so we packaged the engine, the panel and the hosting into one thing: Pitwall.