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, measured since 27 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 29% 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, 19:33 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 Matthew's Rust Server to establish a pattern. Thursday 5 November at 19:00 UTC is the next monthly force wipe, and no Rust server is spared it. The world you are playing on was built 15 hours.
These are the Rust Live Stats lists Matthew's Rust Server fits: Modded Rust servers live now. You will find it on the server list under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
These are the tags Matthew's Rust Server makes public: gmrust (Game mode): Standard survival, in the Rust style; mp40 (Max players): The slot count is 40; 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, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game changes here through plugins or settings, so it is Modded. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
0 of Matthew's Rust Server's 40 slots are filled right now. The seven-day average is 1 players, with a peak of 3. Peak hour over 48 hours: 00:00 UTC, at 3 players on average.
Ranked by seven-day player hours, Matthew's Rust Server is #6,381, placing it in the top 29% of ranked servers.
Nothing in the name of Matthew's Rust Server states a gather rate. The default applies: 8 players to a group. survival is the mode, with the standard game: gather, build, raid. You can raid and fight other players. The server browser files it under Modded: plugins or settings alter the game. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
Matthew's Rust Server runs a game-generated procedural map: size 3,000, seed 69420. Size and seed repeat the same map, so RustMaps can show it from this page.
No region is published by Matthew's Rust Server. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. Connect to 157.85.86.77:20544.
Server fps averaged 174 over the last 48 hours, with a low of 129. It supported up to 48,840 entities, covering buildings, deployables and all other objects. The highest memory usage was 3,153 MB. A climbing entity count and low fps are felt as lag by players.
The setup on Matthew's Rust Server is Rust network protocol 2635 and build 168909 with Linux. Joining requires the same protocol on your game; Steam takes care of updating it.
Right now Matthew's Rust Server is online. Based on the uptime it reports, the last restart was about 2 hours ago. The first sighting by Rust Live Stats was on 27 October 2026.
Enter client.connect 157.85.86.77:20544 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.