ShotFire

The window to join ShotFire is 11:00–15:00 UTC, when it averages 4 concurrent players — well clear of its 2-player round-the-clock average. It bites hardest at 12:00 UTC, averaging 6. Outside it the city empties: across 01:00–11:00 UTC it averages just 0 players, so an off-peak login means an all-but-empty server.

Its 120 slots are far more than it uses: when anyone is on it, it averages 2 players, and the busiest single moment of the week reached only 19 — 16% of capacity. Day to day it barely moves: across those 7 days its daily averages stay within 596% of each other, so this is a settled population rather than a spike.

That puts ShotFire ahead of 93% of the 42,434 FiveM servers ViceHub tracked consistently this week, ranked on peak concurrent players. That is measured from our own five-minute checks, not from anything the server claims about itself.

ShotFire loads 30 resources (a lean build), and none of the usual framework cores — ESX, QBCore, Qbox, vRP — are among them, so it is running standalone or on a custom base, with pma-voice for voice.