Measuring…
The verdict for this game appears once the first full second of packets is in.
Comparing with other tests to this server…
Measuring…
The verdict for this game appears once the first full second of packets is in.
Comparing with other tests to this server…
Are you sure you want to delete all results?
| Date & Time | Duration | Avg Ping | Avg Jitter | Packet Loss | Actions |
|---|
Vehicles teleporting through the city? Other players sliding rather than driving?
FiveM replaces GTA Online's networking entirely with OneSync, a server-controlled synchronisation layer that lifts the player limit far past the original 32 and moves entity ownership to the server. OneSync only sends you state for entities near you - the default culling radius is a few hundred game units - which is why a busy roleplay server can feel perfectly smooth in the countryside and fall apart in the middle of Los Santos. Because everything is configured per server, two servers on the same connection genuinely behave differently.
What this test sends: 30 packets per second of 350 bytes, matching FiveM rather than a generic ping. estimated
Entirely server-dependent: OneSync configuration and the server operator decide the rate, not a publisher.
Run the test above for at least 60 seconds. Here is what each number means for this game specifically.
Loss on an RP server is what produces ghost vehicles and characters that snap between positions. With server-owned entities, a lost update means the server keeps simulating you where it last saw you.
Jitter makes traffic and pedestrians stutter. It is most visible when you drive into a dense area, because that is when the number of synchronised entities jumps.
Under 60 ms is comfortable. RP servers are often hosted in a single country, so a high ping is frequently distance rather than a fault - and this chart tells you which.
What you see in game, and which number on this page explains it.
| What you see in FiveM | Look at | What it means |
|---|---|---|
| Vehicles teleport through the city | loss | Position updates for a server-owned entity were lost; the client corrects in one jump. |
| Pedestrians and traffic stutter | jitter | Most visible in dense areas, where the number of synchronised entities jumps. |
| Only desyncs downtown | server | Entity density against the server's capacity and culling settings, not your line. |
| High ping on one RP server only | region | RP servers are usually hosted in a single country. Distance, not fault. |
FiveM does not tune GTA Online's networking - it replaces it. OneSync moves entity ownership to the server and lifts the original 32-player limit far past it, with Infinity supporting well over a hundred players on a single roleplay server. Everything that follows from that is configured per server in server.cfg: the mode, the tick rate, whether NPC population is synchronised at all, and how far away the server stops sending you updates about vehicles and objects.
That last setting is the one players feel without knowing its name. OneSync culls distant entities, sending you state only for things within a few hundred game units. It is the reason a busy server can be flawless in the countryside and fall apart in the middle of Los Santos: the countryside has almost nothing to synchronise and the city has everything, and the transition happens as you drive.
For diagnosis this changes the usual rule. On most games, two servers behaving differently on the same connection points at routing. On FiveM it points at configuration, and it is a legitimate question to put to a server's staff: which OneSync mode are you running, and what are your population and culling settings? A server running a legacy mode with aggressive population sync will desync under load no matter how good every player's connection is.
What stays yours is the same as everywhere: loss and jitter on your own line. Roleplay sessions run for hours with constant traffic, so a connection that drops a burst every few minutes will break immersion repeatedly - and unlike a round-based game, there is no natural point at which the damage resets.
If the chart above shows packet loss or high jitter, work through these in order.
The Symptom: Only desyncs downtown.
OneSync culls distant entities, so a crowded area raises the number your client has to track at once. Smooth in the hills, unplayable in the city, with a clean chart here, is a server capacity or configuration issue.
The Symptom: Desync worse than on other RP servers.
Infinity is what large servers are expected to run; legacy modes and aggressive population settings behave very differently under load. It is a legitimate question to ask the server's staff.
The Symptom: Bursts of loss with no pattern.
RP sessions are long and the traffic is constant. Wireless retries are the usual source of short bursts that break immersion at the worst possible moment.
The Symptom: Ping rises when the household is active.
QoS keeps FiveM's frequent small packets ahead of streaming and downloads on the same line.
OneSync is FiveM's replacement for GTA's original networking. It moves entity ownership to the server and lifts the 32-player limit, but it also means the server decides what state you receive and how far away it stops sending it.
Because tick rate, OneSync mode, culling distances and population settings are all configured per server. Your connection is the same; the configuration is not.
Lost or late position updates for a server-owned entity. The server keeps simulating from its last known state, and your client corrects in one jump when the next update arrives.
Almost entirely. Most roleplay servers are hosted in one country, so a high ping usually means distance. This chart shows what your line reaches to a nearby server as a reference point.