TEST
Offline 178.65.77.64:28015 checked 21d 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
- 1000/ 100
- 234/ 400
- 212/ 245
- 120/ 100
- 498/ 1000
- 43/ 700
Quick answers
Tags and listings
Where does TEST appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TEST: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on TEST?
gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs164530 (Build): This server runs build 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): The Modded category fits: plugins or settings are in play — that is the tag list TEST puts out for the game's server browser. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What location is TEST in?
TEST does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 178.65.77.64:28015.
What's the uptime like for TEST?
The server TEST is not reachable at the moment; the last sighting was 21 days 5 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 25 September 2026.
What Rust version is TEST on?
On Windows, TEST runs Rust network protocol 2633 and build 164530. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
How often does TEST wipe?
The wipes recorded for TEST are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. 28 days 1 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to TEST?
No gather rate appears in the name of TEST. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Plugins or settings change the game, so the browser lists it as Modded. Oxide plugins are running here. VAC, Valve's anti-cheat, is enabled.
Which map is active on TEST?
The map on TEST is procedural, made by the game.
Player count
Is TEST busy?
The last sighting of TEST was 21 days 5 hours ago; it is offline right now.
What position does TEST hold in the server rankings?
For player hours in the last seven days, TEST ranks #16,758, within the top 71% of ranked servers.
How to join
What's the way to join TEST?
To join, open Rust, hit F1, and enter client.connect 178.65.77.64:28015. Or click Launch Rust on this page to open the game through Steam and connect.