yaga test
Online 212.193.10.54:28015 checked 10m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 bestTop 14% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 15:19 UTC26d ago | 1,501 | – | running | 1 |
| Sat 3 Oct, 03:55 UTC26d ago | 1,501 | – | 0.5 days | 0 |
| Fri 2 Oct, 16:45 UTC26d ago | 1,501 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 149 on average | 186 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 179 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 91 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 284 / 200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 86 on average | 236 / 700 |
Quick answers
from the figures on this pageWipe data
When does yaga test wipe?
With irregular wipe times, yaga test offers no next wipe to predict. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 26 days ago the current world was made.
Wipe day on yaga test: what should you expect?
The average busiest count over recent wipes is 1,501 players. The highest player count on the latest wipe arrived 2 hours in.
Server
Which location hosts yaga test?
No region is published by yaga test. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. The address of the server is 212.193.10.54:28015.
What Rust build does yaga test run?
On Linux, yaga test runs Rust network protocol 2634 and build 166652. Joining requires the same protocol on your game; Steam handles the update.
Is yaga test up, and how steady is its uptime?
As of the latest refresh, yaga test is online. About 7 days 2 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 99%, or 167 of 168 hours. 2 October 2026 is when Rust Server Analytics first recorded it.
Does yaga test perform well?
Over 48 hours the average held at 89 server fps, and the minimum was 50. At its highest the entity count was 17,728, including buildings, deployables and all else. At its highest, memory use was 2,134 MB. Players experience lag as low fps combined with a rising entity count.
Tags
How should the tags on yaga test be read?
Tags from yaga test, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp2000 (Max players): Capacity of 2,000 slots; ts8 (Group limit): Default team size of 8; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs166652 (Build): The game build is 166652; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^z (Modded): Modded listing, where plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On Rust Server Analytics, which lists and filters feature yaga test?
The following Rust Server Analytics lists count yaga test among their servers: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Population
Against other Rust servers, how does yaga test compare?
The seven-day player-hours rank for yaga test is #3,096, inside the top 14% of all ranked servers.
What is the population of yaga test?
yaga test holds 1 players of its 2,000 slots as of the latest update. The seven-day mean is 1 players, against a peak of 1. Across the last 48 hours, 16:00 UTC shows the highest average: 1 players.
Settings
What settings and rules does yaga test use?
No gather rate is given in the name of yaga test. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser it sits under Modded, where plugins or settings alter the game. Carbon plugins are run. VAC, Valve's anti-cheat, is enabled.
What is the map for yaga test?
A procedural map of size 2,000 with seed 12345, generated by the game, runs on yaga test. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Connection
How do you connect to yaga test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 212.193.10.54:28015.