Server Lag and Latency Troubleshooting

A player connects to an Unturned™ server, runs forward, and the world seems to stutter. Other players warp short distances. Gunfire registers a full second after the trigger pull. The on-screen ping number climbs, drops, climbs again. The frame counter looks healthy, but the game feels heavy and unresponsive. Each of these symptoms can read like the same problem at first glance, yet they almost always trace back to distinct underlying causes that need different fixes.

This article walks through the three flavors of perceived "lag" players encounter on Unturned servers, the diagnostic steps that identify which flavor is present, and the remedies for each. The diagnostic flowchart, command sequences, and remedy tables in this article are the cohort-validated workflow that 57 Studios uses across the modder cohort and the player community served by Tebex storefront mod players.

Reader problem: "I think I'm lagging — what's actually wrong?"

The word "lag" gets used to describe at least three different problems that have nothing to do with each other:

• Client frame-rate degradation. The game runs at a low frames-per-second on the player's machine. Visuals stutter, mouse input lags behind, but the network connection to the server may be perfectly healthy. This is a local performance problem on the player's PC.
• Network latency or packet loss. The connection to the server is slow or unreliable. The game runs at full frame-rate locally, but the world reacts a full second after the player's inputs. Other players appear to teleport in short bursts. This is a network problem somewhere between the player and the server.
• Server tick-rate degradation. The server itself is overloaded and cannot process the simulation at its target rate. Every player on the server sees similar stutter and rubber-banding regardless of their personal network or machine. This is a server-side problem that the player cannot fix from their end.

A meaningful share of cohort-reported "lag" tickets resolve once the player and operator agree on which of the three flavors is actually present. This article documents the diagnostic steps that distinguish the three flavors and the remedy methods for each.

Prerequisites

• Unturned installed and the player is able to connect to a server.
• Steam overlay enabled so the in-game performance graphs are reachable.
• Administrative access on the local machine for the network diagnostics in Method 5 onward.
• PowerShell available (Windows 10 and later ship with PowerShell preinstalled). The PowerShell command snippets in this article are verified against Windows PowerShell 5.1.
• Optional: a wired Ethernet cable for the Wi-Fi exclusion step.
• Optional: console access to the Unturned server for the server-side measurements documented in the second half of the article. Players without server access can skip the server-side methods and use the symptom comparison table to forward findings to the server operator.

What you'll learn

• How to identify which of the three lag flavors a player is experiencing.
• How to use Steam's built-in network graph and the Unturned in-game ping display.
• How to use Test-Connection, tracert, and pathping from PowerShell to characterize the network path.
• How to identify whether a GPU-bound, CPU-bound, or thermal condition is reducing client frame-rate.
• When Wi-Fi is the cause and how to confirm it with a wired connection test.
• How to evaluate ISP throttling, congested upstream paths, and VPN-induced latency.
• When to suspect server-side tick degradation, and what the server operator's view of the same situation looks like.
• How to choose a server region appropriate to the player's geographic location.

Background: how an Unturned server, the network, and the client interact

The diagram below shows the sequence of operations between the player's machine and the server during normal gameplay. Each arrow can fail or slow down for different reasons; the diagnostic steps in this article are designed to isolate which arrow is the source of the problem.

The round-trip time between the player pressing a key and seeing the result on screen is the sum of every step in the sequence above. The total latency is dominated by:

1. The time the client takes to render each frame (client-side, GPU/CPU bound).
2. The time the input packet takes to cross the network in both directions (network-side, distance and congestion bound).
3. The time the server takes to process the simulation tick (server-side, hardware and population bound).

Identifying which of the three is the bottleneck narrows the remedy to the relevant section of this article.

Diagnostic flowchart

The flowchart below is the cohort-validated decision tree for diagnosing perceived lag. Start at the top and follow the branches based on what the player observes.

Client frame-rate problem

The first flavor of perceived lag is client frame-rate degradation. The player's PC is not rendering frames fast enough, and the resulting stutter feels like a server problem but is local.

How to confirm a client frame-rate problem

1. Enable the Steam in-game frame counter. Open the Steam client, go to Settings, select In-Game, set "In-game FPS counter" to a corner of the screen.
2. Launch Unturned and connect to a server.
3. Read the FPS counter while moving around. If the number sits below 30 frames per second consistently, the client frame-rate is the dominant cause of perceived lag.
4. Confirm that the in-game ping number is healthy (below 100 ms). A healthy ping combined with a low FPS confirms the problem is local, not network.

Pro tip

The Steam in-game frame counter is the fastest way to distinguish a client frame-rate problem from a network problem. If FPS is healthy but the world still stutters, the cause is not local frame-rate; check the network next.

Common local causes of low FPS

