AzureCity-3.1

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

You can walk straight in: when anyone is on it, it averages 15 players against 120 slots (12% full), and even its busiest moment of the week, 60 players, left 50% of the server free. It is thinning, though: it averaged 14 players across 18 Jul–20 Jul, down 17% on the 16 it averaged across 14 Jul–16 Jul.

That puts AzureCity-3.1 ahead of 97% of the 42,379 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 526 resources loaded — a heavy build, using pma-voice for voice and ox_inventory for inventory.