Online 212.193.10.54:28015 checked 10m ago
yaga test
Connect
srv = rust.server("212.193.10.54: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 3 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 bestTop 14% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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 1,501, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 15:19 UTC26d ago | 1,501 | NaN | running | 1 |
| 1 | Sat 3 Oct, 03:55 UTC26d ago | 1,501 | NaN | 0.5 days | 0 |
| 2 | Fri 2 Oct, 16:45 UTC27d ago | 1,501 | NaN | 0.5 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())Map
2000 · seed 12345
- map
- Procedural Map
- size
- 2000
- seed
- 12345
Server
srv.info()- address
- 212.193.10.54:28015
- region
- –
- max players
- 2000
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 15:19 UTC
- hostname
- –
- first seen
- 2 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 141/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 199/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 87/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 228/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 347/350 |
Quick answers
From the figures on this page.
Population
What position does yaga test take in the server rankings?
Over the last seven days yaga test sits at #3,099 on player hours, in the top 14% of ranked servers.
How full does yaga test run?
Current row: 1 players on yaga test, against 2,000 slots. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 19:00 UTC is the busiest, at 1 players.
About the server
What does performance look like on yaga test?
Averaged over 48 hours: 89 server fps, never under 50. Buildings, deployables and all else in the world took the count as high as 17,629 entities. Memory peaked at 2,134 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What Rust version does yaga test run?
Rust network protocol 2634 and build 166652 on Linux is what yaga test runs. Steam updates your game for you, but the protocol must match to join.
Is yaga test up, and what does its uptime show?
yaga test reports itself online at the current refresh. The uptime it reports puts the last restart about 7 days 5 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 2 October 2026.
Where does yaga test sit?
For yaga test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 212.193.10.54:28015 is its address.
Settings and map
Which rules apply on yaga test, and what settings?
You will not find a gather rate in the string yaga test. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Which map has yaga test selected?
The game generates the map on yaga test: procedural, size 2,000, seed 12345. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does yaga test wipe, and on what schedule?
Irregular wipe times on yaga test leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 2 hours ago.
What is wipe day on yaga test like?
The average peak over recent wipes is 1,501 players. The crowd on the latest wipe topped out 2 hours after it began.
Tags, lists
Which lists on Rust Data hold yaga test, and which filters?
The Rust Data lists that yaga test fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on yaga test hold?
The game's server browser reads these tags from yaga test: gmrust (Game mode): Rust survival in its standard form; mp2000 (Max players): Slot count: 2,000; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join yaga test?
The manual route: launch Rust, F1, then client.connect 212.193.10.54:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.