Skip to the page
Network live 11,801 servers online 78,222 players aboard 109 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 103.236.54.209:28015 checked 9m ago

Tracking number · connect
Wipe progress · wiped 14d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 1000 players now 0% full
07-day averagepeak –
#15,323ranktop 69%
14d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
0123421:0006:0015:0000:0009:0019:00

Hourly average and peak, UTC.

Server performance

010020030040021:0006:0015:0000:0009:0019: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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep15 Oct19 Oct24 Oct28 Oct

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

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

3.5 daysusual gapbetween real wipes
33%on rhythmof its recent wipes
0wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

Fri 16 OctWed 14 OctSun 11 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes

every wipe as a delivery, newest first
  1. Fri 16 Oct, 08:36 UTC 09:36 UK · 12d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Wed 14 Oct, 19:15 UTC 20:15 UK · 14d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    1.6 days
    Players before
    0
  3. Sun 11 Oct, 08:18 UTC 09:18 UK · 17d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    3.5 days
    Players before
    0
  4. Wed 16 Sep, 19:41 UTC 20:41 UK · 42d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    24.5 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. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 552 on average 588 / 675
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average 363 / 525
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 299 on average 49 / 250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 298 on average 40 / 250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 271 on average 130 / 200
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 254 on average 140 / 300
Help desk

Quick answers

From the figures on this page.

Population

Where does TestServer place among Rust servers?

Over the past seven days, TestServer has climbed to #15,323 for player hours, putting it in the top 69% of all ranked servers.

Is TestServer busy at the moment?

At the moment 0 players are on TestServer, which has 1,000 slots. Averaged over the past week: 0 players.

Rules and settings

Which map is active on TestServer?

The game generates the procedural map on TestServer at size 2,300 with seed 12345. You can see the map on RustMaps from this page, since one size and seed give one map.

What are the rules on TestServer, and what settings does it run?

You will not find a gather rate in the name of TestServer. 8 players is the group limit, since the game's default applies. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players is allowed. The server browser files it under Community, as a community server. VAC, the anti-cheat from Valve, is active.

Server details

What location does TestServer run from?

No region is published by TestServer. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. 103.236.54.209:28015 is its address.

Does TestServer perform well?

Server fps over the last 48 hours averaged 241; the lowest was 227. The world held as many as 22,207 entities: buildings, deployables and the rest. 2,912 MB of memory was its top figure. Players feel a rising entity count and low fps as lag.

Is TestServer up, and how good is its uptime?

You can find TestServer online at present. About 13 days 20 hours ago is when it last restarted, judged by the uptime it gives. 100% is the uptime for the last 7 full days, up for 168 of 168 hours. It was first seen by Rust Wipe Tracker on 14 September 2026.

What Rust version is TestServer using?

On Linux, TestServer runs Rust network protocol 2633 and build 163794. Steam keeps your game updated; it has to be on the same protocol to join.

Wipe schedule

How does TestServer handle its wipe days?

0 players is the average peak across its recent wipes. After 0 hours the latest wipe's crowd hit its peak.

When does TestServer wipe? What schedule does it follow?

There is no next wipe to predict for TestServer: it wipes at irregular times. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. 14 days 1 hours have passed since this world was made.

Tags and listings

On Rust Wipe Tracker, which lists and filters is TestServer part of?

These Rust Wipe Tracker lists take TestServer: Rust community servers, unmodded. These are the filters that bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the tags on TestServer?

Read off the game's server browser, the tags for TestServer are: gmrust (Game mode): Standard Rust survival is the game mode here; mp1000 (Max players): Slot count: 1,000; ts8 (Group limit): 8 per team, which is the default; v2633 (Protocol): Protocol 2633 is required; a different version can't join; cs163794 (Build): The game build is 163794; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Connecting

What steps do you take to join TestServer?

Enter client.connect 103.236.54.209:28015 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 mp1000,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Standard Rust survival is the game mode here.
mp1000
Max players Slot count: 1,000.
ts8
Group limit 8 per team, which is the default.
v2633
Protocol Protocol 2633 is required; a different version can't join.
cs163794
Build The game build is 163794.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code A region code isn't set.

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.