Statistical profileOffline
TestServer
160.251.212.33:28015 checked 7d ago
Connect to this server
1. Main points
Players now
0/ 50
0% full
7-day average
0
peak –
Rank
#15,341
top 69%
Last wipe
34d ago
no schedule published
Next wipe
–
too few wipes seen yet
Main points
- The server is offline; at its last check there were 0 players on it, 0% of its 50 slots.
- It ranks #15,341 of all ranked servers, the top 69%, on player hours over the last seven days.
- Its current map went up 34d ago.
2. Players
Figure 1: Players on TestServer
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patterntoo few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipe-day peak
1
players, last three wipes
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 25 Sep, 04:23 UTC34d ago | 1 | – | running | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of TestServer
3000 · seed 15111
Table 2: The world
As the server publishes it
| Map | Custom Map |
|---|---|
| Size | 3000 |
| Seed | 15111 |
8. Server characteristics
Table 3: Characteristics of TestServer
What the server publishes and what was recorded
| Address | 160.251.212.33:28015 |
|---|---|
| Region | – |
| Max players | 50 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 25 Sep 2026, 05:33 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 150 on average | 39 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 86 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 32 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 86 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 309 / 350 |
10. Quick answers
From the figures on this page.
Wipe details
On what schedule are wipes carried out on TestServer?
Too few wipes of TestServer are on record to establish its rhythm. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. This world was generated 34 days 16 hours ago.
On TestServer, what happens on wipe day?
The average busiest point of its recent wipes drew 1 players. On the latest wipe, 1 hours passed before the crowd peaked.
About the server
What does the record show for the uptime and current status of TestServer?
Last seen 7 days 15 hours ago, TestServer is offline in this release. 7 of 168 hours on across the last 7 full days gives an uptime of 4%. The first sighting of it by Rust Census was on 13 September 2026.
What location has been recorded for TestServer?
A region is not published by TestServer. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. At 160.251.212.33:28015 it is addressed.
What version of Rust has been recorded on TestServer?
This release lists TestServer on Rust network protocol 2633 and build 162929, running on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Player counts
What population has been recorded on TestServer?
TestServer is offline at present; its last recording was 7 days 15 hours ago. The seven-day average for this server is 0 players.
In the rankings of Rust servers, where is TestServer placed?
For seven-day player hours, TestServer is ranked #15,341, placing it in the top 69% of all ranked servers.
Tag details
On Rust Census, which lists and filters carry TestServer?
The Rust Census lists that TestServer fits are: Modded Rust servers, counted. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What is meant by each tag shown on TestServer?
gmrust (Game mode): The game mode is standard survival as Rust runs it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): 8 per team, which is the game's default limit; v2633 (Protocol): To connect, your game version must match protocol 2633; cs162929 (Build): Build 162929 is installed; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server carries no region code; ^o (Oxide): Plugins are handled by Oxide (uMod) on this server; ^z (Modded): Modded: the game is changed by plugins or settings are the tags TestServer publishes, and the game's server browser reads them. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Map and rules
Which map has been recorded for TestServer?
TestServer runs a procedural map of size 3,000 with seed 15111, generated by the game. Size and seed together fix the map, so you can view it on RustMaps from this page. The name of the map is listed as: Custom Map.
How is TestServer configured, and what rules does it keep?
No gather rate is recorded for TestServer in its name. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Modded is its section in the server browser, because plugins or settings change the game. Oxide plugins are recorded on it. The server runs VAC, Valve's anti-cheat.
Join details
What steps are needed to join TestServer?
You can open the console in Rust with F1 and enter client.connect 160.251.212.33:28015; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp50,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp50 | Max players The server holds 50 slots. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2633 | Protocol To connect, your game version must match protocol 2633. |
cs162929 | Build Build 162929 is installed. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code This server carries no region code. |
Mods and access
^o | Oxide Plugins are handled by Oxide (uMod) on this server. |
|---|---|
^z | Modded Modded: the game is changed by plugins or settings. |
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.