Online 51.222.244.178:60415 checked 9m ago
Yabadabadoo
Connect
srv = rust.server("51.222.244.178:60417")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 5h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 11d 15h | Tue 10 Nov, 05:32 UTC | wipe |
| 2 | 25d 15h | Tue 24 Nov, 05:32 UTC | wipe |
| 3 | 35d 5h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 39d 15h | Tue 8 Dec, 05:32 UTC | 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 | Tue 13 Oct, 05:32 UTC16d 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
1800 · seed 1
- map
- Procedural Map
- size
- 1800
- seed
- 1
Server
srv.info()- address
- 51.222.244.178:60415
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 13 Oct 2026, 05:32 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 Medium | EU · groups of 12+ · biweekly · 238 on average | 183/200 |
| 1 | Rustafied.com - EU Medium - Large | EU · groups of 16+ · biweekly · 124 on average | 44/100 |
| 2 | Rustopia.gg - US Medium | NA · groups of 12+ · biweekly · 87 on average | 17/200 |
| 3 | Rustoria.co - SEA Medium | EA · groups of 16+ · biweekly · 68 on average | 398/450 |
| 4 | Rusty Moose |US Biweekly| | NA · groups of 12+ · biweekly · 56 on average | 9/200 |
| 5 | Gringers Solo Only | Noob Friendly Oct 22 | NA · groups of 8+ · biweekly · 43 on average | 22/100 |
Quick answers
From the figures on this page.
Population
How does Yabadabadoo compare in the rankings?
Over the last seven days Yabadabadoo sits at #15,326 on player hours, in the top 69% of ranked servers.
How full does Yabadabadoo run?
Yabadabadoo reports 0 players at this refresh, with 10 slots configured. Over the last seven days it averaged 0 players.
Server facts
What does performance look like on Yabadabadoo?
The 48-hour average is 235 server fps, with a low of 224. The entity count peaked at 11,782, covering buildings, deployables and the rest of the world. The memory field tops out at 1,946 MB. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on Yabadabadoo?
Rust network protocol 2634 and build 167584 on Linux is what Yabadabadoo runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Yabadabadoo, and is it up?
The current sample puts Yabadabadoo online. The uptime it reports puts the last restart about 16 days 6 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 13 September 2026.
Which location does Yabadabadoo run from?
No region is published by Yabadabadoo. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 51.222.244.178:60415 is its address.
Rules, settings, map
What rules and settings are recorded for Yabadabadoo?
The name Yabadabadoo carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. Anti-cheat status: VAC on.
Which map has Yabadabadoo loaded?
The game generates the map on Yabadabadoo: procedural, size 1,800, seed 1. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does Yabadabadoo wipe, and on what schedule?
Too few wipes are on record for Yabadabadoo to confirm its schedule, so the tag drives the prediction. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 16 days 8 hours ago. A fortnightly wipe schedule is published in its tags.
On Yabadabadoo, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold Yabadabadoo, and which filters?
These Rust Data lists include Yabadabadoo: Rust community servers, unfiltered and Vanilla Rust servers. Under these filters on the server list, it is listed: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Every two weeks.
How should you read the server tags on Yabadabadoo?
The game's server browser reads these tags from Yabadabadoo: gmvanilla (Game mode): The mode is vanilla survival; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): Build number: 167584; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): The cycle is fourteen days; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join Yabadabadoo?
The manual route: launch Rust, F1, then client.connect 51.222.244.178:60415. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.