Zombie Land
Store

Connection Test

WinMTR

Your data makes a dozen stops between your PC and our server. WinMTR shows which stop is losing it. It is free, takes 10 minutes, and gives you proof you can hand to your internet provider or to us.

Back to Performance

Do this only for connection lag: rubber banding or snapping back while your FPS is fine. For low FPS or freezing, go back to Fix Your FPS. Try the quick fixes first too. A network cable solves most of these without any test.

Run The Test

Five steps. The only slow one is waiting for the test to collect data.

Download WinMTR

1 minute
  1. Get it from the project page on SourceForge. The file is WinMTR-v092.zip.
  2. Right click the zip and choose Extract All.
  3. Open the 64 bit folder and double click WinMTR.exe.

There is nothing to install. It is free and open source. Avoid copies from other download sites.

Copy the server address

10 seconds

Pick the server you play on. Use the address without the :28015 on the end.

Zombie Land 1x Monthly
216.39.241.162
Zombie Land 3x PvE
185.199.95.46

Start it, then go play

10 minutes
  1. Paste the address into the Host box.
  2. Press Start.
  3. Leave it running and play Rust on that server for about 10 minutes.

The test only catches a problem while it is happening. If your lag comes and goes, keep it running until the lag shows up.

Stop and copy the report

10 seconds
  1. Press Stop.
  2. Press Copy Text to clipboard.

Want a file instead? Press Export TEXT and save it.

Read it, then send it

1 minute

Paste the report into the reader below. It tells you in plain words where the problem is and who should get the report.

The Report Reader

Paste your report and get an answer. No report yet? Load an example to see how it works.

Paste Your Report

Read in your browser. Nothing is uploaded or saved.
Examples

The reader follows the standard rules for reading these reports. It is a guide, not a final word. When in doubt, send the report along.

Three Rules For Reading It

Each row is one stop on the way to the server, in order. Row 1 is your own router. The last row is our server.

Read from the bottom up

Look at the last row first. If it shows 0% loss, your data is reaching the server. Nothing above it can change that.

Loss in the middle is usually fake

A stop showing loss while the stops after it show none is just a router ignoring the test. Your game data still gets through. Ignore it.

Real loss carries on

Real trouble starts at one stop and continues on every row after it, all the way down. The stop where it starts is where the problem is.

%Data lost at that stop. The one that matters most.
Sent / RecvTest packets sent and answered. Aim for 600 sent.
BestFastest reply, in milliseconds.
AvrgAverage reply time. On the last row this is close to your ping.
WrstSlowest reply. Far above the average means spikes.
No responseThat stop does not answer tests at all. Normal. Ignore it.

Who To Send It To

Where the loss starts decides who can fix it.

Nobody. Fix it at home.

Loss or slow replies start on row 1

  • Row 1 is your own router.
  • Switch from wifi to a cable.
  • Restart the router and test again.

Your internet provider

Loss starts in the first few rows after your router, or in the middle

  • Contact their support and say you have packet loss with an MTR report.
  • Send the report text and the time you ran it.
  • They choose the route your data takes, so they are the ones who can change it.

Us

Loss starts in the last one or two rows

  • Open a ticket in Discord.
  • Include the report text, the date and time, and which server.
  • We can pass it on to our host.

Nobody. It is clean.

0% on the last row and a steady average

  • Your connection was fine during the test.
  • If the game still felt bad, the cause is on your PC.
  • Go to Fix Your FPS.

A report shows your own IP address and your provider's routers. Share it with your provider and with staff in a ticket, not in public chat.