yaga test
Key statistics
the figures behind the quote- Players now
- 4/ 2000 0% full
- Change · 24h
- ▪+0 +0.0% from 4
- 7-day average
- 4 peak 4
- Rank
- #1,639 top 7%
- Rank · 7d ago
- #1,019 ▼620 places down
- Last wipe
- 11d ago no schedule published
- Next wipe
- – no rhythm it keeps
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 664 player hours, last seven days
- Map
- 2000 Procedural Map · seed 12345
- First seen
- 2 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 4 players.
Daily average and peak, UTC.
Server performance
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 bestTop 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keeps- usual gap
- 0.5 days between real wipes
- on rhythm
- 100% of its recent wipes
- wipe-day peak
- 1,501 players, last three wipes
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 UTC11d ago | 1,501 | – | running | 1 |
| Sat 3 Oct, 03:55 UTC11d ago | 1,501 | – | 0.5 days | 0 |
| Fri 2 Oct, 16:45 UTC12d 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 | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | ShockRust | Blue | NoLimitno group limit · 127 on average | 139/300 | ▲+64+85.7% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 107 on average | 186/225 | ▲+66+54.6% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 88/100 | ▼−3−3.2% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 87 on average | 28/1000 | ▼−33−54.0% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 9/1000 | ▼−10−52.4% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 56/700 | ▼−3−5.1% |
Quick answers
from the figures on this pageRules & Settings
How is yaga test configured in terms of rules and settings?
No gather rate appears in the name of yaga test. Up to 8 players per group, which is the game's default. survival is the mode, gather, build and raid in the standard game. You can fight and raid other players. Modded is its category in the server browser; plugins or settings modify the game. Carbon plugins are running. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on yaga test?
The map on yaga test is procedural, size 2,000, with seed 12345, and generated by the game. The map is reproducible from its size and seed; RustMaps shows it from this page.
Population
What position does yaga test hold in the server rankings?
In the top 7% of all ranked servers, yaga test is #1,639 on player hours over the last seven days.
What is the population on yaga test?
4 of 2,000 slots on yaga test are filled at the moment. The mean over the last seven days is 4 players, reaching 4 at its highest. At 20:00 UTC in the last 48 hours, it averaged 4 players, the busiest hour.
Wipe Cycle
How does yaga test handle wipe day?
An average of 1,501 players marked the busiest point of its recent wipes. 2 hours after the latest wipe, the crowd reached its peak.
When does yaga test schedule its wipes?
There is no next wipe to predict for yaga test, which wipes at irregular times. At the monthly force wipe, every Rust server wipes. That happens next on Thursday 5 November at 19:00 UTC. 11 days 4 hours ago the current world was created.
Server Overview
What is the server location for yaga test?
No region is published by yaga test. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. 212.193.10.54:28015 is its address.
What is the performance like on yaga test?
Server fps over the last 48 hours: 92 on average, 57 at the lowest. 17,742 entities is the maximum carried: buildings, deployables and everything else. Memory use peaked at 2,401 MB. Low fps and growing entities are the source of felt lag.
yaga test runs which version of Rust?
The version in use at yaga test: Rust network protocol 2634 and build 166652, on Linux. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of yaga test?
Online at this moment: yaga test. Its own uptime figure dates the last restart to roughly 10 days 13 hours ago. The last 7 full days give 100% uptime, 168 hours on out of 168. The earliest Rust Analytics saw it was 2 October 2026.
Tags & Filters
How should you interpret the tags on yaga test?
These tags are published by yaga test and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp2000 (Max players): Capacity: 2,000 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166652 (Build): Game build: 166652; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): No region code has been set; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; ^y (Carbon): The plugin framework here is Carbon. Also in the tags and at the top of this page: current players, queue and world creation time.
yaga test appears in which of the lists and filters on Rust Analytics?
On Rust Analytics, yaga test matches these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connection
What is the process to join yaga test?
The console route: start Rust, press F1, enter client.connect 212.193.10.54:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp2000,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust
mp2000
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^z
^y
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.