Live coverage · Rust server
Offline LOCAL raid difficulty validation 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. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
This server has not put up a new map since the desk started watching it.
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 LOCAL raid difficulty validation 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 44 hours.
These are the Rust Live Stats lists LOCAL raid difficulty validation fits: 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.
These are the tags LOCAL raid difficulty validation makes public: gmrust (Game mode): Standard survival, in the Rust style; mp1 (Max players): The slot count is 1; ts8 (Group limit): Team cap: 8, which is the game default; v2635 (Protocol): You need protocol 2635 on your game to get in; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Modded: plugins or changed settings alter the game. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Last seen 44 hours ago, LOCAL raid difficulty validation is offline right now. Across the past week the average was 0 players.
Player hours over seven days put LOCAL raid difficulty validation at #15,426, in the top 69% of all ranked servers.
No gather rate appears in the name LOCAL raid difficulty validation. 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. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
There is no region from LOCAL raid difficulty validation. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 89.106.72.63:28125.
The setup on LOCAL raid difficulty validation is Rust network protocol 2635 and build 168909 with Windows. Joining requires the same protocol on your game; Steam takes care of updating it.
LOCAL raid difficulty validation is currently offline, with its last appearance 44 hours ago. 0 of 24 hours were online in the last 1 full day, giving 0% uptime. Rust Live Stats has tracked it since 26 October 2026.
Enter client.connect 89.106.72.63:28125 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.