Mon Localhost Rust
Offline 89.92.129.38: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 67% 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
- 56/ 400
- 45/ 245
- 134/ 100
- 77/ 1000
- 8/ 700
Quick answers
Tags and filters
Where does Mon Localhost Rust appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Mon Localhost Rust are: 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 Mon Localhost Rust?
Mon Localhost Rust's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): There are 2 slots on this server; 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; cs165217 (Build): It's on build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^o (Oxide): Plugins run through 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.
About the server
Where can you find Mon Localhost Rust?
There is no published region for Mon Localhost Rust. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 89.92.129.38:28015.
What's the uptime like for Mon Localhost Rust?
Right now Mon Localhost Rust is offline, having last been seen 21 days 6 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 26 September 2026.
What Rust version is Mon Localhost Rust on?
Rust network protocol 2633 and build 165217 is what Mon Localhost Rust runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
When does Mon Localhost Rust wipe?
Too few wipes are on record for Mon Localhost Rust to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 22 days 2 hours ago.
Map and rules
Which rules and settings is Mon Localhost Rust running?
The name of Mon Localhost Rust contains no gather rate. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. 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 Mon Localhost Rust?
A procedural map, generated by the game, is in play on Mon Localhost Rust.
Player stats
Is Mon Localhost Rust busy?
Mon Localhost Rust was last seen 21 days 6 hours ago and is offline as you read this.
What's Mon Localhost Rust's rank among Rust servers?
Over the last seven days, Mon Localhost Rust is #15,697 by player hours, among the top 67% of all ranked servers.
Join info
How do you get into Mon Localhost Rust?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 89.92.129.38:28015.