Online 45.126.209.12:28015 checked 12m ago
BELLAKOS
Connect
srv = rust.server("45.126.209.12: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, measured since 11 Oct. 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 17% 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 5, 26 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 03:29 UTC3d ago | 5 | 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
2000 · seed 1984981545
- map
- Procedural Map
- size
- 2000
- seed
- 1984981545
Server
srv.info()- address
- 45.126.209.12:28015
- region
- –
- max players
- 30
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 03:29 UTC
- hostname
- –
- first seen
- 11 Oct 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 542 on average | 164/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 142/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 16/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 283 on average | 19/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 274 on average | 14/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 249 on average | 62/200 |
Quick answers
From the figures on this page.
Population data
How does BELLAKOS compare in the rankings?
Rank #3,851 on seven-day player hours for BELLAKOS, within the top 17% of all ranked servers.
How many players does BELLAKOS hold at once?
BELLAKOS reports 1 players at this refresh, with 30 slots configured. Over the last seven days it averaged 1 players and peaked at 5. The 48-hour sample puts the busiest hour at 06:00 UTC, averaging 3 players.
Server data
What does performance look like on BELLAKOS?
The 48-hour average is 118 server fps, with a low of 110. The entity count peaked at 18,325, covering buildings, deployables and the rest of the world. A high of 1,270 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does BELLAKOS run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by BELLAKOS. Steam updates your game for you, but the protocol must match to join.
How reliable is BELLAKOS, and is it up?
Online is the state at the latest refresh for BELLAKOS. The uptime it reports puts the last restart about 2 days 10 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 11 October 2026.
Where does BELLAKOS sit?
No region is published by BELLAKOS. Rust Data does not look up where the machine stands; it shows where a server says it is. 45.126.209.12:28015 is its address.
Map and rules
Which settings and rules does BELLAKOS run?
You will not find a gather rate in the string BELLAKOS. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. Anti-cheat status: VAC on.
Which map has BELLAKOS loaded?
Size 2,000, seed 1984981545: the procedural map on BELLAKOS, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does BELLAKOS wipe?
Too few wipes are on record for BELLAKOS to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 3 days 2 hours ago.
On BELLAKOS, what happens on wipe day?
The average peak over recent wipes is 5 players. 26 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does BELLAKOS appear among Rust Data lists and filters?
On Rust Data, BELLAKOS appears in these lists: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on BELLAKOS?
These tags are published by BELLAKOS and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp30 (Max players): 30 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to BELLAKOS?
The manual route: launch Rust, F1, then client.connect 45.126.209.12:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.