Measuring…
The verdict appears after a few seconds of measurement.
Comparing with other tests to this server…
The test below is already running at 30 Hz, the tick rate of Call of Duty: Mobile. No click, no signup.
Measuring…
The verdict appears after a few seconds of measurement.
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 |
|---|
Getting blank shots with your sniper? Dying two seconds after sliding behind cover? Ping locking at exactly 199ms?
Call of Duty: Mobile exchanges small updates with its servers about 30 times per second; that is the rate this test uses. Slide-canceling, fast strafing and hit registration depend on those updates arriving on time. When packets go missing, the server has to guess your position, and you see desync, rubber-banding or ping spikes to 199 ms and above. On a phone, the usual causes are Wi-Fi-to-mobile switching and weak signal. A speed test does not show these. Run this test for a minute on the same network you play on.
What this test sends: 30 packets per second of 100 bytes, matching Call of Duty: Mobile rather than a generic ping. estimated
Activision publishes no figure for the mobile title; 30 Hz is the community estimate.
Run the 30Hz test above for at least 60 seconds. Here is what your results mean for COD Mobile:
Red vertical lines mean your connection dropped data entirely. In CODM, this causes "Blank Shots" (Ghost Bullets). You shoot an enemy, hear the gun fire locally, but no hitmarker appears on your crosshair and they take zero damage. It also triggers the yellow/red Wi-Fi warning icon on your HUD.
Jitter is ping fluctuation. If your ping rapidly bounces from 30ms to 90ms, your movement will rubberband. You will slide through a doorway, only to be snapped back outside into the line of fire. High jitter makes tracking fast-moving enemies with fully automatic weapons nearly impossible.
High baseline ping is the core cause of "Desync" and Peeker's Advantage. Because the game relies heavily on lag compensation, an aggressive enemy with 20ms ping can swing a corner and shoot you before their character model even renders on your screen. You will constantly die after ducking behind hard cover.
If the tool above shows packet loss or high jitter, try these specific fixes.
The Symptom: Your ping randomly spikes to exactly 199ms for a few seconds, then drops back to normal.
Smartphones actively try to switch between Wi-Fi and 5G/LTE if the signal drops even slightly. During this handoff, your connection to the Activision server drops all UDP packets, causing a freeze in-game.
The Symptom: Constant stutter and blank shots while using Bluetooth headphones.
The standard 2.4GHz Wi-Fi band shares the exact same frequency as Bluetooth headphones and controllers. This causes radio interference and dropped packets.
The Symptom: Ping spikes to 100ms+ randomly during a match.
Your 30Hz CODM packets are being choked because Instagram is refreshing feeds, or CODM itself is secretly downloading HD Resource Packs in the background.
The Symptom: You are placed in your normal regional server (e.g., NA or EU), but your ping sits permanently at 80ms+.
CODM servers are hosted on large cloud networks (AWS, Tencent Cloud). Sometimes your ISP or cellular provider takes a terrible, highly congested routing path to these datacenters.
What you see in game, and which number on this page explains it.
| What you see in Call of Duty: Mobile | Look at | What it means |
|---|---|---|
| Shots register a full beat after the target has moved | ping | Distance to the regional server, added to the tick interval. |
| Sudden freeze then a jump forward, once or twice a match | loss | A run of dropped updates followed by a correction. |
| Ranked feels worse than casual on the same line | route | Different matchmaking, different datacentre. Test more than one server above. |
| Worse when the phone is warm and the room is unchanged | jitter | Radio performance drops as the device throttles. Compare against a wired device. |
Activision publishes no tick rate for Call of Duty: Mobile, so the 30 Hz used here is an estimate for a mobile shooter of this class and is marked as one. What is not an estimate is the demand the game makes on timing: it is built to feel like its console siblings, with the same short time-to-kill, and a short time-to-kill is the mechanism that turns small network faults into lost fights.
Fifty to a hundred milliseconds decides most exchanges in this game. That is roughly one to three server updates, so the difference between winning and losing a duel can be a single packet that arrived late. Nothing about that is visible while it happens - the player sees an opponent who was faster, and the real reason is that their information about the world was more recent.
The traffic is about 100 bytes per update, which no connection struggles to carry. The struggle is in delivery. A phone shares its radio link with everyone else on the cell, and a home Wi-Fi network shares its channel with every neighbour on the same one; both produce exactly the pattern that hurts here, which is short bursts of loss rather than a steady rate.
Because the game runs on a device that also throttles when it heats up, the useful discipline is to measure on the same phone, in the same place, at the moment the game feels bad. A test from a laptop on the same network proves nothing about the radio link the phone was actually using - and that link, not the provider, is where most of the packet loss in this game is found.
199ms is the hard-capped display limit that CODM uses to indicate severe network failure. It doesn't mean your ping is literally 199ms; it means you are experiencing 100% packet loss and have temporarily disconnected from the server. This is usually caused by your phone switching between Wi-Fi and Cellular data mid-match.
Blank shots are caused by packet loss. Your local game client registers the shot, plays the firing animation, and consumes ammo. However, the data packet carrying that bullet was dropped by your internet before it reached the 30Hz server. The server rejects your shot because it never received the data.
This is a combination of Desync, the game's 30Hz tick rate, and lag compensation. If an enemy with higher ping shoots at where you used to be, the server "rewinds" time to check if they aimed correctly on their screen. If they did, it grants them the kill, even if you already slid behind cover on your screen.
For competitive Ranked Multiplayer, you want your ping strictly under 40ms. Once your ping exceeds 60ms, close-quarters gunfights become a coin flip, as the server will start rejecting your inputs in favor of players with faster connection times.
See the tick rate and packet size of all 570 supported games →