Skip to the story

Live edition68,197 playing on 11,798 servers

Rust Insights

Server profile

TestServer

Online, with 0 of 1000 players on; ranked #15,348 of every public Rust server, the top 69%. It last wiped 14d ago.

Filed under
Launch Rust and join
0/ 1000 players now 0% full
07-day averagepeak –
#15,348ranktop 69%
14d agolast wipeno schedule published
–next wipeno rhythm it keeps

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
0123422:0007:0016:0001:0010:0020:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

010020030040022:0007:0016:0001:0010:0020:00

Note: 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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
15k10k15k20k20 Sep24 Sep15 Oct19 Oct24 Oct28 Oct

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

The wipe cycle

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 days usual gap between real wipes
33% on rhythm of its recent wipes
0 wipe-day peak players, last three wipes

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

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

Note: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

The record

Wipes

Every wipe we saw, newest first.

WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:36 UTC12d ago 0 – running 0
Wed 14 Oct, 19:15 UTC14d ago 0 – 1.6 days 0
Sun 11 Oct, 08:18 UTC17d ago 0 – 3.5 days 0
Wed 16 Sep, 19:41 UTC42d ago 0 – 24.5 days 0

Note: 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.

If you like this one

Similar servers

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

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 553 on average513/575
  2. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average315/400
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 297 on average42/250
  4. Rustoria.co - EU MainEU · groups of 16+ · weekly · 296 on average35/250
  5. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 272 on average91/150
  6. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average111/200

The short version

Quick answers

From the figures on this page.

Wipe days

On TestServer, what happens on wipe day?

At their busiest, its recent wipes drew 0 players on average. 0 hours into the latest wipe, the crowd on the server reached its peak.

How often does TestServer wipe, and on which day?

No next wipe can be predicted for TestServer, which wipes at irregular times. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. The world you are playing on now was made 14 days 2 hours ago.

Server

What does performance look like on TestServer?

The 48-hour average for server fps is 241, and 227 was the lowest seen. Buildings, deployables and the rest took the entity count as high as 22,207. The highest memory figure was 2,912 MB. Lag, for players, is low fps and an entity count that keeps climbing.

On what version does TestServer currently run?

Running on Linux, TestServer is on Rust network protocol 2633 and build 163794. The same protocol is required to join, and Steam takes care of updating it.

What does uptime look like for TestServer, and is it online?

TestServer is currently reachable and online. Going by the uptime figure it gives, its last restart was around 14 days ago. The last 7 full days gave 168 of 168 hours up, or 100% of the time. Rust Insights first logged this server on 14 September 2026.

Where does TestServer run from?

No region is published by TestServer. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. Connect through 103.236.54.209:28015.

Tags

How should you read the tags listed for TestServer?

When the game's server browser reads TestServer, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp1000 (Max players): 1,000 slots in total; ts8 (Group limit): 8 to a team, which is the default the game ships with; v2633 (Protocol): Your game must run the same version to join: the protocol is 2633; cs163794 (Build): Build 163794 is what it runs; ptrak (Networking): The network layer is RakNet, Rust's standard; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.

Where does TestServer turn up among the Rust Insights lists and filters?

TestServer appears among the following Rust Insights lists: Best Rust community servers. You will find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population history

What does the population of TestServer look like?

Of its 1,000 slots, TestServer currently has 0 filled. Its average over seven days comes to 0 players.

How does TestServer compare with other Rust servers in the ranking?

On player hours for the last seven days, TestServer sits at #15,348, inside the top 69% of ranked servers.

Map and rules

What settings and rules apply on TestServer?

Nothing about gather rate is given in the name of TestServer. The default of 8 players per group is what applies here. survival is the game mode, the standard game: gather, build, raid. Players may raid and fight one another. The server browser lists it under Community. Anti-cheat: VAC, from Valve, is on.

Which map is live on TestServer?

Size 2,300 and seed 12345 define the procedural map on TestServer, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps.

Join

What is the way to join TestServer?

To connect, start Rust and enter client.connect 103.236.54.209:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.

The small print

Server tags

What each one means.

Published as mp1000,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp1000
Max players 1,000 slots in total.
ts8
Group limit 8 to a team, which is the default the game ships with.
v2633
Protocol Your game must run the same version to join: the protocol is 2633.
cs163794
Build Build 163794 is what it runs.
ptrak
Networking The network layer is RakNet, Rust's standard.
$r?
Region code No region code is set.

Note: 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.