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 19 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 22% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 12h. The force wipe · high confidence
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The current map
Monday 26 October 2026, 00:50 UTC
Wipe
Saturday 24 October 2026, 20:54 UTC
Wipe
Wednesday 21 October 2026, 01:36 UTC
Wipe
Tuesday 20 October 2026, 17:08 UTC
Wipe
Monday 19 October 2026, 23:02 UTC
Wipe
Saturday 17 October 2026, 18:19 UTC
Wipe
Saturday 10 October 2026, 19:25 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 2 players at their busiest. 0 hours after the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 100% of its recent wipes.
The monthly force wipe is the only wipe dunklips takes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world you are playing on was built 2 days 5 hours. Its tags give wipes as monthly.
On Rust Live Stats, dunklips is listed under Modded Rust servers live now. You will find it on the server list under Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 3 days.
gmrust (Game mode): Standard survival, in the Rust style; mp40 (Max players): The slot count is 40; 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): The game build is 168909; ptrak (Networking): RakNet, the game's usual network layer, carries this server; $r? (Region code): Region code: none set; ^m (Monthly): A single monthly wipe, set by Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules — this is the game as Facepunch ships it; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game changes here through plugins or settings, so it is Modded: that is the tag list dunklips publishes for the game's server browser. 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.
dunklips is carrying 0 players at the moment, with 40 slots in total. Averaged across seven days, 0 players; the peak was 2. Peak hour over 48 hours: 22:00 UTC, at 1 players on average.
Ranked by seven-day player hours, dunklips is #4,847, placing it in the top 22% of ranked servers.
No gather rate appears in the name dunklips. The default applies: 8 players to a group. survival applies here, the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser files it under Modded: plugins or settings alter the game. The plugin load is Oxide. By its own label it is vanilla: no changed rates, kits or rules — this is the game as Facepunch ships it. VAC is off: Valve's anti-cheat.
dunklips runs a game-generated procedural map: size 4,000, seed 65666643. RustMaps shows it from this page, since equal size and seed give an equal map.
No region is published by dunklips. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. 216.225.145.45:2000 is its address.
It never went below 39 server fps in the last 48 hours, averaging 76. It supported up to 91,875 entities, covering buildings, deployables and all other objects. Up to 3,913 MB of memory was used. Players experience lag when fps is low and the entity count climbs.
Rust network protocol 2635 and build 168909 on Linux is what dunklips runs. To join, your game must use the same protocol; Steam handles the update for you.
Right now dunklips is online. Based on the uptime it reports, the last restart was about 2 hours ago. It was online for 168 of 168 hours in the last 7 full days, or 100% of the time. Rust Live Stats has tracked it since 19 September 2026.
Enter client.connect 216.225.145.45:2000 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you.