Test
Offline 176.6.76.229:28015 checked 9d 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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 7 Oct, 23:32 UTC10d ago | 0 | – | running | 0 |
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
- 241/ 300
- 429/ 475
- 234/ 250
- 176/ 225
- 202/ 250
- 218/ 275
Quick answers
Tags and listings
Where does Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Test: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all.
How should you read the tags on Test?
gmrust (Game mode): Survival, as standard Rust does it; mp5 (Max players): The slot count is 5; v2323 (Protocol): The protocol is 2323; a different version won't get you in; ptrak (Networking): RakNet, the network layer Rust uses by default; he8c2d43f (Custom tag): It's a custom tag, set by the owner or a plugin, not a standard one; stok (Custom tag): It's a custom tag, set by the owner or a plugin, not a standard one — 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. To connect, use 176.6.76.229:28015.
Is Test up, and how often does it stay online?
Right now Test is offline, having last been seen 9 days 17 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 7 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for Test?
The version on Test is Rust network protocol 2323, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
What schedule does Test follow for wipes?
Test's rhythm is unclear because not enough wipes are on record yet. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 1770 days 23 hours is how long ago this world came into being.
What happens on wipe day at Test?
Across its recent wipes, the average busiest point drew 0 players. On the latest wipe, 0 hours passed before the crowd peaked.
Settings and map
What settings are in place on Test?
The name of Test contains no gather rate. No group limit is published. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser lists it under Community, making it a community server. VAC is on: Valve's anti-cheat is active.
What's the map on Test?
A procedural map, generated by the game, is in play on Test.
Player count
What's the population like on Test?
Test was last seen 9 days 17 hours ago and is offline as you read this.
What position does Test hold in the server rankings?
For player hours in the last seven days, Test ranks #15,907, within the top 72% of ranked servers.
How to join
How do you get into Test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 176.6.76.229:28015.