test
81.9.127.119:28015 checked 27d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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 servers
Quick answers
Rules and settings
What is the setup on test when it comes to rules and settings?
No gather rate appears in the name test. The group cap is 8 players, the default for the game. survival is its mode, gather, build, raid: the regular game. Raiding and fighting other players are allowed. This one sits under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running on it. Anti-cheat is on: VAC, from Valve.
Which map is active on test?
A procedural map, generated by the game, is what test runs.
Population
How full is test?
The server test is currently offline; it was last seen 27 days 16 hours ago.
Where does test sit in the rankings?
For player hours over the last week, test is #15,497, which puts it in the top – of all ranked servers.
Lists and tags
What do test's tags indicate?
The game's server browser reads these tags from test: gmrust (Game mode): Survival in the standard Rust mode; mp15 (Max players): It holds 15 players; ts8 (Group limit): This uses the standard team limit of 8; v2633 (Protocol): To join, your game must match protocol 2633; cs163493 (Build): Build number: 163493; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): Region code left unset; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded category: the game is altered by plugins or settings. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.
Which Rust Zerg Life filters and lists cover test?
These Rust Zerg Life lists include test: Modded Rust servers for clans and zergs. Under these filters it shows on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
About the server
What is the uptime and reliability of test?
Currently offline, test was last seen 27 days 16 hours ago. Over the last 7 full days, uptime was 0%: 0 hours up out of 168. The first time Rust Zerg Life saw it was on 16 September 2026.
Which Rust build does test use?
On Windows, test runs Rust network protocol 2633 and build 163493. Joining requires your game to be on the same protocol, which Steam updates automatically.
What is the location of test?
No region is published by test. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 81.9.127.119:28015.
Wipe schedule
How often does test wipe, and on what days?
The record of test's wipes is too thin to reveal its rhythm. The monthly force wipe hits every Rust server, and on Thursday 5 November at 19:00 UTC it is due next. 34 days 22 hours ago is when its present world was created.
Join the server
What steps do I take to join test?
Enter client.connect 81.9.127.119:28015 in the F1 console. Another way: use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published as mp15,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z
Game
gmrust
mp15
ts8
v2633
cs163493
ptrak
$r?
Mods and access
^o
^z
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.