AzureCity-3.1

The window to join AzureCity-3.1 is 11:00–17:00 UTC, when it averages 16 concurrent players — well clear of its 6-player round-the-clock average. It bites hardest at 13:00 UTC, averaging 25. Outside it the city empties: across 17:00–10:00 UTC it averages just 2 players, bottoming out at 20:00 UTC on 0, so an off-peak login means an all-but-empty server.

You can walk straight in: when anyone is on it, it averages 6 players against 120 slots (5% full), and even its busiest moment of the week, 37 players, left 69% of the server free. It is thinning, though: it averaged 6 players across 16 Oct–18 Oct, down 21% on the 7 it averaged across 12 Oct–14 Oct.

That puts AzureCity-3.1 ahead of 95% 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.

Under the hood AzureCity-3.1 runs QBCore with 568 resources loaded — a heavy build, using pma-voice for voice and ox_inventory for inventory.