TestServ12
Offline 89.125.214.42:28015 checked 28d ago
Server instruments
no direct query in 48 hoursPlayers now
2% 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 60% 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- 127/500
- 126/100
- 195/225
- 74/700
- 222/700
- 348/350
Quick answers
from the figures on this pageWipe schedule
How often does TestServ12 wipe, and when?
Its rhythm cannot be told from the wipes of TestServ12 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 29 days 5 hours ago.
Tag meanings
Which tags does TestServ12 carry, and what do they mean?
Tags published by TestServ12, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): Slots: 50; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $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.
Which lists and filters on Rust Metrics show TestServ12?
These Rust Metrics lists carry TestServ12: 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 TestServ12 sit in the rankings?
Player hours over seven days put TestServ12 at #14,336, in the top 60% of all ranked servers.
What player count does TestServ12 carry?
TestServ12 is not responding; status offline, last seen 28 days 22 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. Check: address. It reads 89.125.214.42:28015.
What Rust version is TestServ12 on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by TestServ12. To get in, your game needs the same protocol; Steam applies the update.
How reliable is TestServ12, and is it online now?
TestServ12 reports offline. The last reading came 28 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 30 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TestServ12?
Check: gather rate. The name TestServ12 does not state one. The group cap is 8 players, which is the default in the game. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. 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.
What map is TestServ12 on?
From seed 352165132, the game generates the procedural map on TestServ12. Its size is 1,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
How can you get onto TestServ12?
Press F1 in Rust and enter client.connect 89.125.214.42:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.