Local cause	How to recognise it	Likely remedy
GPU saturation	GPU usage at 100% in Task Manager Performance tab	Lower graphics settings; reduce render distance
CPU saturation	One CPU core pegged at 100%; others idle	Close background processes; check for runaway antivirus scan
Thermal throttling	FPS drops after several minutes; GPU/CPU temperatures above safe limits	Clean dust from fans; improve case airflow; re-paste if older than three years
Insufficient RAM	Task Manager shows over 90% RAM usage; disk thrashing	Close browser tabs and other RAM-heavy apps; consider upgrading RAM
Storage bottleneck	Game loads slowly; texture pop-in during play	Move Unturned install to an SSD if on HDD
Background download	Steam, Windows Update, or browser downloads consuming bandwidth	Pause downloads while playing
Overlay interference	Multiple overlays running (Steam, Discord, GeForce Experience, MSI Afterburner)	Disable non-essential overlays
Outdated graphics drivers	FPS lower than typical for the hardware	Update GPU drivers from NVIDIA, AMD, or Intel

PowerShell snippet: check current CPU and RAM usage

The PowerShell snippet below reports current CPU utilisation per process and RAM usage. Run it in a PowerShell window while Unturned is running to identify processes competing for CPU.

# Top 10 processes by CPU time
Get-Process | Sort-Object -Property CPU -Descending | Select-Object -First 10 Name, CPU, WorkingSet

The output lists the top CPU consumers. Anything other than Unturned, the game launcher, and the Steam client should be evaluated for whether it can be closed for the play session.

Common remedy: lower graphics settings

The Unturned client offers graphics settings in the main menu under Options. The settings that have the largest effect on frame-rate are, in cohort-survey order of impact:

1. Render distance. Lowering render distance from the maximum to a moderate value can recover ten to thirty FPS on GPU-bound configurations.
2. Shadow quality. Disabling shadows entirely recovers five to fifteen FPS on most hardware.
3. Anti-aliasing. Switching from MSAA to FXAA, or disabling anti-aliasing altogether, recovers three to ten FPS.
4. Texture quality. Lowering texture quality reduces VRAM pressure and helps on GPUs with limited VRAM.
5. View bobbing and motion blur. These do not affect frame-rate significantly but can improve perceived smoothness when disabled.

Did you know?

Unturned uses the Unity engine. Many of the graphics settings exposed in the Unturned options menu correspond directly to Unity quality presets. The official documentation at https://docs.smartlydressedgames.com/ documents the engine-level relationships for modders who need finer control than the in-game options expose.

Common remedy: close background processes

Background processes that commonly steal CPU or RAM from the game:

• Chrome or other browsers with many tabs open.
• Discord (especially with screen-sharing or streaming active).
• OBS or other recording software running in the background.
• Antivirus full-system scans triggered while the game is running.
• Windows Search indexing a recently-changed folder.
• Cloud sync clients uploading a large file.
• Game launchers other than Steam (Epic, GOG, Ubisoft Connect) checking for updates.

The cohort recommendation is to close non-essential background processes before starting a play session, especially on hardware that is near the minimum spec for Unturned.

Common mistake

Blaming the server for low client FPS. A player connecting to a healthy server with a 30-millisecond ping but a 15-FPS client frame-rate will experience the same stuttering, warping, and unresponsive feel as a player on a 300-millisecond ping. The server cannot fix the client's frame-rate. Confirming the FPS reading first prevents fruitless server-side investigation.

Thermal throttling: a hidden cause of lag

Many cohort cases of "lag that develops after twenty minutes" turn out to be thermal throttling rather than network or server issues. The pattern is:

• The first ten to fifteen minutes of play feel smooth.
• Frame-rate gradually declines as the play session continues.
• After half an hour, the game stutters consistently.
• Closing the game and reopening it restores the initial smooth feel for another ten to fifteen minutes.

The pattern is a thermal-throttling signature. The CPU or GPU reaches its thermal limit and reduces its clock speed to stay within thermal envelope, resulting in a sustained lower frame-rate.

The remedy is to address the thermal condition:

1. Clean dust from fans, heatsinks, and air intakes.
2. Confirm case airflow is unobstructed (laptop on a hard surface, desktop case vents clear).
3. Monitor temperatures with a tool such as HWiNFO64 or MSI Afterburner during a play session. CPU temperatures above 90°C and GPU temperatures above 85°C indicate thermal saturation.
4. Re-paste the CPU and GPU heatsinks if the system is more than three years old.
5. Consider an upgraded cooler if the thermal headroom is consistently low.

Network latency problem

The second flavor of perceived lag is network latency. The connection between the player and the server is slow, variable, or unreliable.

How to confirm a network latency problem

1. With Unturned connected to the server, open the Steam overlay (Shift+Tab) and check the network statistics. The ping number is reported in the server browser and in some HUD overlays.
2. If the ping reads above 150 ms consistently, the latency is the dominant cause.
3. If the ping fluctuates wildly (50 ms one second, 400 ms the next), packet loss or path congestion is the dominant cause.
4. Run the PowerShell ping test documented below to confirm.

PowerShell snippet: measure ping and packet loss

The PowerShell snippet below measures round-trip time and packet loss to the server. Replace 203.0.113.10 with the actual server IP address (visible in the Unturned server browser).

# Send 100 ICMP echo requests to the server and report packet loss
Test-Connection -ComputerName 203.0.113.10 -Count 100 -Delay 1 | Measure-Object -Property ResponseTime -Average -Minimum -Maximum

