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 18 Oct. 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 Codezalot Rust's wipes to reveal its 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. The world you are playing on was built 10 days 15 hours.
On Rust Live Stats, Codezalot Rust is listed under Modded Rust servers live now. Under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks it appears on the server list.
gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): Team cap: 8, which is the game default; v2634 (Protocol): You need protocol 2634 on your game to get in; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the network layer — the game's standard one; $r? (Region code): No region code is set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded: that is the tag list Codezalot Rust publishes for the game's server browser. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
Codezalot Rust is carrying 0 players at the moment, with 50 slots in total. Across the past week the average was 0 players.
Player hours over seven days put Codezalot Rust at #15,373, in the top 69% of all ranked servers.
No gather rate appears in the name Codezalot Rust. Eight players per group, which is the game's default. survival applies here, the standard game: gather, build, raid. You can raid and fight other players. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are in use. Anti-cheat: VAC from Valve is enabled.
Size 3,500, seed 1887230747: that is the procedural map the game generates for Codezalot Rust. Same size, same seed, same map: RustMaps has it, reachable from this page.
Nothing on Codezalot Rust states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. You can reach it at 72.218.192.227:28015.
Server fps averaged 123 over the last 48 hours, with a low of 103. Entity count reached 69,099: buildings, deployables and the rest of the world. Memory use peaked at 3,612 MB. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2634 and build 167781 on Linux is what Codezalot Rust runs. To join, your game must use the same protocol; Steam handles the update for you.
At the time of this update, Codezalot Rust is live. The uptime it reports puts the last restart at about 10 days 12 hours ago. It was online for 168 of 168 hours in the last 7 full days, or 100% of the time. On 18 October 2026, Rust Live Stats saw it for the first time.
Enter client.connect 72.218.192.227: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.