TestServ12
Offline 89.125.214.42:28015 checked 29d 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 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- 172/500
- 127/100
- 168/225
- 82/700
- 100/200
- 248/700
Quick answers
from the figures on this pageWipe schedule
What wipe timing does TestServ12 follow?
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 in play was created 29 days 1 hours ago.
Tag meanings
How should you read the tags on TestServ12?
These are the tags TestServ12 publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; 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): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does TestServ12 appear in Rust Metrics lists and filters?
On Rust Metrics, TestServ12 sits in these lists: 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.
Population
Where does TestServ12 sit in the rankings?
Player hours over seven days put TestServ12 at #16,810, in the top 70% of all ranked servers.
What is the population on TestServ12?
TestServ12 is not responding; status offline, last seen 29 days 1 hours ago.
Server
Where does TestServ12 sit?
Reading: location. TestServ12 gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 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. Matching protocol is required to join. Let Steam update your game.
Is TestServ12 up, and how often does it stay up?
TestServ12 reports offline. The last reading came 29 days 1 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.
Rules and settings
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. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is TestServ12 on?
The game generates a procedural map for TestServ12.
How to join
What do you do to join 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.