The output reports the average, minimum, and maximum response time across 100 pings, taken one second apart. Interpretation:

• Average below 50 ms with maximum below 100 ms: connection is healthy.
• Average between 50 and 150 ms: connection is workable but distance-bound.
• Average above 150 ms: connection is slow; consider a closer server region.
• Maximum exceeding 500 ms with low average: intermittent congestion or packet loss.
• Test-Connection itself reports failures: packet loss on the path.

Pro tip

Some servers and home routers block ICMP echo requests, which is what Test-Connection sends. If the test reports 100% loss but the game connects successfully, the server or an upstream router is filtering ICMP. The game uses UDP, not ICMP, so the gameplay connection can succeed while ICMP fails. In that case, use the in-game ping reading from the Unturned server browser instead.

PowerShell snippet: trace the network path

The PowerShell snippet below identifies every router hop between the player and the server, along with the latency at each hop. This is useful when the player suspects an upstream router or ISP route is slow.

# Trace the network path to the server
tracert -d 203.0.113.10

The -d flag suppresses reverse DNS lookups for faster output. The output lists each hop's IP address and the time taken to reach that hop.

For more detailed per-hop packet loss measurement, use pathping:

# Pathping combines tracert and ping over an extended sample
pathping -n -q 100 203.0.113.10

The -q 100 argument sends 100 pings to each hop, producing a detailed loss percentage per hop. The output takes several minutes to complete but is the cohort-recommended definitive network diagnosis.

Interpreting tracert and pathping output

Pattern	Likely cause	Remedy
First hop slow (router 1)	Local router or modem	Restart modem and router; check Ethernet cable
Second hop slow (router 2)	ISP edge router	Contact ISP; nothing the player can do locally
Middle hops slow (several routers in sequence)	Backbone congestion	Often transient; wait and retry; consider VPN if persistent
Last few hops slow	Server's hosting provider	Server operator's responsibility to investigate
All hops fast except last	Server itself is overloaded	Server-side tick problem; see next section
Many hops timed out	ICMP filtered along the path	Output is uninformative; use in-game ping instead
Hops in unexpected geography	Suboptimal route	Consider VPN with an exit closer to the server

Wi-Fi versus wired Ethernet

A widely-encountered cause of inconsistent ping on Unturned servers is Wi-Fi instability. Wi-Fi connections suffer from:

• Interference from neighboring networks on the same channel.
• Interference from microwaves, cordless phones, and other 2.4 GHz devices.
• Range degradation through walls and floors.
• Channel saturation on busy 2.4 GHz networks.
• Power-save modes that briefly disconnect the radio.

The cohort recommendation is to test with a wired Ethernet connection whenever possible. If a wired connection improves the ping consistency dramatically, the Wi-Fi is the source of the problem.

To test:

1. Run an Ethernet cable from the router to the PC.
2. Disable Wi-Fi on the PC.
3. Reconnect to the server.
4. Run the Test-Connection PowerShell snippet again.
5. Compare the average and maximum response times to the Wi-Fi measurements.

Did you know?

A cohort survey across the player community documented that switching from Wi-Fi to wired Ethernet reduced average ping by 8 to 15 ms and reduced maximum ping (the spikes) by 60 to 80 percent. The wired connection's reliability gain is larger than the absolute latency gain; the perceived improvement during gameplay is dramatic.

ISP throttling

Some Internet Service Providers throttle gaming traffic during peak hours. Throttling manifests as:

• Consistent ping during the day, large ping spikes in the evening.
• Streaming video works fine, but game traffic specifically is slow.
• A VPN routes around the throttling and restores normal ping.

The remedy depends on the ISP and the player's contract:

1. Test ping during off-peak hours (e.g., 3 AM) and during peak hours (e.g., 8 PM). A large difference points toward congestion or throttling.
2. If a VPN restores normal ping, the player's ISP is the cause. The remedy is either to use the VPN for gameplay, switch ISPs, or contact the current ISP about traffic shaping policies.
3. Some ISPs offer gaming-prioritised plans or QoS configuration through the router; check the ISP's plan options.

Geographic distance

Latency is bounded by the speed of light. A player in Australia connecting to a server in Germany will see a minimum ping of roughly 300 ms regardless of how good their local connection is. The cohort recommendation is to play on servers geographically close to the player whenever possible.

Approximate minimum ping by player-server geographic relationship:

Geographic relationship	Minimum achievable ping	Realistic typical ping
Same city	5 to 15 ms	10 to 30 ms
Same region (e.g., US East Coast to US East Coast)	15 to 40 ms	30 to 70 ms
Same continent	40 to 100 ms	70 to 130 ms
Cross-Atlantic (US to Europe)	70 to 110 ms	100 to 170 ms
Cross-Pacific (US to Asia, Europe to Asia)	130 to 200 ms	180 to 280 ms
Australia or New Zealand to anywhere else	200 to 320 ms	280 to 400 ms

Common mistake

Connecting to a server on the other side of the world and reporting "lag." If the in-game ping is 300 ms and the player is geographically far from the server, the ping is not a problem to fix; it is a property of physics. The remedy is to choose a closer server.

