What peeker's advantage is
Picture two players either side of a corner. One holds still and watches the gap. The other steps out. In many online shooters the one who moves sees the other first, even with identical connections. That head start is called peeker's advantage.
It happens because the two players learn about the same event by different routes. The peeker's own movement is drawn on their screen straight away, so as soon as they clear the corner the defender, who has not moved, is already in view. The defender learns that the peeker has moved only when the movement has been sent to the server, processed, sent back down and drawn. Every one of those steps takes time, and all of that time is the peeker's head start.
How the model works
Time 0 is the moment the peeker presses the movement key. Everything is in milliseconds, and the one-way delay on each connection is taken as half its ping.
- The peeker sees the defender after waiting for their next frame: a random time between 0 and one frame (1000 ÷ frame rate), half a frame on average. The defender is standing still and the peeker's own movement is drawn at once, so no network delay is involved.
- The defender sees the peeker after six waits in a row: the peeker's client waiting to send (random, 0 to one tick), the trip up to the server (half the peeker's ping), the server waiting for its next tick (random, 0 to one tick), the trip down to the defender (half the defender's ping), the interpolation delay (the chosen number of ticks) and the defender's next frame (random, 0 to one frame).
- The head start is the defender's time minus the peeker's time.
- Jitter adds independent random noise, normally distributed with the chosen spread, to each of the two network trips. A trip is never allowed below zero.
Averaging those waits gives an exact formula. With no jitter and equal frame rates, the mean head start is one tick interval times (1 + interpolation ticks) plus half the sum of the two pings. At 64 Hz a tick is 15.625 ms, so with 2 ticks of interpolation and 40 ms pings that is 15.625 × 3 + 40 = 86.875 ms. The page also rolls 20,000 random trials from a seeded generator and shows their mean beside the formula, so you can see them agree. The seed is in the link, so the same link always gives the same trials.
Why tick rate and interpolation matter as much as ping
Ping gets the blame, but at good connection quality it is often not the biggest part. With the defaults, both players' pings together contribute 40 ms of the 86.9 ms. The other 46.9 ms comes from waiting for ticks and from interpolation, and all of it scales with the tick interval.
Interpolation is the quiet one. To draw other players moving smoothly, a client usually shows them slightly in the past, between two updates it has already received, rather than snapping them to each update as it arrives. That buffer is commonly a couple of ticks long. It removes jerky movement, but it means the defender always sees the peeker a little late: at 64 Hz, two ticks is 31.25 ms on its own. Doubling the tick rate halves the tick waits and the interpolation together, which is why it cuts the head start from 86.9 to 63.4 ms in this model even though no one's ping changes.
Frame rate is the smallest lever. Each player waits on average half a frame for their screen to update, so the two frame waits largely cancel when both players run the same frame rate.
What players and developers can do
- Players: a lower ping helps you whichever side of the corner you are on, but you cannot change your opponent's. A higher frame rate trims a few milliseconds. Holding an angle from further back gives the peeker more distance to cover, which buys time no setting can.
- Developers: a higher tick rate shrinks every tick-based wait at once, at the cost of server processing and bandwidth. A shorter interpolation buffer cuts delay but makes movement less smooth when an update is late or lost. Placing servers close to players keeps both one-way trips short.
Nobody can remove the head start entirely while movement has to travel through a server: the information really does reach the peeker first.
Tick rate, ping, interpolation and jitter in numbers
The tables use the page's exact formula for the mean, tick interval × (1 + interpolation ticks) + ½(peeker ping + defender ping) + the frame difference, and, for the last table, its own random-trial code with seed 1.
| Tick rate | Tick interval | Tick waits and interpolation | Both pings, halved | Mean head start | Share of a 250 ms reaction |
|---|---|---|---|---|---|
| 20 Hz | 50.00 ms | 150.00 ms | 40.00 ms | 190.00 ms | 76% |
| 30 Hz | 33.33 ms | 100.00 ms | 40.00 ms | 140.00 ms | 56% |
| 60 Hz | 16.67 ms | 50.00 ms | 40.00 ms | 90.00 ms | 36% |
| 64 Hz | 15.63 ms | 46.88 ms | 40.00 ms | 86.88 ms | 35% |
| 128 Hz | 7.81 ms | 23.44 ms | 40.00 ms | 63.44 ms | 25% |
At the defaults the head start is 86.9 ms, of which 46.9 ms is waiting on ticks and interpolation and 40 ms is the two pings. Doubling the tick rate from 64 to 128 Hz cuts it to 63.4 ms without touching either ping. At 20 Hz the tick part alone is 150 ms.
Ping, one side at a time
| Peeker ping | Defender ping | Mean head start | Of which ping |
|---|---|---|---|
| 10 ms | 10 ms | 56.88 ms | 10.00 ms |
| 20 ms | 20 ms | 66.88 ms | 20.00 ms |
| 40 ms | 40 ms | 86.88 ms | 40.00 ms |
| 80 ms | 40 ms | 106.88 ms | 60.00 ms |
| 40 ms | 80 ms | 106.88 ms | 60.00 ms |
| 80 ms | 80 ms | 126.88 ms | 80.00 ms |
| 150 ms | 40 ms | 141.88 ms | 95.00 ms |
| 150 ms | 150 ms | 196.88 ms | 150.00 ms |
The peeker's ping and the defender's ping count equally, since each is a half-trip in the chain. A 150 ms peeker against a 40 ms defender gives 141.9 ms, the same as a 40 ms peeker against a 150 ms defender.
Interpolation
| Interpolation | Delay at 64 Hz | Head start at 64 Hz | Head start at 128 Hz |
|---|---|---|---|
| 0 ticks | 0.00 ms | 55.63 ms | 47.81 ms |
| 1 tick | 15.63 ms | 71.25 ms | 55.63 ms |
| 2 ticks | 31.25 ms | 86.88 ms | 63.44 ms |
| 3 ticks | 46.88 ms | 102.50 ms | 71.25 ms |
Each tick of interpolation adds one tick interval to the defender's delay: 15.63 ms at 64 Hz and 7.81 ms at 128 Hz. Going from 2 ticks to 0 at 64 Hz cuts the head start from 86.9 to 55.6 ms, the biggest drop in that column, although the page notes a shorter buffer makes movement less smooth when an update is late.
Frame rates
| Peeker frame rate | Defender frame rate | Mean head start | Against equal frame rates |
|---|---|---|---|
| 60 fps | 60 fps | 86.88 ms | 0.00 ms |
| 144 fps | 144 fps | 86.88 ms | 0.00 ms |
| 240 fps | 240 fps | 86.88 ms | 0.00 ms |
| 60 fps | 240 fps | 80.63 ms | −6.25 ms |
| 240 fps | 60 fps | 93.13 ms | 6.25 ms |
| 360 fps | 60 fps | 93.82 ms | 6.94 ms |
When both players run the same frame rate the frame waits cancel, and the head start is 86.9 ms at 60, 144 or 240 fps alike. A 360 fps peeker against a 60 fps defender gains only 6.9 ms.
Jitter
| Jitter | Exact mean without jitter | Mean of the trials | 5th percentile | 95th percentile | Width of the band |
|---|---|---|---|---|---|
| 0 ms | 86.88 ms | 86.8 ms | 75.5 ms | 98.4 ms | 22.9 ms |
| 10 ms | 86.88 ms | 87.1 ms | 62.2 ms | 112.7 ms | 50.5 ms |
| 20 ms | 86.88 ms | 90.3 ms | 51.5 ms | 135.2 ms | 83.7 ms |
| 30 ms | 86.88 ms | 96.1 ms | 47.1 ms | 158.5 ms | 111.4 ms |
The exact formula ignores jitter, but the spread opens up: the 5th-to-95th percentile band is 22.9 ms wide with none and 83.7 ms with 20 ms of jitter. The mean of the trials also creeps up, to 96.1 ms at 30 ms of jitter, because a trip cannot be shorter than zero and the clamping removes only the negative side.
Six mistakes when reading peeker's advantage
- Blaming ping alone. At the defaults the two pings are 40 of the 86.9 ms. The rest is waiting on ticks and interpolation, and all of it scales with the tick interval.
- Expecting a higher tick rate to remove the advantage. 128 Hz cuts the mean from 86.9 to 63.4 ms. The ping part and the information route through the server stay.
- Reading the mean as every encounter. Nine in ten of the trials at the defaults fall between about 75 and 98 ms, and the band widens with jitter. Any single peek can be shorter or longer than the average.
- Believing frame rate is the fix. With equal frame rates the frame waits cancel exactly. Only a gap between the two players changes the result, by a few milliseconds.
- Treating the head start as a guaranteed win. The page calls it an information gap. It says nothing about aim, reaction or position, and the comparison with a 250 ms reaction is only a yardstick.
- Applying the numbers to a particular game. Lag compensation, prediction, packet loss, asymmetric routes and clock sync are not in the model. Use it to see how the pieces trade off, not to rate a game.
Assumptions & limitations
- Ping is symmetric: each trip takes half the round-trip time.
- The tick waits and frame waits are independent and uniformly random. In real systems they can be correlated, and clients can send commands at a different rate from the server tick.
- The server sends an update to every client on every tick, with no extra processing time.
- Lag compensation, client prediction, extrapolation, clock synchronisation, packet loss and resent packets are not modelled.
- The defender is standing perfectly still and the peeker's first frame of movement is what counts as "seen". Real visibility depends on models, maps and how much of a body must be on screen.
- Jitter is normally distributed and clamped at zero, so large jitter on a short trip also raises the average a little.
How to use this simulator
- Set your tick rate, both pings and the interpolation delay you want to test. The timeline redraws at once and the 20,000 trials re-run.
- Move the reaction time slider to compare the head start with a reaction time you think is realistic. It changes only the comparison sentence.
- Press Run again to roll a fresh set of trials with a new seed, then Copy link to share exactly those trials.
- Save picture downloads the timeline with your settings and result printed underneath.
Frequently asked questions
What is peeker's advantage?
It is the head start a player gets by moving round a corner rather than holding still behind it. The peeker's own screen shows their movement at once, so they see the defender within a frame. The defender only sees the peeker after that movement has gone to the server, been processed on a tick, travelled back down and been drawn with interpolation delay. With the default settings here that gap averages 86.9 ms.
Does a higher tick rate remove peeker's advantage?
No, but it shrinks it. Tick rate sets two waits and the interpolation delay, which in this model add up to one tick interval for every interpolation tick plus one. Going from 64 Hz to 128 Hz with everything else at the defaults cuts the mean head start from 86.9 ms to 63.4 ms. The ping part, 40 ms here, does not change.
Does my own ping matter, or only the other player's?
Both, equally. The peeker's movement has to travel up to the server on the peeker's connection and down to the defender on the defender's connection, so every millisecond of either one-way delay adds to the head start. Each 1 ms of ping, which is a round trip, adds 0.5 ms, because only one direction of each player's connection is on the path.
Does a higher frame rate help the defender?
A little. The defender's frame wait averages half a frame, so going from 60 to 144 fps saves the defender about 4.9 ms. A higher frame rate for the peeker makes the head start slightly larger for the same reason, because the peeker sees the defender sooner. Next to tick waits, interpolation and ping, the frame rate is usually the smallest part.
Does this simulator say who wins the fight?
No. It measures only how long one player can see the other before the reverse is true. Who wins also depends on reactions, aim, lag compensation, prediction and many choices the server makes, none of which are modelled here. Treat the number as the size of an information gap, not a result.
Related calculators
Sources and references
- Edgegap: Netcode (glossary) — prediction, interpolation and lag compensation, and why interpolation shows other players a little late
- Edgegap: Interpolation (glossary) — why clients draw other players slightly in the past, and the delay that costs
