Online 135.148.150.27:60404 checked 8m ago
cybrancee
Connect
srv = rust.server("135.148.150.27:60406")
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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 22h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 22h | Thu 3 Dec, 19:00 UTC | FW 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 | Sat 10 Oct, 15:08 UTC19d 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
2500 · seed 1
- map
- Procedural Map
- size
- 2500
- seed
- 1
Server
srv.info()- address
- 135.148.150.27:60404
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 10 Oct 2026, 15:08 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 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 373/425 |
| 1 | Rusty Moose |EU Monthly| | EU · groups of 12+ · monthly · 212 on average | 240/300 |
| 2 | [EU East] Facepunch 4 | EU · groups of 8+ · monthly · 161 on average | 136/350 |
| 3 | [EU] Facepunch 1 | EU · groups of 8+ · monthly · 160 on average | 173/400 |
| 4 | Rustopia.gg - US Large | NA · groups of 16+ · monthly · 126 on average | 96/200 |
| 5 | Rustafied.com - EU Long - Large | EU · groups of 16+ · monthly · 124 on average | 116/150 |
Quick answers
From the figures on this page.
Population data
How does cybrancee compare in the rankings?
Player hours over seven days put cybrancee at #15,269, in the top 68% of the ranked set.
How full does cybrancee run?
cybrancee reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players.
About the server
How smoothly does cybrancee run?
Server fps over the last 48 hours averages 224; the floor is 188. Entity numbers reached 30,156, and that includes buildings, deployables and the rest. Memory peaked at 2,541 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is cybrancee on?
Version Rust network protocol 2634 and build 167781 on Linux is reported by cybrancee. The protocol has to match before you can join, and Steam does the updating.
How reliable is cybrancee, and is it up?
cybrancee reports itself online at the current refresh. Count back 13 days 6 hours from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
Which location does cybrancee run from?
There is no region published for cybrancee. Rust Data does not look up where the machine stands; it shows where a server says it is. 135.148.150.27:60404 is its address.
Map and rules
Which rules apply on cybrancee, and what settings?
The name cybrancee carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
What is the map on cybrancee?
Size 2,500, seed 1: the procedural map on cybrancee, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
On what schedule does cybrancee wipe?
The only wipe cybrancee takes is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 19 days 4 hours ago. The tags list wipes as monthly.
On cybrancee, 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
Where does cybrancee appear among Rust Data lists and filters?
The Rust Data lists that cybrancee fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on cybrancee hold?
The game's server browser reads these tags from cybrancee: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to cybrancee?
The manual route: launch Rust, F1, then client.connect 135.148.150.27:60404. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.