DWG RG-S0000Server sheetchecked 45d ago
Testing
Offline 144.130.111.115:28015 checked 45d 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
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
| 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
Server data
Is Testing online, and what uptime has been recorded?
The current state of Testing is offline, with the last sighting 45 days 17 hours ago. 0 of 168 hours up over the last 7 full days, which is 0% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
What location is recorded for Testing?
There is no region published by Testing. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. It is reached at 144.130.111.115:28015.
On which Rust version is Testing running?
On Windows, Testing runs Rust network protocol 2633 and build 163207. Steam updates your game, which must be on the same protocol for you to join.
Counts
How many players are plotted on Testing?
No response from Testing; the server was last seen 45 days 17 hours ago.
Wipe times
Which times and days are wipes plotted at on Testing?
Too few wipes are on record for Testing to show its rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 53 days 12 hours ago.
Rules and settings
What settings and rules apply on Testing?
Gather rate for Testing: not stated in the name. The group limit is 8 players, the game's default. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.
What is the map for Testing?
A procedural map, generated by the game, is what Testing runs.
Lists and filters
Where does Testing appear among the Rust Graphs lists and filters?
On Rust Graphs, Testing is placed in these lists: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meaning is attached to each tag on Testing?
gmrust (Game mode): Survival in standard Rust style; mp10 (Max players): 10 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): Join only if your game is on protocol 2633; cs163207 (Build): Build: 163207; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded are the tags Testing publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
By what method do you join Testing?
Enter client.connect 144.130.111.115:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it 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.