Testing
Offline 144.130.111.115:28015 checked 46d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
the same kind of game, then region, group limit, rate and wipes- 40/500
- 128/100
- 84/225
- 34/700
- 87/700
- 301/310
Quick answers
from the figures on this pageWipe timing
What wipe timing does Testing follow?
The rhythm of Testing's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 54 days 5 hours ago.
Tag meanings
How should you read the tags on Testing?
Tags published by Testing, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163207 (Build): Game build reading: 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Testing?
On Rust Metrics, Testing sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
How full does Testing get?
Reading for Testing: offline at this moment; last seen 46 days 10 hours ago.
Operator and location
What location is Testing hosted in?
No region tag on Testing. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 144.130.111.115:28015.
What Rust version is Testing on?
Reading: Testing, Rust network protocol 2633 and build 163207, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is Testing up, and how often does it stay up?
Reading: offline. Testing last answered 46 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
How is Testing configured, and what rules are in force?
No gather rate appears in the name: Testing. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
What map is Testing on?
Procedural map on Testing, made by the game's generator.
How to join
How do you connect to Testing?
To join: start Rust, press F1 and type client.connect 144.130.111.115:28015. Or press Launch Rust here and Steam opens the game and connects you.