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 0, 0 hours in.
The current map
Friday 2 October 2026, 06:15 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.
The average peak across its recent wipes is 0 players. The crowd on the latest wipe peaked 0 hours in.
The record holds too few of kenzoku server'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. 27 days 3 hours have passed since this world was generated.
These are the Rust Live Stats lists kenzoku server fits: Live Rust community servers. These filters on the server list bring it up: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more.
These are the tags kenzoku server makes public: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots are available; 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): The network layer is RakNet, the standard the game uses; $r? (Region code): No region code is set here; ^o (Oxide): It runs the 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.
kenzoku server is carrying 0 players at the moment, with 50 slots in total. Across the past week the average was 0 players.
On player hours for the past seven days, kenzoku server sits at #15,338, inside the top 69% of ranked servers.
No gather rate appears in the name kenzoku server. Eight players per group, which is the game's default. It runs survival, the standard game: gather, build, raid. Fighting and raiding between players are allowed. Community is its browser category. Oxide plugins are in use. VAC is enabled: Valve's anti-cheat.
Size 4,000, seed 1024842347: that is the procedural map the game generates for kenzoku server. Size and seed repeat the same map, so RustMaps can show it from this page.
Nothing on kenzoku server states a region. A server's stated location is what Rust Live Stats shows; the machine's actual position is not looked up. 124.110.28.118:28015 is its address.
The average server fps was 107 over the last 48 hours; the lowest was 33. It supported up to 94,142 entities, covering buildings, deployables and all other objects. Memory use peaked at 2,886 MB. A climbing entity count and low fps are felt as lag by players.
kenzoku server operates on Linux with Rust network protocol 2635 and build 168909. Steam updates it for you, but your game needs the same protocol to join.
At the time of this update, kenzoku server is live. About 1 hours ago is when it last restarted, according to its uptime. 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.
Enter client.connect 124.110.28.118: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.