Battle royale · universalspeedtest.com
Prueba tu conexión para PUBG: Battlegrounds en unos 20 segundos — ping, jitter, pérdida de paquetes, descarga y subida, latencia bajo carga y una puntuación de calidad de gaming. Las peleas de PUBG se resuelven a cientos de metros, así que la red decide si el jugador al que apuntabas está donde lo viste.
Indicadores de calidad de red, no garantías de rendimiento en el juego · ≈20 segundos · sin registro, sin anuncios
Test de internet para gaming
Una medición mide ping, jitter, pérdida de paquetes, descarga y subida, latencia bajo carga y estabilidad de la conexión — y luego puntúa la red para el gaming en línea. La puntuación califica únicamente tu conexión; tu tasa de fotogramas pertenece a tu hardware.
≈20 segundos · normalmente 50–200 MB de datos · sin registro, sin anuncios
Preparando el test
Calidad de gaming
—/100
——
—
Los FPS reales dependen del hardware de tu equipo.
—
Estos son indicadores de calidad de red, no garantías del rendimiento real en el juego. Las mediciones se ejecutan contra el borde de Cloudflare más cercano — los navegadores no pueden alcanzar los servidores de juego directamente, así que la latencia a los servidores de juego en este sitio es siempre orientación general, nunca una cifra medida.
El test falló
Algo salió mal al ejecutar el test.
Qué medimos
Ping is the round trip to the server and back. PUBG validates hits server-side: a shot at a player 200 metres away arrives after your ping has elapsed, so a high or swinging ping widens the gap between what you saw and what the server credits — most visible on vehicle chases and peek fights. General guidance: under 60 ms feels responsive, under 40 ms is ideal; these figures are guidance, not measurements of KRAFTON’s servers.
Jitter is ping varying between samples. In PUBG it reads as inconsistency: cover that holds one moment and betrays the next, loot that refuses to register under pressure, movement that stutters while you sprint between buildings. A steady connection beats a faster-but-jittery one. Keep jitter under 15 ms (general guidance) for fights that match what your screen showed.
Packet loss is traffic that never arrives and has to be retransmitted. Bursts during a firefight present as shots that did nothing, a character who teleports a step, or a driving sequence that snaps you back. Rare, single losses happen everywhere; repeatable loss during matches is a path problem. Target: 0%.
PUBG’s matchmaking typically selects servers by region, and Indian players commonly connect to nearby Asian options — check the network or region settings in your version for the live list, since options change. We do not measure KRAFTON’s servers; every figure on this page is general guidance, not measured game-server latency.
Señales de problemas
01
PUBG updates are large and launchers start them without asking. A saturating download fills your router’s queue and your ping rides up with it — watch this test’s “under load” row: idle clean and loaded terrible is the signature. Pause updates before a session, or enable QoS so game traffic stays first.
02
Region-based matchmaking sometimes places you outside your usual server pool — especially in less-populated queues or at odd hours. Compare this test’s idle ping with the latency you see in a match: if match numbers sit far above your test baseline, the assignment changed, not your line.
03
A PUBG round runs long enough for wireless conditions to change mid-game: interference arrives, the band gets crowded, your device roams to a weaker access point. Average ping may look fine while brief spikes cost the fight that mattered. Position and band choice are the fix.
04
Shared access networks fill up between roughly 7 and 11 PM. Run this test at 10 AM and at 9 PM from the same spot for a few days: consistent evening degradation is congestion on the line — schedule downloads off-peak and play on whichever connection measures better at your real hours.
PUBG runs well on either link, but the two fail differently. Home Wi-Fi is usually steadier if you are close to the router on 5 GHz; cellular follows signal strength and tower load wherever you are. Decide with data rather than assumption: run this test on mobile data (Wi-Fi off) and on your home network from your usual spot, then keep the connection with lower jitter, zero loss and a calmer “under load” row.
Pasos concretos
Paso 1
Run this test on the connection you play on — and on a control (mobile data, or next to the router). Note ping, jitter and under-load latency for each. You are separating the line itself from how you reach it before changing anything.
Paso 2
Disable auto-updates during play or schedule them for off-hours. If others share the line, enable QoS or SQM on the router so a background download cannot fill the queue — then retest the “under load” row to confirm the fix.
Paso 3
Ethernet removes the variable entirely. On Wi-Fi: 5 GHz only, router in the open and elevated, away from fridges and microwaves, played from where the signal is strong. Retest after each change and keep what moves jitter down.
Paso 4
Check PUBG’s network or region settings and note the server you normally land on. If match latency suddenly differs from this test’s baseline, the match pool moved — verify in settings rather than assuming your line degraded.
Paso 5
Wired idle ping above 100 ms, jitter above 30 ms while idle, or repeatable packet loss are ISP-level findings. Send your ISP this test’s numbers with time of day and region — concrete measurements get faster, more useful replies than “the game is laggy”.
A VPN detours your traffic through extra servers, which usually raises ping and adds jitter — costly in a game where a 100 m peek resolves in a fraction of a second. It can genuinely help only when your ISP’s natural route to your usual region is unusually bad. Prove it either way: run this test with and without the VPN, keep the lower and steadier numbers, and check the game’s rules on VPN use before playing through one.
Fotogramas frente a conexión
Two separate systems get blamed on each other in PUBG. Frame rate — PUBG is demanding on CPU and GPU — comes from your hardware, resolution, graphics settings, drivers and thermals: if the game itself stutters while you stand still, that is rendering, not networking. Ping is the round trip measured on this page. A faster internet plan cannot raise a struggling machine’s FPS, and a top-tier PC cannot fix a 150 ms ping. Fix each on its own side.
Todo en esta página es un indicador de calidad de red, no una garantía de rendimiento en el juego. Las partidas reales añaden carga en el servidor, cambios de enrutado, variación del Wi-Fi y el propio netcode del juego — prueba donde juegas, a la hora a la que juegas.
No medimos los servidores de PUBG directamente — cada cifra de esta página es orientación general, no latencia medida a servidores de juego.
FAQ
General guidance — not measured game-server latency: under 60 ms feels responsive, under 40 ms is ideal for peek fights and vehicle chases, and above 120 ms desync becomes obvious. Jitter under 15 ms and 0% loss matter as much as the average, because PUBG’s worst moments decide the whole match.
Because “fast” usually means download speed — and lag comes from ping, jitter and packet loss, which move independently. Run this test and read those three rows. If they are clean, compare them against the in-match latency: a large gap suggests you are being matched onto a farther server rather than a slower line.
Whichever measures steadier where you play. Run this test on both — home Wi-Fi on 5 GHz usually wins on jitter when you are near the router; strong cellular wins when the router is far or the band is crowded. Recheck at your usual playing hour before deciding.
No. FPS drops come from your hardware — CPU/GPU load, resolution, graphics settings, thermals — the game rendering slowly. Lag is the network: ping, jitter and loss, your actions reaching the server slowly. This test measures the network side; if frames stutter while these numbers are clean, lower settings and cool the machine.
Usually not — it adds a detour through extra servers, typically raising latency and jitter. The exception is bad ISP routing to your usual region; the only honest way to know is measuring with and without using this test. Keep the steadier result and check the game’s rules on VPN use first.