Testserver
Offline 178.230.2.223: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- 46/500
- 124/100
- 45/225
- 50/700
- 9/200
- 6/1000
Quick answers
from the figures on this pageReset cycle
What wipe timing does Testserver follow?
Its rhythm cannot be told from the wipes of Testserver 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 in play was created 30 days 13 hours ago.
Tag meanings
Which tags does Testserver carry, and what do they mean?
Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp10 (Max players): Slots: 10; 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): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from Testserver. 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 Testserver?
Rust Metrics lists featuring Testserver: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
What position does Testserver hold among Rust servers?
Player hours over seven days put Testserver at #16,949, in the top 71% of all ranked servers.
How full does Testserver get?
Reading for Testserver: offline at this moment; last seen 30 days 12 hours ago.
Operator and location
Which location does Testserver run from?
No region comes from Testserver. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 178.230.2.223:28015.
What Rust version is Testserver on?
Rust network protocol 2633 and build 165217 on Linux is the build Testserver runs. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is Testserver, and is it online now?
Reading: offline. Testserver last answered 30 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 28 September 2026.
Rules and settings
What rules does Testserver enforce, and what are its settings?
No gather rate appears in the name: Testserver. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.
What map is Testserver on?
Check: map. Procedural, generated by the game, on Testserver.
Join
How do you connect to Testserver?
Press F1 in Rust and enter client.connect 178.230.2.223:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.