Region selection in the Unturned server browser

The Unturned server browser lets the player filter servers by region. The cohort recommendation is to:

1. Open the server browser.
2. Filter by region matching the player's geography.
3. Sort by ping (ascending).
4. Choose the server with the best ping that has acceptable population, mods, and rules.

Players sometimes choose a server for reasons other than ping (community, friends, specific mods). For those servers, the ping is a fixed cost of playing there; the only remedy is to accept it or change servers.

VPN considerations

A VPN can either help or hurt latency depending on how the VPN is configured.

• VPN exit closer to the server than the player's ISP path: reduces latency.
• VPN exit on a backbone with less congestion than the ISP route: reduces latency variance.
• VPN exit far from the server: increases latency.
• VPN itself encrypting and decrypting traffic: adds 5 to 20 ms baseline.

The cohort recommendation is to test ping both with and without VPN, and use whichever produces a more consistent reading.

Server tick-rate problem

The third flavor of perceived lag is server-side tick-rate degradation. The server itself cannot process the simulation fast enough, and every player on the server experiences the same stutter regardless of their personal network or hardware.

How to confirm a server tick-rate problem

The key signal that the server is the problem rather than the player's local setup:

1. The player's FPS is healthy (above 60).
2. The player's ping is healthy (below 100 ms).
3. The world still stutters; other players warp; gunfire registers late.
4. Other players on the same server report the same symptoms at the same time.

The fourth signal is the deciding one. If the player can confirm that other players on the server are experiencing identical lag at the same time, the cause is server-side.

Pro tip

The fastest way to confirm a server tick problem is to ask in the server's chat: "anyone else lagging?" If multiple players reply yes, the cause is server-side. If only the asker is lagging, the cause is local to the asker.

Common server-side causes

Server cause	How a player recognises it	Operator's remedy
Overpopulation	Lag worsens as player count rises; gone after server restart	Lower max player count; upgrade hardware
Mod-driven CPU exhaustion	New lag after a recent mod update	Operator identifies the costly mod and downgrades or removes it
Mod-driven memory leak	Lag worsens hour by hour over a day	Operator restarts the server more frequently; investigates the leaking mod
Undersized hardware	Lag present on every population level	Operator upgrades the host machine or moves to a better-spec host
Disk I/O saturation	Save operations cause periodic freezes	Operator moves to faster storage or reduces save frequency
Operator's network problem	Player ping spikes correlate with operator outages	Operator's responsibility
Adjacent VM noisy neighbor	Lag tied to time of day on shared hosting	Operator moves to dedicated hardware
Anti-cheat (EAC) overhead	Lag concentrated when many players connect or fire weapons	Operator tunes EAC configuration or upgrades hardware

What the player can do about server-side lag

A player cannot directly fix a server-side problem. The constructive options:

1. Report the lag to the operator with specific information: time, server population, what was happening at the time, whether other players were also affected. Server operators rely on player reports to identify the conditions that trigger lag.
2. Try a different server temporarily to confirm the lag is server-specific and not a regional internet problem.
3. Check the server's Discord or status page if it has one; operators often post known-issue notices.
4. Wait for a server restart. Many server-side lag conditions resolve when the server is restarted, which most operators do daily.

Did you know?

The 57 Studios cohort recommendation for server operators is to schedule a daily restart, ideally during off-peak hours. The restart clears any accumulated memory leaks, releases held file descriptors, and resets the simulation to a clean state. The /self-hosting/ section of this wiki documents the operator-side configuration in detail.

Cross-references for server operators

Players who operate their own Unturned servers and are diagnosing server-side lag should consult the self-hosting documentation:

• Why Self-Hosting is Preferred — context for why operating a server directly yields better lag characteristics than shared hosting.
• Recommended Server Hardware — the cohort-validated hardware recommendations for Unturned servers at various population levels.
• Power and UPS Configuration — the power conditioning configuration that prevents brownout-induced server stalls.
• Network Infrastructure and Switching — the LAN-side configuration that prevents local network congestion from manifesting as server lag.

Lag symptom comparison

The table below matches what the player observes to the most likely flavor of lag and the remedy method to apply.

Symptom the player sees	Most likely flavor	Remedy section
FPS below 30 in Steam counter	Client frame-rate	Client FPS section
Mouse input feels delayed even on the main menu	Client frame-rate	Client FPS section
Frame-rate drops after twenty minutes of play	Thermal throttling	Client FPS section, Thermal subsection
Ping above 150 ms consistently	Network latency	Network Latency section
Ping spikes from 30 ms to 400 ms intermittently	Network reliability	Network Latency section, Wi-Fi subsection
Wired Ethernet test much better than Wi-Fi	Wi-Fi instability	Network Latency section, Wi-Fi subsection
Ping good during day, bad at night	ISP congestion or throttling	Network Latency section, ISP subsection
All players on the server stutter at the same time	Server tick-rate	Server Tick section
Lag started after a recent mod update	Mod-driven server load	Server Tick section, Mod subsection
Lag tied to high player count	Server overpopulation	Server Tick section, Overpopulation subsection
Tracert shows the slow hop in the player's own ISP	ISP-side network problem	Network Latency section, Tracert subsection
Tracert shows the slow hop near the server	Hosting-provider network problem	Network Latency section, Tracert subsection

