Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Packet loss (rubber-banding and lost progress)
Your position is server-authoritative, so when your movement packets do not arrive the server keeps you where it last agreed you were and snaps you back. On a flat plain that is an annoyance. On a cliff, on a raft, or while carrying something across the map, it is a death and an hour of work.
Jitter (tames and dinos that slide)
Your own character is predicted locally and will usually look smooth. Wild creatures and other players' tames come entirely from the server, so uneven updates make them stutter and slide while you do not. That asymmetry is the fastest way to tell a network problem from a frame rate problem.
Ping (and what a server list number hides)
The server browser shows ping, and it is a real signal - but it is not the whole story, because a nearby server that is heavily built up can perform worse than a distant one that is not. Use the ping to shortlist and the first hour of play to decide.
What you see in game, and which number on this page explains it.
Most multiplayer games hand the server a clean slate every match. ARK does the opposite: the server holds a persistent world where everything anyone builds or tames stays until it is destroyed or decays. Over months, a popular server accumulates an enormous amount of state that must be tracked, saved and replicated to clients, and none of it is visible from the server browser.
The effect on players is a slow, confusing degradation. Nothing changed on your end, your ping is the same number it always was, and the game gradually becomes less responsive. It is easy to conclude that your connection has deteriorated, and easy to spend money on that conclusion. Measuring the line directly is how you avoid that: the path and the load at the far end are independent, and only one of them is yours.
The client-side asymmetry gives you a second, immediate check. ARK predicts your own character locally, so your movement looks smooth almost regardless of the connection, while everything the server owns - wild creatures, other players, their tames - shows the truth. A world in which you glide and everything else stutters is a network diagnosis; one in which everything including you is jerky is usually the machine you are sitting at.
What makes this worth the attention is the cost of a failure. In a session-based shooter, a burst of loss costs a round. Here it costs whatever you were carrying, whatever you were riding, and sometimes a character. That asymmetry is a good argument for fixing the cheap and boring things - a cable, a router that prioritises small packets - before rather than after a long flight across the map.
If the chart above shows packet loss or high jitter, work through
these in order.
Why do I rubber-band in ARK: Survival Ascended?
Because your position is decided by the server. When your movement packets are lost, the server keeps you at the last position it agreed to and your client is snapped back to it. Sustained loss on this chart is the direct cause.
Is the lag my connection or the server?
Run this test for a few minutes while the game misbehaves. A clean chart during heavy rubber-banding points at the server - particularly a long-running one carrying a lot of structures and tames. Red lines point at your line.
Why do tames slide while my character moves fine?
Your own movement is predicted on your machine, so it stays smooth. Creatures come from the server, so they show the connection's actual quality. That difference is the clearest sign that the problem is the network rather than your hardware.
Does a low ping in the server browser mean a good server?
Only partly. Ping measures the path, not the load at the other end, and a nearby server that has been running for months with thousands of structures on it can play worse than a further one that is fresh.