Offline 68.106.240.11:28015 checked 10d ago
Belldandy
Connect
srv = rust.server("68.106.240.11:28017")
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 best
Top 62% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 22:30 UTC FW27d ago | 1 | NaN | running | 1 |
| 1 | Sun 20 Sep, 23:56 UTC38d ago | 1 | held half | 10.9 days | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 68.106.240.11:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 22:39 UTC
- hostname
- –
- first seen
- 20 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 | 154/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 72/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 23/1000 |
Quick answers
From the figures on this page.
Player counts
How does Belldandy compare in the rankings?
Over the last seven days Belldandy sits at #13,556 on player hours, in the top 62% of ranked servers.
How many players does Belldandy hold at once?
The current row shows Belldandy offline; the last response was 10 days 9 hours ago.
Server data
Which Rust version is Belldandy on?
Rust network protocol 2634 and build 167781 on Windows is what Belldandy runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Belldandy, and is it online now?
The latest sample has Belldandy offline, with a last sighting 10 days 9 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 20 September 2026.
Where does Belldandy sit?
There is no region published for Belldandy. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 68.106.240.11:28015 is its address.
Map and rules
Which rules apply on Belldandy, and what settings?
No gather rate appears in the name: Belldandy. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
What is the map on Belldandy?
A procedural map runs on Belldandy, generated by the game.
Wipe schedule
On what schedule does Belldandy wipe?
The record for Belldandy holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 12 hours ago.
On Belldandy, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.
Tags, lists
Where does Belldandy appear among Rust Data lists and filters?
On Rust Data, Belldandy appears in these lists: 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 Belldandy?
Read by the game's server browser, the tags Belldandy publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is 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.
Connecting
How can I connect to Belldandy?
The manual route: launch Rust, F1, then client.connect 68.106.240.11:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.