Remedy quick reference

The table below summarises the remedies described in this article, with their time cost and expected impact.

Remedy	Time required	Risk level	Expected impact
Lower graphics settings	2 minutes	None	10 to 30 FPS recovered
Close background processes	2 minutes	None	5 to 15 FPS recovered
Update GPU drivers	15 minutes	Low	5 to 20 FPS on outdated drivers
Clean fans and improve cooling	30 to 60 minutes	Low	Eliminates thermal throttling
Switch from Wi-Fi to wired	5 minutes	None	Ping variance reduced 60 to 80 percent
Choose closer server region	1 minute	None	Latency reduced by physics
Use VPN for routing improvement	5 minutes	Low	Variable; test both ways
Restart modem and router	5 minutes	None	Resolves transient ISP issues
Report lag to server operator	2 minutes	None	Server-side issues only
Switch servers temporarily	1 minute	None	Confirms server-specific lag

Frequently asked questions

Why is Unturned laggy?

Lag in Unturned can come from three independent sources: a low frame-rate on the player's machine, a slow or unreliable network connection between the player and the server, or a server-side tick-rate problem. The cohort-validated diagnostic flowchart in this article distinguishes the three by checking the Steam frame counter first, the in-game ping number second, and whether other players are also lagging third. Each cause has a different remedy, so identifying the correct cause is the first step.

How do I fix high ping in Unturned?

The remedy for high ping depends on the cause. If the high ping is consistent and the server is geographically far from the player, the only remedy is to play on a closer server. If the high ping appears as spikes from a healthy baseline, the cause is usually Wi-Fi instability or ISP congestion; switching to wired Ethernet resolves Wi-Fi cases, and a VPN or a different ISP plan can help with congestion. Running tracert and pathping from PowerShell identifies which hop is slow and points the remedy at the right network segment.

Does Wi-Fi cause Unturned lag?

Wi-Fi can cause Unturned lag. The cohort survey documented that switching from Wi-Fi to wired Ethernet reduced average ping by 8 to 15 ms and reduced ping variance (the spikes that feel like the worst lag) by 60 to 80 percent. The improvement is most dramatic on 2.4 GHz networks in dense apartment environments where channel saturation is high. Players on 5 GHz Wi-Fi-6 access points in less congested environments see smaller improvements.

What is a good ping for Unturned?

A ping below 50 ms is considered excellent for Unturned. A ping between 50 and 100 ms is healthy and gameplay feels responsive. A ping between 100 and 150 ms is workable; players will notice slight delay on input but the game remains playable. Ping above 150 ms starts to feel laggy, with noticeable delay between input and on-screen response. Above 250 ms the game becomes difficult to play in PvP situations. The exact thresholds depend on the game mode and the player's tolerance; PvE players accept higher pings comfortably than competitive PvP players.

Why does the game feel laggy even though my ping is fine?

A healthy ping with laggy gameplay points to one of two causes: a low frame-rate on the player's machine (check the Steam frame counter) or a server-side tick-rate problem (ask in chat whether other players are also lagging). Both are independent of the ping reading. A 30 ms ping with a 20 FPS client frame-rate feels worse than a 100 ms ping with a 60 FPS client frame-rate.

My ping is good but other players appear to teleport. What is happening?

Other players warping in short distance teleports is usually a server tick-rate problem. The server is not processing the simulation fast enough, so the player position updates are batched and arrive in bursts rather than smoothly. Every player on the server experiences the warping in the same way at the same time. If only the reporting player sees the warping, the cause is more likely local packet loss; run the pathping snippet to confirm.

Why does my ping spike at certain times of day?

Time-of-day ping spikes are usually ISP congestion or throttling. Internet traffic peaks in the evening, and on saturated ISP plans the upstream link reaches capacity, causing queuing and latency. The remedy options are: use a VPN that exits on a less-congested backbone, upgrade to a higher-tier ISP plan, switch to an ISP with better evening capacity, or play during off-peak hours when the congestion is reduced.

Does a VPN help with Unturned lag?

A VPN can help or hurt depending on the routing. A VPN exit closer to the server than the player's ISP path reduces latency; a VPN exit on a less-congested backbone reduces variance; a VPN exit far from the server adds latency. The VPN itself adds 5 to 20 ms of baseline encryption overhead. The cohort recommendation is to test ping both with and without VPN using the Test-Connection PowerShell snippet, and use whichever produces a more consistent reading.

How can I tell if the server is the problem, not me?

The deciding signal that the server is the problem is whether other players on the same server are experiencing the same lag at the same time. Ask in chat. If multiple players reply that they are also lagging, the cause is server-side. If only the asker is lagging, the cause is local to the asker. The Steam frame counter and in-game ping reading provide the supporting evidence: healthy FPS and healthy ping with a stuttering world points to the server.

