TestServ12
Offline 89.125.214.42:35001 checked 28d 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, measured since 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% 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- 26/500
- 130/100
- 35/225
- 11/700
- 3/200
- 1/1000
Quick answers
from the figures on this pageWipe timing
How often does TestServ12 wipe, and when?
To tell the rhythm of TestServ12, 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. The world in play was created 28 days 14 hours ago.
Lists and filters
Which tags does TestServ12 carry, and what do they mean?
Check: tags. The game's server browser reads gmvanilla (Game mode): Check: mode. Vanilla survival; mp200 (Max players): The server holds 200 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from TestServ12. 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 TestServ12?
Rust Metrics lists featuring TestServ12: 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.
Population
Where does TestServ12 sit in the rankings?
Ranking for TestServ12: #16,699 on seven-day player hours, top 70% of all ranked servers.
How full does TestServ12 get?
Status for TestServ12: offline. Last seen 28 days 5 hours ago.
Server details
Where does TestServ12 sit?
Reading: location. TestServ12 gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 89.125.214.42:35001.
What Rust version is TestServ12 on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by TestServ12. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on TestServ12, and is it online?
Check: connection. TestServ12 is offline at this moment. Last contact was 28 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 30 September 2026.
Map and rules
How is TestServ12 configured, and what rules are in force?
Check: gather rate. The name TestServ12 does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
What map is TestServ12 on?
Size 1,000 and seed 352165132: the game generates the procedural map on TestServ12 from them. View it on RustMaps from this page: matching size and seed give an identical map.
Join
What do you do to join TestServ12?
Check: join. Open Rust, press F1, then enter client.connect 89.125.214.42:35001. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.