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
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.
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
The current map
Friday 2 October 2026, 08:55 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. Peak population on the latest wipe came 4 hours after it.
Riorus's wipe history is too thin on record to show a rhythm. Every server in Rust, this one among them, wipes at the monthly force wipe; Thursday 5 November at 19:00 UTC is the next. 26 days 12 hours have passed since this world was generated.
These are the Rust Live Stats lists Riorus fits: Live Rust community servers. Under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more it appears on the server list.
These are the tags Riorus makes public: gmrust (Game mode): Standard survival, in the Rust style; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team at most, the game's default setting; v2634 (Protocol): Join only if your game is on protocol 2634; cs167781 (Build): Build: 167781; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here. Also in the tags: players on now, the queue, and when the world was made. You will find them at the top of this page.
0 of Riorus's 50 slots are filled right now. Across the past week the average was 0 players.
On player hours for the past seven days, Riorus sits at #15,348, inside the top 69% of ranked servers.
Nothing in the name of Riorus states a gather rate. No custom limit is set, so groups hold the default 8 players. It runs survival, the standard game: gather, build, raid. You can raid and fight other players. Community is its browser category. Anti-cheat: VAC from Valve is enabled.
Riorus runs a game-generated procedural map: size 3,000, seed 1234. Same size, same seed, same map: RustMaps has it, reachable from this page.
Nothing on Riorus states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. 163.44.152.42:28015 is its address.
It never went below 45 server fps in the last 48 hours, averaging 58. It supported up to 44,076 entities, covering buildings, deployables and all other objects. Memory use peaked at 1,971 MB. A climbing entity count and low fps are felt as lag by players.
Rust network protocol 2634 and build 167781 on Linux is what Riorus runs. To join, your game must use the same protocol; Steam handles the update for you.
Riorus is up and running at this moment. About 2 days 20 hours ago is when it last restarted, according to its uptime. It was online for 168 of 168 hours in the last 7 full days, or 100% of the time. On 13 September 2026, Rust Live Stats saw it for the first time.
Enter client.connect 163.44.152.42: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.