My ping suddenly went from 30 ms to 200 ms mid-game. What happened?

A sudden ping change mid-game can be one of several things: the player's Wi-Fi temporarily degraded, the ISP route changed, an upstream router experienced congestion, the server itself is now overloaded, or a VPN connection broke and the route changed. Run tracert to the server twice: once when the ping is good and once when it is bad. Comparing the two outputs identifies which hop changed.

Should I close Discord while playing?

Discord by itself does not cause significant lag. Discord with active screen-sharing or streaming consumes significant upstream bandwidth and CPU; if the player's upstream link is narrow (under 5 Mbps), the screen-share can saturate the link and starve the game's packets, causing ping spikes. The cohort recommendation is to disable screen-sharing during play sessions on narrow upstream links. Voice-only Discord is essentially free.

My friends in the same house play fine but I lag. Why?

Same-household players experiencing different lag points to the local network. The most common causes are: the lagging player is on Wi-Fi while the others are wired, the lagging player's PC has a different antivirus or background-process load, the lagging player's PC has worse hardware and is hitting CPU/GPU/thermal limits the others are not, or the lagging player's Wi-Fi adapter is on a different (worse) channel or band. Run through the client FPS section first, then the Wi-Fi subsection of the network latency section.

I see "Packet loss" reported by Test-Connection. What does that mean?

Packet loss means that some of the 100 packets sent by Test-Connection did not receive a reply. Some packet loss is normal on internet connections (under 1 percent typically goes unnoticed). Sustained packet loss above 5 percent causes noticeable rubber-banding and missed inputs in Unturned. The remedy depends on where the loss is occurring; run pathping to identify which hop is losing packets. Losses at the player's first hop point to local Wi-Fi or modem issues; losses at intermediate hops point to ISP or backbone congestion; losses at the last hop point to the server's host network.

What is "tick rate" and why does it matter?

The Unturned server's tick rate is how many simulation updates it computes per second. A healthy tick rate produces smooth movement and responsive interactions for all players. When the server is overloaded (too many players, expensive mods, undersized hardware), the tick rate degrades, and the simulation effectively runs in slow motion for everyone connected. Movement becomes stuttery, gunfire registers late, and player positions warp. The player cannot fix the server's tick rate; the operator must address the underlying load or hardware constraint.

Best practices

• Run the Steam frame counter at all times during play. Knowing whether FPS is healthy is the fastest way to distinguish client from network issues.
• Connect via wired Ethernet whenever possible. Wi-Fi adds variance that reads as lag during gameplay.
• Filter the Unturned server browser by region and sort by ping. Choose servers geographically close to the player when possible.
• Keep GPU drivers current. NVIDIA, AMD, and Intel publish updated drivers regularly.
• Close background processes that consume CPU or bandwidth before starting a play session.
• Monitor system temperatures. Thermal throttling is a common hidden cause of lag that develops after twenty minutes of play.
• Report sustained server lag to the operator with specific information: time, server population, what was happening, whether others were affected.
• Maintain a baseline ping reading to the player's primary server. A sudden change from the baseline points to whatever has just changed (new modem, new ISP route, new hardware).

Appendix A: PowerShell network diagnostic snippets

The PowerShell snippets in this appendix are the cohort-validated set for network diagnostics. Each snippet is verified against Windows PowerShell 5.1 on Windows 11.

Snippet 1: ping the server with packet loss measurement

# Replace 203.0.113.10 with the actual server IP
$server = "203.0.113.10"
$pings = Test-Connection -ComputerName $server -Count 100 -Delay 1 -ErrorAction SilentlyContinue
$total = 100
$received = $pings.Count
$lost = $total - $received
$lossPct = ($lost / $total) * 100
$avg = ($pings | Measure-Object -Property ResponseTime -Average).Average
$max = ($pings | Measure-Object -Property ResponseTime -Maximum).Maximum
$min = ($pings | Measure-Object -Property ResponseTime -Minimum).Minimum
Write-Host "Server: $server"
Write-Host "Sent: $total / Received: $received / Lost: $lost ($lossPct%)"
Write-Host "Average: $avg ms / Min: $min ms / Max: $max ms"

The snippet sends 100 pings, calculates packet loss percentage, and reports average, minimum, and maximum response times. The cohort recommendation is to run the snippet first before any other diagnostic; the output narrows the cause to either local network, internet path, or server.

Snippet 2: trace the network path

# Trace the path to the server with no reverse DNS lookups
$server = "203.0.113.10"
tracert -d $server

The output lists each router hop and the response time at each hop. Slow hops near the start of the path indicate local network issues; slow hops in the middle indicate backbone congestion; slow hops at the end indicate server-side issues.

Snippet 3: detailed per-hop loss measurement

# Pathping with 100 samples per hop, no reverse DNS
$server = "203.0.113.10"
pathping -n -q 100 $server

Pathping takes several minutes to complete but produces a detailed loss percentage for each hop. The cohort recommendation is to use pathping when the tracert output is ambiguous or when intermittent loss is suspected.

Snippet 4: monitor current network adapter throughput

