Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Red lines (packet loss)
At 60 ticks a single lost packet is 16.7 ms in which the server has no idea you moved. In a 64-player fight that is the difference between reaching cover and dying at it, because the server killed a version of you that was still in the open.
Jitter (stability)
Jitter above roughly 16 ms means packets are arriving out of step with the server's own tick. Enemy models stutter, and leading a sprinting target stops working. This matters more than a slightly higher steady ping.
Ping (latency)
Under 40 ms is comfortable at 60 ticks. Above 80 ms you are roughly five server updates behind, which is precisely the "killed behind cover" experience.
What you see in game, and which number on this page explains it.
DICE confirming a 60Hz tick rate at launch is more useful than it sounds, because most studios never state one. It gives you a fixed number to reason against: the server reconciles the battle every 16.7 milliseconds. Every complaint about hit registration or dying behind cover can be measured against that interval instead of argued about.
The catch is that a tick rate is a ceiling, not a guarantee. A 60Hz server can only be as accurate as the updates that actually reach it. If your connection drops a short burst of packets, the server spends that burst simulating a version of you that is standing where you used to be - and it will happily kill that version. This is why the phrase "my ping is fine" is not the same statement as "my connection is fine", and why a chart showing loss matters more than a number showing 28 ms.
Jitter interacts with the tick rate directly. If your packets arrive with more variation than the tick interval itself, the extra precision the server offers cannot reach you: updates land out of step with the ticks they belong to, and enemy models stutter rather than move. Keeping jitter under roughly 16 ms is therefore a concrete, checkable target rather than a vague aspiration.
One more Battlefield 6 specific: the RedSec battle royale mode runs at 30Hz rather than 60. That is a genuine, deliberate difference, and it means the same connection legitimately behaves differently between the two modes. If only one of them feels mushy, you have found the tick rate, not a fault.
If the chart above shows packet loss or high jitter, work through
these in order.
What is Battlefield 6's server tick rate?
60Hz on official multiplayer servers, confirmed by DICE at launch. The RedSec battle royale mode runs at 30Hz.
Why do I die behind cover in Battlefield 6?
The server resolved the shot against a position you had already left. Latency causes some of it by design; packet loss makes it far worse, because the server never learned you moved at all.
Is 60Hz enough for competitive play?
It is one update every 16.7 ms, which is fine for the scale Battlefield plays at. Your own jitter matters more: if it exceeds the tick interval, the extra server updates do not reach you in time to be useful.
Does packet loss cause the rubber-banding?
Yes. Rubber-banding is the server correcting your position after it stopped hearing from you. A high but steady ping does not cause it; missing packets do.