Live coverage · Rust server
Offline Rust Custom Map Test is not on the server list right now. The figures below are from when it was last seen, 1d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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, measured since 27 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 50% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The current map
Tuesday 27 October 2026, 15:47 UTC
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.
Too few wipes are recorded for Rust Custom Map Test to establish a pattern. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. This world dates from 37 hours.
On Rust Live Stats, Rust Custom Map Test is listed under Modded Rust servers live now. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
gmrust (Game mode): Standard survival, in the Rust style; mp3 (Max players): The slot count is 3; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded: that is the tag list Rust Custom Map Test publishes for the game's server browser. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Last seen 35 hours ago, Rust Custom Map Test is offline right now. Averaged across seven days, 1 players; the peak was 2. Peak hour over 48 hours: 16:00 UTC, at 2 players on average.
On player hours for the past seven days, Rust Custom Map Test sits at #11,180, inside the top 50% of ranked servers.
The name Rust Custom Map Test carries no gather rate. No custom limit is set, so groups hold the default 8 players. survival is the mode, with the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser files it under Modded: plugins or settings alter the game. Plugins run here: Oxide. VAC is enabled: Valve's anti-cheat.
Rust Custom Map Test runs a game-generated procedural map: size 3,800, seed 1337. Size and seed repeat the same map, so RustMaps can show it from this page. Map name, as listed: Custom Map.
Nothing on Rust Custom Map Test states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. Connect to 171.229.218.49:28015.
The average server fps was 196 over the last 48 hours; the lowest was 196. Entity count reached 84,465: buildings, deployables and the rest of the world. Memory use peaked at 1,493 MB. Players experience lag when fps is low and the entity count climbs.
Rust network protocol 2635 and build 168909 on Windows is what Rust Custom Map Test runs. Joining requires the same protocol on your game; Steam takes care of updating it.
Rust Custom Map Test is currently offline, with its last appearance 35 hours ago. Based on the uptime it reports, the last restart was about 57 minutes ago. It was online for 0 of 24 hours in the last 1 full day, or 0% of the time. Rust Live Stats has tracked it since 27 October 2026.
Use Launch Rust and join on this page to open Rust through Steam and connect, or start Rust, press F1, and type client.connect 171.229.218.49:28015.