test 2
Offline 138.204.25.121:28016 checked 40d 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- 180/500
- 132/100
- 187/225
- 84/700
- 349/200
- 238/700
Quick answers
from the figures on this pageWipe schedule
When does test 2 wipe?
Its rhythm cannot be told from the wipes of test 2 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 47 days 13 hours ago.
Tag meanings
How should you read the tags on test 2?
Tags published by test 2, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163207 (Build): The server runs game build 163207; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does test 2 appear in Rust Metrics lists and filters?
These Rust Metrics lists carry test 2: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Player count
Where does test 2 sit in the rankings?
Player hours over seven days put test 2 at #15,450, in the top – of all ranked servers.
What is the population on test 2?
Status for test 2: offline. Last seen 40 days 12 hours ago.
Operator and location
What location is test 2 hosted in?
Reading: location. test 2 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 138.204.25.121:28016.
What Rust version is test 2 on?
Reading: test 2, Rust network protocol 2633 and build 163207, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on test 2, and is it online?
test 2 reports offline. The last reading came 40 days 12 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.
Map and rules
What settings and rules apply on test 2?
Reading the name gives no gather rate for test 2. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.
Connection
How can you get onto test 2?
Press F1 in Rust and enter client.connect 138.204.25.121:28016. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.