TEST
Offline 176.209.14.217:28015 checked 1d 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 52% 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
- 1001/ 100
- 63/ 400
- 44/ 245
- 128/ 100
- 80/ 1000
- 8/ 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. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the tags on TEST?
TEST's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): The slot count is 10; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167781 (Build): It's on build 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
Where can you find TEST?
TEST does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. You can reach it at 176.209.14.217:28015.
How reliable is TEST?
TEST is down at the moment; it was last up 42 hours ago. It stayed up for 0 of the 24 hours in the last 1 full day, giving 0% uptime. The first sighting by Rust Going Deep was on 16 October 2026.
What Rust version is TEST on?
Rust network protocol 2634 and build 167781 is what TEST runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe schedule
How often does TEST wipe?
Too few wipes are on record for TEST to show its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 44 hours ago.
Settings and map
What settings and rules have been applied to TEST?
No gather rate appears in the name of TEST. Up to 8 players per group, which is the 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. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Which map is active on TEST?
A procedural map, generated by the game, is in play on TEST.
Player stats
Is TEST busy?
Right now TEST is offline, with its last appearance 42 hours ago. For the past week, players averaged 1 with a high of 1. Over the last 48 hours, 08:00 UTC drew the most players, 1 on average.
What position does TEST hold in the server rankings?
For player hours in the last seven days, TEST ranks #11,494, within the top 52% of ranked servers.
How to join
What's the process to join TEST?
Open Rust and press F1, then type client.connect 176.209.14.217:28015. Alternatively, click Launch Rust on this page to join via Steam.