TestServer
Offline 178.178.89.62:28015 checked 18d ago
Players
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
- 0/ 100
- 78/ 400
- 50/ 245
- 124/ 100
- 83/ 1000
- 5/ 700
Quick answers
Tags and search
Where does TestServer appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TestServer are: Modded Rust servers. You can find it on the server list by these filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TestServer?
gmrust (Game mode): This is the standard Rust survival experience; mp15 (Max players): The slot count is 15; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): To join, your game has to be on protocol 2633; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list TestServer puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
About the server
Where can you find TestServer?
TestServer does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. The endpoint is 178.178.89.62:28015.
What's the uptime like for TestServer?
Right now TestServer is offline, having last been seen 18 days 9 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 29 September 2026.
What is the Rust version for TestServer?
On Windows, TestServer runs Rust network protocol 2633 and build 165217. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does TestServer wipe?
Too few wipes are on record for TestServer to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 21 days 18 hours is how long ago this world came into being.
Map and rules
What settings are in place on TestServer?
The name of TestServer contains no gather rate. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC is on: Valve's anti-cheat is active.
What's the map on TestServer?
TestServer uses a game-generated procedural map.
Population
How many players are on TestServer?
The last sighting of TestServer was 18 days 9 hours ago; it is offline right now.
Where does TestServer sit in the rankings?
For player hours in the last seven days, TestServer ranks #16,859, within the top 71% of ranked servers.
Getting in
How do you get into TestServer?
To join, open Rust, hit F1, and enter client.connect 178.178.89.62:28015. Or click Launch Rust on this page to open the game through Steam and connect.