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 15 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 27% 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 Wardaddy's Rust 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. 16 days 1 hours have passed since this world was generated.
These are the Rust Live Stats lists Wardaddy's Rust fits: Live Rust community servers. These filters on the server list bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
The server browser reads gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The slot count is 10; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): The server sets no region code, which Wardaddy's Rust publishes. 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 Wardaddy's Rust's 10 slots are filled right now. Averaged across seven days, 0 players; the peak was 1. The busiest hour in the past 48 was 19:00 UTC, averaging 1 players.
On player hours for the past seven days, Wardaddy's Rust sits at #5,987, inside the top 27% of ranked servers.
No gather rate appears in the name Wardaddy's Rust. The default applies: 8 players to a group. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser lists it under Community. Anti-cheat: VAC from Valve is enabled.
Size 6,000, seed 1337: that is the procedural map the game generates for Wardaddy's Rust. RustMaps shows it from this page, since equal size and seed give an equal map.
Nothing on Wardaddy's Rust states a region. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 70.8.175.28:28015 is its address.
Server fps averaged 133 over the last 48 hours, with a low of 114. Entity count reached 208,282: buildings, deployables and the rest of the world. Up to 4,504 MB of memory was used. A climbing entity count and low fps are felt as lag by players.
Rust network protocol 2635 and build 168909 on Linux is what Wardaddy's Rust runs. Joining requires the same protocol on your game; Steam takes care of updating it.
Wardaddy's Rust is up and running at this moment. Based on the uptime it reports, the last restart was about 6 hours ago. It was online for 143 of 168 hours in the last 7 full days, or 85% of the time. Rust Live Stats has tracked it since 12 October 2026.
Enter client.connect 70.8.175.28: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.