TestServer
Offline 178.178.89.62:28015 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. 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- 40/500
- 125/100
- 48/225
- 18/700
- 6/200
- 7/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. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 31 days 18 hours ago.
Tag meanings
How should you read the tags on TestServer?
These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): Slots: 15; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^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 TestServer appear in Rust Metrics lists and filters?
On Rust Metrics, TestServer sits in these lists: 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.
Player count
What position does TestServer hold among Rust servers?
Ranking for TestServer: #16,859 on seven-day player hours, top 71% of all ranked servers.
What player count does TestServer carry?
Reading for TestServer: offline at this moment; last seen 28 days 8 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. Connect using 178.178.89.62:28015.
What Rust version is TestServer on?
Version check: Rust network protocol 2633 and build 165217 on Windows, run by TestServer. Check: protocol. To join, your game must match; Steam handles the update.
How reliable is TestServer, and is it online now?
TestServer reports offline. The last reading came 28 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 29 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on TestServer?
Reading the name gives no gather rate for TestServer. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
Which map is live on TestServer?
The game generates a procedural map for TestServer.
Connection
How do you connect to TestServer?
Check: join. Open Rust, press F1, then enter client.connect 178.178.89.62:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.