LiveLive coverage · Rust server
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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 26% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The current map
Sunday 25 October 2026, 06:28 UTC
Wipe
Sunday 4 October 2026, 05:12 UTC
Wipe
Tuesday 29 September 2026, 17:12 UTC
Wipe
Sunday 27 September 2026, 00:48 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.
Recent wipes on this server averaged a peak of 1 players at their busiest. The crowd on the latest wipe peaked 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. On those occasions it fell below half by day 5.5.
My Custom Map Server wipes with no fixed pattern, so there is nothing to predict. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. This world dates from 4 days 4 hours.
The Rust Live Stats lists that include My Custom Map Server are 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 week.
gmrust (Game mode): Standard survival, in the Rust style; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded: that is the tag list My Custom Map Server 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.
Live now: 0 players on My Custom Map Server, out of 10 slots. The seven-day average is 1 players, with a peak of 1. Between now and 48 hours back, 14:00 UTC drew the most players, 1 on average.
Player hours over seven days put My Custom Map Server at #5,776, in the top 26% of all ranked servers.
Nothing in the name of My Custom Map Server states a gather rate. The default applies: 8 players to a group. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. Plugins or settings change the game, and the browser lists it as Modded. The plugin load is Oxide. VAC is enabled: Valve's anti-cheat.
A procedural map, generated by the game, runs on My Custom Map Server.
No region is published by My Custom Map Server. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 106.156.250.10:28015 is its address.
My Custom Map Server operates on Windows with Rust network protocol 2635 and build 168909. Joining requires the same protocol on your game; Steam takes care of updating it.
My Custom Map Server is up and running at this moment. It was online for 38 of 168 hours in the last 7 full days, or 23% of the time. On 26 September 2026, Rust Live Stats saw it for the first time.
Enter client.connect 106.156.250.10:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.