Online EU 77.66.179.119:28015 checked 12m ago
[RU] YOBA | rate x2 | kits | stacks | anti offline raid
Connect
srv = rust.server("77.66.179.119:28016")
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 best
Top 18% of all ranked servers, top 50% in EU. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 14d 5h | Thu 12 Nov, 16:16 UTC | wipe |
| 2 | 35d 8h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 3 | 42d 5h | Thu 10 Dec, 16:16 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 21 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 16:16 UTC13d ago | 4 | NaN | running | 1 |
| 1 | Thu 1 Oct, 18:10 UTC FW27d ago | 3 | halved by day 3 | 13.9 days | 0 |
| 2 | Thu 17 Sep, 16:10 UTC41d ago | 6 | halved by day 3 | 14.1 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())
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 2X Medium | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · biweekly · 158 on average | 24/100 |
| 1 | ДЛЯ НОВИЧКОВ | КЛАССИКА X2 |KARMA RUST 24.10 | EU · groups of 10+ · 2x · biweekly · 51 on average | 23/200 |
| 2 | PROSTOJ #6 | Ресурсы x2 | Компоненты x1 | EU · groups of 8+ · 2x · biweekly · 49 on average | 13/200 |
| 3 | Magic Rust #22 — Vanilla 2x (Biweekly) | Pyccкий | EU · groups of 150+ · 2x · biweekly · 42 on average | 11/200 |
| 4 | Россия | Классика X2 | IMBA RUST 23.10 | EU · groups of 100+ · 2x · biweekly · 31 on average | 17/200 |
| 5 | РОССИЙСКИЙ x2 | GGRust #5 | Для нoвичкoв 2x | EU · groups of 300+ · 2x · biweekly · 30 on average | 7/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does [RU] YOBA | rate x2 | kits | stacks | anti offline raid rank?
On seven-day player hours [RU] YOBA | rate x2 | kits | stacks | anti offline raid is #4,009 overall and #1,469 in Europe, inside the top 18% of all ranked servers.
What population does [RU] YOBA | rate x2 | kits | stacks | anti offline raid carry?
[RU] YOBA | rate x2 | kits | stacks | anti offline raid reports 2 players at this refresh, with 60 slots configured. Over the last seven days it averaged 1 players and peaked at 4. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 2 players.
Server facts
How smoothly does [RU] YOBA | rate x2 | kits | stacks | anti offline raid run?
Server fps over the last 48 hours averages 60; the floor is 42. The entity count peaked at 131,685, covering buildings, deployables and the rest of the world. The memory field tops out at 4,867 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is [RU] YOBA | rate x2 | kits | stacks | anti offline raid on?
Rust network protocol 2635 and build 168909 on Linux is what [RU] YOBA | rate x2 | kits | stacks | anti offline raid runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is [RU] YOBA | rate x2 | kits | stacks | anti offline raid, and is it online now?
The current sample puts [RU] YOBA | rate x2 | kits | stacks | anti offline raid online. Count back 6 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is [RU] YOBA | rate x2 | kits | stacks | anti offline raid hosted?
The EU tag is what [RU] YOBA | rate x2 | kits | stacks | anti offline raid uses to list itself in Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 77.66.179.119:28015.
Settings and map
Which settings and rules does [RU] YOBA | rate x2 | kits | stacks | anti offline raid run?
Gather sits at 2x, read from the server's own name: [RU] YOBA | rate x2 | kits | stacks | anti offline raid. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. Anti-cheat status: VAC on.
Which map has [RU] YOBA | rate x2 | kits | stacks | anti offline raid loaded?
The game generates the map on [RU] YOBA | rate x2 | kits | stacks | anti offline raid: procedural, size 4,500, seed 641062915. The same size and seed produce the same map; this page links to RustMaps so it can be viewed. Under map name you will find: Custom Map.
Wipes and dates
When does [RU] YOBA | rate x2 | kits | stacks | anti offline raid wipe, and on what schedule?
Wipes on [RU] YOBA | rate x2 | kits | stacks | anti offline raid run every 4 weeks on Thursday at 16:16 UTC. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 13 days 18 hours ago. Its tags carry a wipe schedule of every two weeks.
On [RU] YOBA | rate x2 | kits | stacks | anti offline raid, what happens on wipe day?
The average peak over recent wipes is 4 players. Peak population on the latest wipe came 21 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 3 in the other cases.
Tags and filters
Which lists on Rust Data hold [RU] YOBA | rate x2 | kits | stacks | anti offline raid, and which filters?
On Rust Data, [RU] YOBA | rate x2 | kits | stacks | anti offline raid appears in these lists: EU Rust servers, Modded Rust servers and 2x Rust servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 2x.
How should you read the server tags on [RU] YOBA | rate x2 | kits | stacks | anti offline raid?
The game's server browser reads these tags from [RU] YOBA | rate x2 | kits | stacks | anti offline raid: gmrust (Game mode): Survival play, standard Rust; mp60 (Max players): 60 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon; EU (Europe): In the server browser it sits under Europe. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way into [RU] YOBA | rate x2 | kits | stacks | anti offline raid?
Enter client.connect 77.66.179.119:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://discord.com/invite/qQhCJt2Env.
