TEST
Offline 46.41.65.46:28015 checked 27d 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 bestWipe 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
- 848/ 100
- 115/ 400
- 113/ 245
- 131/ 100
- 283/ 1000
- 21/ 700
Quick answers
Tags and filters
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): Survival, as standard Rust does it; mp50 (Max players): The slot count is 50; 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): It's on build 164530; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What's the location of TEST?
No region comes from TEST. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 46.41.65.46:28015.
How reliable is TEST?
TEST is down at the moment; it was last up 27 days 7 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 20 September 2026.
What Rust version is TEST on?
Rust network protocol 2633 and build 164530 is what TEST runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
What schedule does TEST follow for wipes?
The wipes recorded for TEST are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. The world you are on now was created 27 days 11 hours.
Rules and settings
What settings are in place on TEST?
No gather rate appears in the name of TEST. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
Which map is active on TEST?
TEST uses a game-generated procedural map.
Population
Is TEST busy?
The last sighting of TEST was 27 days 7 hours ago; it is offline right now.
What's TEST's rank among Rust servers?
Over the last seven days, TEST is #15,515 by player hours, among the top – of all ranked servers.
Getting in
What's the way to join TEST?
To join, open Rust, hit F1, and enter client.connect 46.41.65.46:28015. Or click Launch Rust on this page to open the game through Steam and connect.