TEST
Offline 95.70.20.144:28015 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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- 55/500
- 123/100
- 46/225
- 54/700
- 7/200
- 8/1000
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TEST follow?
To tell the rhythm of TEST, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 43 days 4 hours ago the current world was made.
Tag meanings
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; 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): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TEST: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does TEST sit in the rankings?
Ranking for TEST: #14,814 on seven-day player hours, top – of all ranked servers.
What is the population on TEST?
TEST is not responding; status offline, last seen 43 days 3 hours ago.
Server
Which location does TEST run from?
Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 95.70.20.144:28015.
What Rust version is TEST on?
Reading: TEST, Rust network protocol 2633 and build 163794, Windows. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TEST, and is it online now?
Check: connection. TEST is offline at this moment. Last contact was 43 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 15 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TEST?
No gather rate appears in the name: TEST. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is TEST on?
Check: map. Procedural, generated by the game, on TEST.
Connection
How can you get onto TEST?
Check: join. Open Rust, press F1, then enter client.connect 95.70.20.144:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.