Station XX-2420 · recording
yaga test
Online 212.193.10.54:28015 checked 8m ago
- Players now
- 1/ 2000
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 2
- peak 4
- Rank
- #2,420
- top 11%
- Last wipe
- 24d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 2000 slots
- Motion · 24 h
- M0.0■steady+0 players
- Peak · 48 h
- 1most players in any hour
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
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 11% 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.
- usual gap
- 0.5 daysbetween real wipes
- on rhythm
- 100%of its recent wipes
- wipe-day peak
- 1,501players, 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 3 Oct, 15:19 UTC24d ago | M3.2▲rising | 1,501 | – | running | 1 | |
| Sat 3 Oct, 03:55 UTC24d ago | M3.2▲rising | 1,501 | – | 0.5 days | 0 | |
| Fri 2 Oct, 16:45 UTC25d ago | M3.2▲rising | 1,501 | – | 0.5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on yaga test?
yaga test runs a procedural map of size 2,000 with seed 12345, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on yaga test?
The name of yaga test gives no gather rate. At the game's default, groups can have up to 8 players. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on yaga test right now?
A reading taken now shows 1 players on yaga test, which has 2,000 slots. Across seven days this server recorded an average of 2 players and a peak of 4. The last 48 hours show their highest activity at 19:00 UTC, averaging 1 players.
How does yaga test rank against other Rust servers?
Over the last seven days, yaga test recorded enough player hours to reach #2,420 worldwide, placing it in the top 11% of all ranked servers.
Server details
How reliably does yaga test stay online?
yaga test is up at the moment. The uptime it reports puts its last restart about 5 days 5 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 2 October 2026.
How well does yaga test perform under load?
Across the last 48 hours it averaged 82 server fps, with a floor of 32. The world held up to 17,728 entities at its peak, buildings and deployables included. It reached a ceiling of 1,959 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does yaga test run from?
No region is published by yaga test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 212.193.10.54:28015.
Which Rust version is yaga test running?
Rust network protocol 2634 and build 166652 on Linux is what yaga test runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on yaga test?
1,501 players, on average, was the busiest crowd at its recent wipes. 2 hours after the latest wipe, the crowd peaked.
On what timetable does yaga test run its wipes?
There is no next wipe to predict at yaga test, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. It has run its current world for 24 days 2 hours.
Tags
What do the server tags on yaga test mean?
The game's server browser reads the tags yaga test publishes: gmrust (Game mode): Survival in standard Rust; mp2000 (Max players): 2,000 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does yaga test appear?
These Rust Server Trends lists include yaga test: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
How do you connect to yaga test?
You can connect by pressing F1 in Rust and typing client.connect 212.193.10.54:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.