Online 170.23.54.69:11030 checked 11m ago
dukmber
Connect
srv = rust.server("170.23.54.69:11031")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 04:58 UTC26d ago | 0 | NaN | running | 0 |
# 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.
display(srv.map, srv.info())Map
4000 · seed 1119
- map
- Procedural Map
- size
- 4000
- seed
- 1119
Server
srv.info()- address
- 170.23.54.69:11030
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 04:58 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 154 on average | 19/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 34/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 13/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does dukmber rank?
Over the last seven days dukmber sits at #15,358 on player hours, in the top 69% of ranked servers.
What population does dukmber carry?
dukmber reports 0 players at this refresh, with 30 slots configured. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on dukmber?
Averaged over 48 hours: 55 server fps, never under 34. Buildings, deployables and all else in the world took the count as high as 176,127 entities. A high of 4,557 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What Rust version does dukmber run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by dukmber. Steam updates your game for you, but the protocol must match to join.
How reliable is dukmber, and is it up?
The current sample puts dukmber online. Count back 8 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Where does dukmber sit?
There is no region published for dukmber. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 170.23.54.69:11030.
Map and rules
Which rules apply on dukmber, and what settings?
You will not find a gather rate in the string dukmber. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has dukmber loaded?
dukmber runs a procedural map of size 4,000 with seed 1119, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does dukmber wipe, and how often?
Too few wipes are on record for dukmber to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 26 days 22 hours ago.
On dukmber, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which Rust Data filters and lists contain dukmber?
The Rust Data lists that dukmber fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on dukmber?
These tags are published by dukmber and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp30 (Max players): The server lists 30 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join dukmber?
The manual route: launch Rust, F1, then client.connect 170.23.54.69:11030. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.