Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Packet loss (invisible by design)
In a game with hitmarkers, a lost shot packet at least announces itself as a hit that produced no damage. Squad deliberately withholds that feedback, so a lost packet and a genuine miss are indistinguishable in the moment. This chart is one of the few ways to find out which one you have been getting.
Jitter (across a long shot)
At Squad's engagement ranges, a bullet takes a meaningful fraction of a second to travel, and your target's position on the server has moved during that time. Consistent latency means your lead is repeatable and you learn it. Jitter means the target's interpolated position moves unpredictably, and the lead you learned yesterday is wrong today.
Ping (and the server browser's other number)
Squad exposes server performance to players rather than hiding it, which is unusual and genuinely useful. A server under strain performs badly for everyone on it regardless of their ping, so a low number next to a struggling server does not mean a good match. Use both figures, not just the familiar one.
What you see in game, and which number on this page explains it.
Most shooters give you a steady stream of small confirmations: a hitmarker, a hit sound, a damage number, a killcam showing what the server thought happened. Those exist for feel, but they double as diagnostics - a hitmarker with no kill is the classic sign of a connection problem, and every player learns to read it. Squad removes almost all of them on purpose, in favour of not knowing.
That makes the game more tense and much harder to troubleshoot. When you fire at a distant figure and nothing happens, the possibilities are that you missed, that you hit and they were already behind cover on the server, or that the packet carrying your shot never arrived - and there is no in-game information that separates them. Players fill the gap with belief, and 'Squad's hit registration is broken' becomes received wisdom on connections that were never measured.
The engagement ranges make it worse in a specific way. A shot across three hundred metres has real travel time, during which the server continues updating your target's position. Your client is drawing an interpolation between the updates it has received, so the figure you are leading is a reconstruction, and the accuracy of that reconstruction depends on updates arriving evenly. Steady latency you can learn and compensate for; jitter is a moving target in the literal sense.
The server side deserves equal attention, and Squad is unusually honest about it. A hundred players, their vehicles and everything they have built on one continuous map is a large simulation, and the game exposes how well a given server is coping rather than hiding it behind a ping figure. Two numbers, both visible before you join: one for the path, one for the machine at the end of it. This page measures the first properly so that the second can be judged fairly.
If the chart above shows packet loss or high jitter, work through
these in order.
Why do my shots not register in Squad?
There are two very different causes and the game does not help you tell them apart. Either your shot packet did not arrive, or your lead was wrong for a target whose position the server had already updated. Packet loss on this chart distinguishes them.
Does server performance matter more than ping in Squad?
Often, yes. A hundred players on one map is a heavy simulation, and a struggling server degrades for everyone connected to it no matter how close they are. Squad exposes that figure to players, which is worth using.
Why is there no hitmarker in Squad?
It is a deliberate design choice in favour of realism, and it has a side effect: the usual feedback that would reveal a network problem is absent. That is precisely why measuring the connection separately is more useful here than in a game that tells you when you hit.
Will lowering my ping fix long-range engagements?
Consistency helps more than the absolute number. Bullet travel time at these ranges is substantial, so what you need is a stable relationship between what you see and where the target actually is. Jitter breaks that relationship; a stable 80 ms does not.