Metro Detroit Roleplay

The window to join Metro Detroit Roleplay is 00:00–07:00 UTC, when it averages 9 concurrent players — well clear of its 3-player round-the-clock average. It bites hardest at 03:00 UTC, averaging 14. Outside it the city empties: across 07:00–00:00 UTC it averages just 1 player, bottoming out at 11:00 UTC on 0, so an off-peak login means an all-but-empty server.

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

That puts Metro Detroit Roleplay ahead of 93% of the 42,441 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.

Metro Detroit Roleplay loads 257 resources (a substantial 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.