Testing
144.130.111.115:28015 checked 31d 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
Which settings and rules apply on Testing?
There is no gather rate in the name Testing. That is the game's default: groups of up to 8 players. survival is its mode, gather, build and raid: the standard game. Other players can be fought and raided. This one sits under Modded in the browser: the game is changed by plugins or settings. The plugins it runs number Oxide. Anti-cheat is on: VAC, from Valve.
Which map is active on Testing?
A procedural map, generated by the game, is what Testing runs.
Server population
What is the population like on Testing?
At present, Testing is offline and its last appearance was 31 days ago.
Lists and tags
How should you read the tags on Testing?
The game's server browser reads these tags from Testing: gmrust (Game mode): Survival in the standard Rust mode; mp10 (Max players): The server has 10 slots; ts8 (Group limit): The team cap is 8, which is the game's default; v2633 (Protocol): Protocol 2633—only players on that version can get in; cs163207 (Build): The game build is 163207; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code is set; ^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.
Where does Testing appear in Rust Zerg Life lists?
Modded Rust servers for clans and zergs: that is where you will find Testing among the Rust Zerg Life rankings. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
About the server
How reliable is Testing, and is it up?
Currently offline, Testing was last seen 31 days 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 13 September 2026.
What Rust version is Testing on?
On Windows, Testing runs Rust network protocol 2633 and build 163207. Joining requires your game to be on the same protocol, which Steam updates automatically.
What location does Testing use?
From Testing, no region is published. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 144.130.111.115:28015.
Wipe cycle
When does Testing wipe?
The record of Testing's wipes is too thin to reveal its rhythm. Come Thursday 5 November at 19:00 UTC, the monthly force wipe arrives for every Rust server. The world it is running now dates from 38 days 19 hours ago.
Join the server
How can I connect to Testing?
Enter client.connect 144.130.111.115: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 mp10,ptrak,$r?,v2633,gmrust,cs163207,ts8,^o^z
Game
gmrust
mp10
ts8
v2633
cs163207
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.