Local Rust Custom Map Test
Offline 77.73.135.51:28015 checked 34d 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
- 118/ 2000
- 325/ 2000
- 38/ 200
- 49/ 250
- 50/ 200
- 62/ 200
Quick answers
Tags and filters
Where does Local Rust Custom Map Test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Local Rust Custom Map Test: Modded Rust servers and Go deep on PvE servers. You can find it on the server list by these filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Local Rust Custom Map Test?
Local Rust Custom Map Test's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp5 (Max players): It holds 5 players; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs162929 (Build): It's on build 162929; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^p (PvE): It's player versus environment, so the world poses the risk, not other players; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
What's the location of Local Rust Custom Map Test?
No region comes from Local Rust Custom Map 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 77.73.135.51:28015.
Is Local Rust Custom Map Test up, and how often does it stay online?
Local Rust Custom Map Test is down at the moment; it was last up 34 days 22 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 13 September 2026.
What Rust version is Local Rust Custom Map Test on?
On Windows, Local Rust Custom Map Test runs Rust network protocol 2633 and build 162929. The protocol must match to join; Steam will update your game.
Wipe schedule
What schedule does Local Rust Custom Map Test follow for wipes?
Too few wipes are on record for Local Rust Custom Map 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 35 days 23 hours ago.
Map and rules
What settings and rules have been applied to Local Rust Custom Map Test?
No gather rate appears in the name of Local Rust Custom Map Test. 8 players is the group cap, the game's default. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC is on: Valve's anti-cheat is active.
Player stats
What's the population like on Local Rust Custom Map Test?
Local Rust Custom Map Test was last seen 34 days 22 hours ago and is offline as you read this.
How to join
How do you get into Local Rust Custom Map Test?
To join, open Rust, hit F1, and enter client.connect 77.73.135.51:28015. Or click Launch Rust on this page to open the game through Steam and connect.