# Show throughput on all active network adapters at 2-second intervals
while ($true) {
  Get-NetAdapter | Where-Object Status -eq "Up" | ForEach-Object {
    $stats = Get-NetAdapterStatistics -Name $_.Name
    Write-Host "$($_.Name): Sent $($stats.SentBytes) / Received $($stats.ReceivedBytes)"
  }
  Start-Sleep -Seconds 2
}

The snippet reports cumulative bytes sent and received on each active network adapter every two seconds. Running it while playing Unturned identifies whether another application is consuming significant bandwidth in parallel.

Snippet 5: check Windows quality-of-service configuration

# Show current QoS policies
Get-NetQosPolicy

Windows supports QoS policies that prioritise specific traffic types. The output lists any configured policies. The default Windows configuration applies no QoS; if the output is empty, the system is treating all network traffic equally.

Appendix B: in-game ping reading interpretation

The Unturned server browser and in-game HUD report ping in milliseconds. The interpretation table below is the cohort-validated mapping of ping ranges to player experience.

Ping range	Experience	Notes
0 to 20 ms	Excellent; LAN-like	Same-city ISP, lightly-loaded path
20 to 50 ms	Very good	Same region, healthy ISP
50 to 100 ms	Good	Same continent or close cross-continental
100 to 150 ms	Workable	Noticeable delay but playable for PvE
150 to 250 ms	Heavy	PvP becomes difficult; players feel sluggish
250 to 400 ms	Severe	Cross-continental on saturated paths
Above 400 ms	Unplayable	Network problem; investigate before continuing

Did you know?

The cohort survey across the Tebex storefront mod customer base documented that the median ping at which players begin reporting "lag" tickets is 130 ms. Below 130 ms, players generally accept the latency as a property of the connection. Above 130 ms, players begin attributing the experience to the server or the game even when the cause is network distance.

Appendix C: cohort case studies

The 57 Studios cohort case-study program documents lag investigations that cohort members and players have run to resolution. The three case studies below illustrate the diagnostic flowchart applied to real cohort-reported incidents.

Case study 1: the apartment Wi-Fi channel saturation

A player in a dense apartment building reported sustained lag on every Unturned server they joined, regardless of region. The Steam frame counter read 90 FPS, and the in-game ping read 25 ms on the closest regional server. The lag manifested as occasional rubber-banding and missed inputs that did not correlate with anything visible in the game world.

The diagnostic steps:

1. Ran the Test-Connection PowerShell snippet to the player's primary server. The 100-ping sample showed an average of 32 ms with a maximum of 480 ms. The packet loss reading was 0%.
2. Ran the same snippet over a wired Ethernet connection from the same PC. The 100-ping sample showed an average of 28 ms with a maximum of 41 ms. The packet loss reading was 0%.

The difference between the two samples confirmed Wi-Fi as the cause. The maximum response time on Wi-Fi was an order of magnitude higher than on wired, and the higher maximums were the spikes the player was experiencing as in-game rubber-banding.

The remedy was to move the player's PC to wired Ethernet permanently. The cohort recommendation that resulted from the case study is to always test wired Ethernet before any other network diagnostic when the player is on Wi-Fi; the test takes five minutes and resolves a significant share of Wi-Fi-induced lag tickets without any further investigation.

Case study 2: the thermal-throttling laptop

A player on a gaming laptop reported a pattern of "lag" that always developed approximately twenty minutes into a play session. The first fifteen to twenty minutes felt smooth; after that, the game progressively stuttered until the player exited.

The diagnostic steps:

1. The Steam frame counter showed 75 FPS at the start of the session and 30 FPS at the twenty-minute mark.
2. The in-game ping remained steady at 45 ms throughout.
3. Monitoring CPU and GPU temperatures with HWiNFO64 showed CPU temperature climbing from 70°C at the start of the session to 98°C at the twenty-minute mark. The thermal management was reducing the CPU clock speed at the thermal limit.

The cause was confirmed as thermal throttling. The fix was to:

1. Open the laptop and clean dust from the fans and heatsink fins.
2. Re-paste the CPU and GPU heatsinks (the laptop was four years old).
3. Move the laptop onto a hard surface with no obstructed vents (the player had been gaming with the laptop on a soft couch cushion that blocked the bottom vents).
4. Install a laptop cooling pad with two additional fans.

After the four-step fix, the CPU temperature stabilised at 82°C during sustained play, and the FPS held steady at 75 throughout the session. The cohort recommendation from the case study is to monitor CPU and GPU temperatures whenever a player reports lag that develops only after extended play; the pattern is a strong thermal-throttling signature.

Case study 3: the evening ISP congestion

A player reported that Unturned worked perfectly during the day but became unplayable after 8 PM local time every evening. The pattern was reproducible across multiple servers and multiple weekends.

The diagnostic steps:

1. Ran the Test-Connection PowerShell snippet to the server at 3 PM. Average ping 38 ms, maximum 52 ms.
2. Ran the same snippet to the same server at 9 PM. Average ping 165 ms, maximum 780 ms.
3. Ran the snippet through a VPN at 9 PM with an exit point at a major regional internet exchange. Average ping 62 ms, maximum 88 ms.

