local-mapgen-test
Offline 52.35.237.101:28965 checked 17d 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 70% 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
- 352/ 375
- 590/ 600
- 397/ 475
- 120/ 200
- 607/ 625
- 243/ 250
Quick answers
Tags and search
Where does local-mapgen-test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include local-mapgen-test: Rust community servers, going deep. You can find it on the server list by these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on local-mapgen-test?
gmrust (Game mode): This is the standard Rust survival experience; mp1 (Max players): The slot count is 1; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): This server runs build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code — that is the tag list local-mapgen-test puts out for the game's server browser. 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 location is local-mapgen-test in?
No region comes from local-mapgen-test. 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 52.35.237.101:28965.
How reliable is local-mapgen-test?
The server local-mapgen-test is not reachable at the moment; the last sighting was 17 days 2 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. 1 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for local-mapgen-test?
The version on local-mapgen-test is Rust network protocol 2633 and build 165217, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
What schedule does local-mapgen-test follow for wipes?
The wipes recorded for local-mapgen-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. 17 days 2 hours is how long ago this world came into being.
Rules and settings
What settings are in place on local-mapgen-test?
The name of local-mapgen-test contains no gather rate. 8 players is the group cap, the game's default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. The server browser lists it under Community, making it a community server. The server runs Valve's anti-cheat, VAC.
Which map is active on local-mapgen-test?
A procedural map, generated by the game, is in play on local-mapgen-test.
Player count
Is local-mapgen-test busy?
local-mapgen-test was last seen 17 days 2 hours ago and is offline as you read this.
Where does local-mapgen-test sit in the rankings?
For player hours in the last seven days, local-mapgen-test ranks #16,614, within the top 70% of ranked servers.
How to join
How do you get into local-mapgen-test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 52.35.237.101:28965.