LOCAL_MAIN
Offline 37.67.192.175:28015 checked 32d 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
- 1001/ 100
- 62/ 400
- 49/ 245
- 130/ 100
- 82/ 1000
- 7/ 700
Quick answers
Tags and filters
Where does LOCAL_MAIN appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry LOCAL_MAIN are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on LOCAL_MAIN?
The server browser shows these tags for LOCAL_MAIN: gmrust (Game mode): This is the standard Rust survival experience; mp5 (Max players): There are 5 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163794 (Build): This server runs build 163794; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^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.
Server details
What's the location of LOCAL_MAIN?
LOCAL_MAIN 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. You can reach it at 37.67.192.175:28015.
Is LOCAL_MAIN up, and how often does it stay online?
The server LOCAL_MAIN is not reachable at the moment; the last sighting was 32 days 9 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 14 September 2026.
What is the Rust version for LOCAL_MAIN?
Rust network protocol 2633 and build 163794 is what LOCAL_MAIN runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
When does LOCAL_MAIN wipe?
Too few wipes are on record for LOCAL_MAIN 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. 33 days 18 hours is how long ago this world came into being.
Settings and map
Which rules and settings is LOCAL_MAIN running?
No gather rate appears in the name of LOCAL_MAIN. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
What's the map on LOCAL_MAIN?
LOCAL_MAIN uses a game-generated procedural map.
Player count
What's the population like on LOCAL_MAIN?
Right now LOCAL_MAIN is offline, with its last appearance 32 days 9 hours ago.
Where does LOCAL_MAIN sit in the rankings?
For player hours in the last seven days, LOCAL_MAIN ranks #15,404, within the top – of ranked servers.
Join info
What's the way to join LOCAL_MAIN?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 37.67.192.175:28015.