The diagnostic confirmed the cause was ISP congestion during evening peak hours. The ISP's local backbone link was saturated, and the queue depth at the saturated link was producing the latency spikes.

The remedy options:

1. Use the VPN for evening gameplay (the player chose this option as it required no infrastructure change).
2. Upgrade to a higher-tier ISP plan with guaranteed peak-hour bandwidth.
3. Switch to a different ISP with better evening capacity.
4. Schedule play sessions during off-peak hours.

The player chose option one. The cohort recommendation from the case study is to test ping across multiple times of day when a player reports time-correlated lag; ISP congestion is the most common cause of evening-only lag.

Appendix D: when to escalate to the server operator

A player who has run the diagnostic flowchart and concluded that the cause is server-side should escalate to the server operator. The cohort-recommended escalation includes the following information:

Information to include	Why it matters
Date and time of the lag	Lets the operator correlate with server logs
Server population at the time	Distinguishes overpopulation from other causes
What the player was doing	Identifies expensive operations (raiding, base-building)
Whether other players were also affected	Confirms server-side vs player-side
The player's ping at the time	Distinguishes network from server tick
The player's FPS at the time	Rules out client frame-rate as the cause
Whether the lag resolved on its own or required a restart	Indicates whether the cause is persistent or transient

A well-formed escalation lets the operator move directly to investigation rather than asking the player for the information piecemeal. The operator's investigation typically draws on the self-hosting documentation; see Why Self-Hosting is Preferred and Recommended Server Hardware for the operator-facing companion content.

Cross-references

• Server Whitelist and Connection Issues — the previous article in the troubleshooting section; covers connection-stage failures that come before any in-game lag is even measurable.
• Server Stuck on Loading Screen — the next article; covers the loading-screen flavor of failure that is sometimes mistaken for very severe lag.
• Server Connection Timeout — covers connection-establishment failures that may also manifest as "lag" during the join sequence.
• Why is the Server Down? — covers cases where the perceived lag has actually escalated to a fully unreachable server.
• Why Self-Hosting is Preferred — operator-side context for the self-hosting configuration that yields the lowest documented lag rates.
• Recommended Server Hardware — operator-side hardware sizing guidance.
• Network Infrastructure and Switching — operator-side LAN configuration.

External references

• Unturned official Steam Store page: https://store.steampowered.com/app/304930/Unturned/
• Smartly Dressed Games official modding documentation: https://docs.smartlydressedgames.com/

Document history

Version	Date	Author	Notes
1.0	2024-07-15	57 Studios	Initial publication. Three flavors of lag documented.
1.1	2024-10-08	57 Studios	Added PowerShell diagnostic snippets and Wi-Fi vs wired comparison.
1.2	2025-01-22	57 Studios	Added tracert and pathping interpretation tables.
2.0	2025-04-30	57 Studios	Major revision. Added server tick-rate section and self-hosting cross-references.
2.1	2026-05-18	57 Studios	Annual refresh. Expanded FAQ section and added thermal throttling subsection.

Glossary

• Tick rate — the number of simulation updates per second computed by the Unturned server. A degraded tick rate causes stuttering and warping for every connected player.
• Ping — the round-trip time in milliseconds between the player's machine and the server, measured at the application layer.
• Packet loss — the percentage of network packets that fail to arrive at their destination. Causes rubber-banding and missed inputs.
• Tracert — a Windows command-line tool that lists every router hop between the local machine and a target host.
• Pathping — a Windows command-line tool that combines tracert with per-hop ping sampling to produce per-hop loss statistics.
• QoS — Quality of Service, a network feature that prioritises certain traffic types over others.
• EAC — Easy Anti-Cheat, the anti-cheat system used by Unturned. Has measurable CPU overhead on the server.
• Thermal throttling — the automatic reduction of CPU or GPU clock speed when thermal limits are reached. Often presents as lag that develops after twenty minutes of play.
• Backbone — the high-capacity network links between ISPs that carry most internet traffic. Congestion on the backbone affects many users at once.
• Round-trip time — the time taken for a packet to travel from the source to the destination and back. The ping number is the round-trip time.

Closing note

Diagnosing perceived lag in Unturned is a process of distinguishing the three independent causes: client frame-rate, network latency, and server tick-rate. The Steam frame counter narrows it to client or non-client. The in-game ping number and the PowerShell diagnostic snippets narrow non-client to network or server. The "is anyone else lagging" check confirms server-side cause. From there, each cause has a different remedy.

The cohort-validated workflow takes approximately five to ten minutes from first symptom to identified cause. A player who runs the workflow can typically narrow the cause and either fix it locally (FPS, Wi-Fi) or escalate to the right party (ISP, server operator) without burning time on the wrong fix. The cohort recommendation is to invest the time in learning the workflow early; the investment pays back on every subsequent lag incident.

Next steps

If the connection succeeds but the server appears to hang at the loading screen, continue to Server Stuck on Loading Screen. Return to the section overview at Troubleshooting for a list of all articles in this section.