Offline 114.177.122.3:28215 checked 30d ago
Daedalus Local Verification
Connect
srv = rust.server("114.177.122.3:28217")
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. 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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 114.177.122.3:28215
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Sep 2026, 09:00 UTC
- hostname
- –
- first seen
- 28 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 · 149 on average | 186/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 179/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 91/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 284/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 236/700 |
Quick answers
From the figures on this page.
Player counts
How does Daedalus Local Verification compare in the rankings?
Rank #16,966 on seven-day player hours for Daedalus Local Verification, within the top 71% of all ranked servers.
How full does Daedalus Local Verification run?
Daedalus Local Verification returns no live count at this refresh, having last been seen 30 days 21 hours ago.
About the server
Which Rust version is Daedalus Local Verification on?
Rust network protocol 2633 and build 165217 on Windows is what Daedalus Local Verification runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Daedalus Local Verification, and is it up?
The latest sample has Daedalus Local Verification offline, with a last sighting 30 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 28 September 2026.
Where does Daedalus Local Verification sit?
There is no region published for Daedalus Local Verification. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 114.177.122.3:28215.
Map and rules
Which rules apply on Daedalus Local Verification, and what settings?
You will not find a gather rate in the string Daedalus Local Verification. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on Daedalus Local Verification?
A procedural map runs on Daedalus Local Verification, generated by the game.
Wipes and dates
When does Daedalus Local Verification wipe, and how often?
A rhythm cannot be read from the wipes of Daedalus Local Verification on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 33 days 6 hours ago.
Lists and tags
Which lists on Rust Data hold Daedalus Local Verification, and which filters?
On Rust Data, Daedalus Local Verification appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Daedalus Local Verification hold?
These tags are published by Daedalus Local Verification and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to Daedalus Local Verification?
The manual route: launch Rust, F1, then client.connect 114.177.122.3:28215. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.