Station XX-13556 · no signal
Belldandy
Offline 68.106.240.11:28015 checked 10d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,556
- top 62%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 10.9 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 22:30 UTC FW27d ago | M0.0■steady | 1 | – | running | 1 | |
| Sun 20 Sep, 23:56 UTC38d ago | M0.0▲rising | 1 | held half | 10.9 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Belldandy?
The map on Belldandy is procedural, produced by the game.
Which settings and rules apply on Belldandy?
The name of Belldandy gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on Belldandy?
No players are recorded on Belldandy at this moment; it is offline, and the last sighting was 10 days 20 hours ago.
How does Belldandy rank against other Rust servers?
The last seven days of player hours place Belldandy at #13,556, in the top 62% of all ranked servers.
Operator and location
How reliably does Belldandy stay online?
Belldandy is down at the moment; the last recorded contact was 10 days 20 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 20 September 2026.
Which region does Belldandy run from?
Nothing about a region comes from Belldandy. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 68.106.240.11:28015.
Which Rust version is Belldandy running?
Rust network protocol 2634 and build 167781 on Windows is what Belldandy runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Belldandy?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
On what timetable does Belldandy run its wipes?
The rhythm of Belldandy cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 27 days 23 hours is how long the current world has been running.
Lists and tags
What do the server tags on Belldandy mean?
The game's server browser reads the tags Belldandy publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Belldandy appear?
These Rust Server Trends lists include Belldandy: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to Belldandy?
Enter client.connect 68.106.240.11:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.