Skip to the page
Network live 11,640 servers online 39,046 players aboard 72 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

Testserver

Online 157.85.85.43:23120 checked 9m ago

moddedoxide
Tracking number · connect
Wipe progress · wiped 7d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –too few wipes seen yet
0/ 1 players now 0% full
07-day averagepeak 1
#12,089ranktop 54%
7d agolast wipeno schedule published
–next wipetoo few wipes seen yet
Delivery history

Players, performance and rank

Players

AveragePeak
0123404:0013:0022:0007:0016:0001:00

Hourly average and peak, UTC.

Server performance

010020030040004:0013:0022:0007:0016:0001:00

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct6 Oct12 Oct17 Oct23 Oct28 Oct

Top 54% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

19 daysusual gapbetween real wipes
1wipe-day peakplayers, last three wipes
0%crowd heldelse halves by day 1

The first 48 hours of its last wipes

Tue 20 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes

every wipe as a delivery, newest first
  1. Tue 20 Oct, 14:50 UTC 15:50 UK · 7d ago
    Wipe delivered
    Peak
    1
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 1 Oct, 15:21 UTC 16:21 UK · 26d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 1
    Lasted
    19 days
    Players before
    0

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 160 on average 40 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average 134 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average 49 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average 20 / 700
  5. RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average 7 / 200
  6. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average 5 / 1000
Help desk

Quick answers

From the figures on this page.

Player activity

Where does Testserver place among Rust servers?

In the top 54% of all ranked servers sits Testserver, at #12,089 on hours played over seven days.

Is Testserver busy at the moment?

At the moment 0 players are on Testserver, which has 1 slots. Averaged over the past week: 0 players, peaking at 1.

Server rules

Which map is active on Testserver?

Size 1,500 and seed 50000 define the procedural map Testserver runs, generated by the game. Size and seed match means the map matches, so you can view it on RustMaps from this page.

What settings and rules should you know for Testserver?

You will not find a gather rate in the name of Testserver. The game's default applies: 8 players to a group at most. survival is the mode, the usual game: build, gather, raid. Raiding and PvP are both on. Because plugins or settings change the game, it is filed under Modded in the server browser. Oxide supplies the plugins. The VAC anti-cheat from Valve is enabled.

Operator and location

What location does Testserver run from?

No region is published by Testserver. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. The address to connect to is 157.85.85.43:23120.

What is the performance like on Testserver?

Server fps over the last 48 hours averaged 237; the lowest was 217. Buildings, deployables and all the rest of the world pushed its entity count as high as 8,458. Memory use peaked at 3,369 MB. Lag, to players, means low fps alongside an entity count on the rise.

Is Testserver up, and how good is its uptime?

Right now, Testserver is online. Its reported uptime suggests a restart roughly 4 days 16 hours ago. 100% is the uptime for the last 7 full days, up for 168 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 1 October 2026.

On what Rust version does Testserver operate?

On Linux, Testserver runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles that update for you.

Wipe times

What happens on Testserver when wipe day arrives?

At their busiest, its recent wipes drew an average of 1 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 1 it had fallen below half where the crowd did not hold.

How often does Testserver wipe, and at what times?

To tell its rhythm we would need more of Testserver's wipes on record; there are too few yet. The monthly force wipe, when every Rust server starts a new world, falls next on Thursday 5 November at 19:00 UTC. You are playing a world created 7 days 12 hours.

Tags and listings

Where does Testserver appear across the Rust Wipe Tracker lists and filters?

The Rust Wipe Tracker lists that include Testserver are: Modded Rust servers. These are the filters that bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should you read the tags on Testserver?

gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): Slot count: 1; ts8 (Group limit): 8 per team, which is the default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): A region code isn't set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it's listed under Modded are the tags Testserver publishes, and the server browser takes them as read. The top of this page also carries its current players and queue, plus when its world was made, all read from the tags.

Connecting

What steps do you take to join Testserver?

Enter client.connect 157.85.85.43:23120 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1
Max players Slot count: 1.
ts8
Group limit 8 per team, which is the default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code A region code isn't set.

Mods and access

^o
Oxide The plugin framework here is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.