Test_2
Offline 163.123.33.233:28015 checked 30d 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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 113/500
- 133/100
- 196/225
- 73/700
- 211/700
- 348/350
Quick answers
from the figures on this pageWipe schedule
What wipe timing does Test_2 follow?
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 46 days 22 hours ago.
Tag meanings
Which tags does Test_2 carry, and what do they mean?
Tags published by Test_2, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Test_2?
On Rust Metrics, Test_2 sits in these lists: 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.
Player count
What position does Test_2 hold among Rust servers?
Player hours over seven days put Test_2 at #16,924, in the top 71% of all ranked servers.
What player count does Test_2 carry?
Test_2 is not responding; status offline, last seen 30 days 21 hours ago.
Server details
Which location does Test_2 run from?
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 163.123.33.233:28015.
What Rust version is Test_2 on?
Rust network protocol 2633 and build 165217 on Windows is the build Test_2 runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Test_2, and is it online now?
Test_2 reports offline. The last reading came 30 days 21 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.
Settings and map
What rules does Test_2 enforce, and what are its settings?
Check: gather rate. The name Test_2 does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
What map is Test_2 on?
The game generates a procedural map for Test_2.
Connection
How can you get onto Test_2?
Check: join. Open Rust, press F1, then enter client.connect 163.123.33.233:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.