TEST
Offline 178.178.89.235:28015 checked 17d 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 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
- 944/ 100
- 171/ 400
- 130/ 245
- 125/ 100
- 384/ 1000
- 25/ 700
Quick answers
Tags and search
Where does TEST appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TEST: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TEST?
The server browser shows these tags for TEST: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): There are 10 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): The build number is 164530; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What location is TEST in?
TEST 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.235:28015.
What's the uptime like for TEST?
TEST is down at the moment; it was last up 17 days 7 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 30 September 2026.
What is the Rust version for TEST?
The version on TEST is Rust network protocol 2633 and build 164530, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe info
How often does TEST wipe?
TEST's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 28 days 2 hours ago.
Rules and settings
Which rules and settings is TEST running?
Its name does not state a gather rate for TEST. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
What's the map on TEST?
A procedural map, generated by the game, is in play on TEST.
Population
Is TEST busy?
Right now TEST is offline, with its last appearance 17 days 7 hours ago.
What's TEST's rank among Rust servers?
Over the last seven days, TEST is #16,787 by player hours, among the top 70% of all ranked servers.
Join info
What's the process to join TEST?
Open Rust and press F1, then type client.connect 178.178.89.235:28015. Alternatively, click Launch Rust on this page to join via Steam.