Battle royale & sandbox · universalspeedtest.com
Testen Sie Ihre Verbindung für Fortnite in etwa 20 Sekunden: Ping, Jitter, Paketverlust, Download und Upload, Latenz unter Last und einen Gaming-Qualitäts-Score. Bau- und Edit-Loops in Fortnite sind Timing-Spiele — dieser Test misst die Netzseite dieses Timings.
Netzqualitätsindikatoren, keine Garantie für die Leistung im Spiel · ≈20 Sekunden · keine Anmeldung, keine Werbung
Gaming-Internettest
Ein Durchlauf misst Ping, Jitter, Paketverlust, Download und Upload, Latenz unter Last und Verbindungsstabilität — und bewertet das Netz fürs Online-Gaming. Der Score bewertet nur Ihre Verbindung; Ihre Bildrate gehört Ihrer Hardware.
≈20 Sekunden · typischerweise 50–200 MB Daten · keine Anmeldung, keine Werbung
Test wird vorbereitet
Gaming-Qualität
—/100
——
—
Die tatsächlichen FPS hängen von der Hardware Ihres Geräts ab.
—
Dies sind Netzqualitätsindikatoren, keine Garantien für die tatsächliche Leistung im Spiel. Die Messungen laufen gegen die nächstgelegene Cloudflare-Edge — Browser können Game-Server nicht direkt erreichen, daher ist die Game-Server-Latenz auf dieser Site immer nur allgemeine Orientierung, nie eine gemessene Zahl.
Test fehlgeschlagen
Beim Ausführen des Tests ist ein Fehler aufgetreten.
Was wir messen
Ping is the round trip to the server and back. Fortnite is unusually ping-sensitive because two systems depend on timing: shotgun trades, where the server decides who connected first, and build/edit interactions, where your placement must land before your opponent’s shot. General guidance: under 50 ms feels responsive, under 30 ms is ideal — guidance figures, not measurements of Epic’s servers.
Jitter is ping varying between samples. In a game where you alternate between calm looting and split-second builds, a link that swings between 30 and 90 ms never lets you trust your timing: edits register late, shots feel stolen, movement desyncs during rotations. Keep jitter under 15 ms (general guidance).
Packet loss is traffic that never arrives and must be retransmitted. During a build battle it shows as placements that vanish, shots absorbed without effect, or a rubber-band that drops you off a ramp you already climbed. Rare single-packet losses happen everywhere; anything you can reproduce mid-fight deserves a fix. Target: 0%.
Fortnite lets you set your matchmaking region in the game settings (Automatic picks what it measures as nearest). Indian players typically see nearby Asian options — open your in-game settings for the live list. We do not measure Epic’s servers; every figure on this page is general guidance, not measured game-server latency.
Hinweise auf Probleme
01
Fortnite’s patches are famously large, and platform launchers happily begin them in the background. A saturating download inflates your router’s queue — this test’s “under load” row measures exactly that inflation. Pause updates before playing, or enable QoS so they cannot crowd out game packets.
02
Fortnite’s matchmaking region setting (including Automatic) decides which server pool you land in — and it can change the effective distance between sessions. Check the region in your game settings, then compare this test’s baseline against the ping shown in a match: a widening gap means you are being sent farther.
03
Wi-Fi competes with neighbours, Bluetooth devices and microwaves; brief contention adds jitter spikes that strike mid-fight while signal bars still read full. Dense apartment buildings make this worse. It is the classic “fine until it matters” network fault.
04
Shared access networks peak when everyone streams at night. Compare a morning test with a 9 PM test from the same spot: if evenings degrade consistently, that is your line under load — move downloads off-peak and play on whichever connection measures best at your actual hours.
Fortnite runs on any connection, but wireless variation hurts it twice: once in your own reactions and once in build interactions against others. Ethernet is the stable answer. Without it, play on 5 GHz close to the router, keep the channel uncrowded, and verify changes with this test — jitter and the “under load” row are the two numbers to improve, because average ping hides the spikes that cost fights.
Konkrete Schritte
Schritt 1
Run this test on the connection you play (and on an alternative — mobile data, or next to the router), noting ping, jitter and under-load latency. You are separating the line itself from the way you reach it.
Schritt 2
Set the matchmaking region deliberately instead of leaving it on a setting that may drift. Then compare this test’s ping against the in-game ping you see in a match — they should tell the same story.
Schritt 3
Pause platform updates and large downloads during play; if others share the line, enable QoS/SQM on the router so game traffic stays prioritised. Verify with this test’s “under load” row before and after the change.
Schritt 4
5 GHz only, router in the open and elevated, away from fridges, microwaves and Bluetooth gear — then retest from your playing seat. If jitter does not improve, wire the console or PC; ethernet is the only configuration that removes airtime contention entirely.
Schritt 5
A wired idle ping above 80 ms, jitter above 30 ms while idle, or repeatable packet loss are ISP-level findings. Attach this test’s results, time of day and your matchmaking region to the ticket — concrete evidence gets concrete replies.
A VPN inserts extra hops between you and the match server, so the common outcome is higher ping and more jitter — the opposite of what you want in a build fight. It can win only when your ISP’s natural route to your region is unusually poor, and that claim should be tested, not assumed: run this test with and without the VPN and keep whichever is lower and steadier. Check Epic’s and any tournament’s rules before playing through one.
Bildrate vs. Verbindung
Fortnite conversations mix up two numbers constantly. FPS is rendering speed: CPU, GPU, RAM, resolution, graphics settings (Performance Mode is a graphics setting, not a network one), drivers and thermals decide it. Ping is network round-trip time, measured on this page. Performance Mode can lift your frame rate dramatically while changing your ping by zero, and a faster internet plan will not fix a machine struggling to render the storm. Treat them as two independent dials.
Alles auf dieser Seite ist ein Netzqualitätsindikator, keine Garantie für die Leistung im Spiel. Echte Matches bringen Serverlast, Routenänderungen, WLAN-Schwankungen und das eigene Netcode des Spiels hinzu — testen Sie dort, wo Sie spielen, zu der Uhrzeit, zu der Sie spielen.
Wir messen Fortnite-Server nicht direkt — jede Zahl auf dieser Seite ist allgemeine Orientierung, keine gemessene Game-Server-Latenz.
FAQ
General guidance, not measured server latency: under 50 ms feels responsive, under 30 ms is ideal for shotgun trades and build interactions, and above 100 ms fights start resolving against you. Jitter under 15 ms and zero loss keep the timing consistent.
Check in order: a platform or game update running in the background, your matchmaking region pointing farther than usual, Wi-Fi interference, or evening congestion. Use this test before and after pausing downloads, and compare its baseline to the in-game ping to spot region changes.
Download speed affects patch downloads and streaming — not your frame rate. FPS comes from your CPU, GPU, RAM, resolution, graphics settings and thermals. In-match, what matters is ping, jitter and loss, which this test measures. Even a modest stable line carries Fortnite’s match traffic comfortably.
Ethernet — it eliminates the interference and contention that cause spikes, which matters in build fights. If you must use Wi-Fi, sit on 5 GHz near the router and use this test to compare: look at jitter and the “under load” row before and after any change.
Yes — it decides which server pool you play on, so distance directly sets your floor. Set it deliberately in settings, then sanity-check against this test: your in-match ping should sit reasonably close to this test’s idle ping. If not, the region setting or server assignment has moved.