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.
Friduwulf's Private Server's wipe history is too thin on record to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. 127 days 8 hours have passed since this world was generated.
The Rust Live Stats lists that include Friduwulf's Private Server are Live Rust community servers. Under the filters Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more it appears on the server list.
These are the tags Friduwulf's Private Server makes public: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The slot count is 100; ts8 (Group limit): Teams stop at 8, the default the game ships with; v2627 (Protocol): Join only if your game is on protocol 2627; cs154033 (Build): The game build is 154033; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework: Oxide (uMod). Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
Live now: 0 players on Friduwulf's Private Server, out of 100 slots. Across the past week the average was 0 players.
On player hours for the past seven days, Friduwulf's Private Server sits at #15,349, inside the top 69% of ranked servers.
No gather rate appears in the name Friduwulf's Private Server. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser lists it under Community. Plugins run here: Oxide. Anti-cheat: VAC from Valve is enabled.
Size 4,500, seed 15332: that is the procedural map the game generates for Friduwulf's Private Server. RustMaps shows it from this page, since equal size and seed give an equal map.
There is no region from Friduwulf's Private Server. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. Connect to 160.202.167.13:49155.
It never went below 51 server fps in the last 48 hours, averaging 57. It supported up to 114,930 entities, covering buildings, deployables and all other objects. The highest memory usage was 4,791 MB. Players experience lag when fps is low and the entity count climbs.
Friduwulf's Private Server operates on Windows with Rust network protocol 2627 and build 154033. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, Friduwulf's Private Server is live. The uptime it reports puts the last restart at about 4 days 20 hours ago. It was online for 167 of 168 hours in the last 7 full days, or 99% of the time. Rust Live Stats has tracked it since 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 160.202.167.13:49155.