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 17 Sep. 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.
The record holds too few of x5 MOSKOCOORP's wipes to reveal its rhythm. 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 90 days 5 hours.
On Rust Live Stats, x5 MOSKOCOORP is listed under 5x Rust servers, live now, Modded Rust servers live now and Rust PvE servers, live now. These filters on the server list bring it up: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
These are the tags x5 MOSKOCOORP makes public: gmrust (Game mode): Standard survival, in the Rust style; mp30 (Max players): The slot count is 30; ts8 (Group limit): Team cap: 8, which is the game default; v2631 (Protocol): Join only if your game is on protocol 2631; cs158240 (Build): This server runs game build 158240; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): No region code is set here; ^p (PvE): The world is the danger here; players do not fight each other; ^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.
x5 MOSKOCOORP is carrying 0 players at the moment, with 30 slots in total. The seven-day average for this server is 0 players.
On player hours for the past seven days, x5 MOSKOCOORP sits at #15,290, inside the top 69% of ranked servers.
Gather rates on x5 MOSKOCOORP are 5x, as its name states. Eight players per group, which is the game's default. It runs pve, no fighting other players. The server browser files it under Modded: plugins or settings alter the game. The plugin load is Oxide. Anti-cheat: VAC from Valve is enabled.
Size 3,500, seed 648252: that is the procedural map the game generates for x5 MOSKOCOORP. RustMaps shows it from this page, since equal size and seed give an equal map.
No region is published by x5 MOSKOCOORP. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 104.234.251.170:28025.
The average server fps was 109 over the last 48 hours; the lowest was 58. Entity count reached 74,709: buildings, deployables and the rest of the world. The highest memory usage was 4,199 MB. A climbing entity count and low fps are felt as lag by players.
Rust network protocol 2631 and build 158240 on Windows is what x5 MOSKOCOORP runs. Steam updates it for you, but your game needs the same protocol to join.
x5 MOSKOCOORP is up and running at this moment. Based on the uptime it reports, the last restart was about 33 hours ago. 167 of 168 hours were online in the last 7 full days, giving 99% uptime. The first sighting by Rust Live Stats was on 13 September 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 104.234.251.170:28025.