yaga test
212.193.10.54:28015 checked 10m ago
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
Top 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- 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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 15:19 UTC 11d ago | 1,501 | – | running | 1 |
| Sat 3 Oct, 03:55 UTC 11d ago | 1,501 | – | 0.5 days | 0 |
| Fri 2 Oct, 16:45 UTC 12d 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
Quick answers
Population
yaga test ranking: what position does it hold?
Over the last seven days, yaga test ranks #1,640 in player hours, which is in the top 7% of ranked servers.
Is yaga test busy?
4 of 2,000 slots are filled on yaga test at the moment. The average player count over the last seven days is 4, with a peak of 4. In the last 48 hours, 21:00 UTC saw the highest activity, with an average of 4 players.
Server Tags
How should the tags on yaga test be interpreted?
Read by the game's server browser, the tags yaga test publishes are: gmrust (Game mode): Standard survival gameplay; mp2000 (Max players): Slot count is 2,000; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Protocol 2634: join only if your game matches this version; cs166652 (Build): Running build 166652; ptrak (Networking): Network layer: RakNet, the standard; $r? (Region code): No region code listed; ^z (Modded): Plugins or settings alter the game, so it appears under Modded; ^y (Carbon): Uses Carbon for plugins. Current players, queue and world creation time come from the tags and appear at the top of this page.
yaga test in BestRustServers.xyz lists and filters: which ones?
These BestRustServers.xyz lists include yaga test: Best 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.
Server Overview
What Rust version is yaga test on?
Rust network protocol 2634 and build 166652 on Linux is what yaga test uses. Steam updates your game automatically, but it needs to match the protocol to join.
Is the performance on yaga test smooth?
Its average server fps over the last 48 hours was 92, with a low of 57. It held up to 17,742 entities: everything from buildings to deployables in the world. The maximum memory used was 2,482 MB. Players feel lag when fps is low and entity count climbs.
How reliable is yaga test and is it online?
At the moment, yaga test is up. The uptime it reports shows a restart roughly 10 days 14 hours ago. Over the past 7 full days, it was online 168 of 168 hours, 100% of the time. It was first seen by BestRustServers.xyz on 2 October 2026.
yaga test location: where is it?
There is no region published by yaga test. BestRustServers.xyz 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 & Map
Which map is used on yaga test?
On yaga test, the map is procedural, size 2,000 with seed 12345, generated by the game. On RustMaps, from this page, the same size and seed show the same map.
yaga test rules and settings: what are they?
The name yaga test carries no gather multiplier. With no stated limit, groups default to 8 players. Listed as survival, gather, build, raid: the standard game. Player combat and raiding are enabled. Listed as Modded in the browser: the game is changed by plugins or settings. Carbon plugins are used. VAC: on.
Wipe Cycle
yaga test wipe schedule: what does it show?
The wipe times of yaga test are irregular, so no next wipe can be predicted. A force wipe, next on Thursday 5 November at 19:00 UTC, takes every Rust server with it. Its world dates from 11 days 5 hours.
On yaga test, what occurs on wipe day?
Across its recent wipes, the busiest point averaged 1,501 players. 2 hours into the latest wipe, the crowd reached its peak.
How to Join
What is the process to join yaga test?
To connect, type client.connect 212.193.10.54:28015 in the F1 console. Launch Rust on this page opens Rust through Steam and joins you.
Server tags
Published as mp2000,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust- Game mode Standard survival gameplay.
mp2000- Max players Slot count is 2,000.
ts8- Group limit Default team size: 8.
v2634- Protocol Protocol 2634: join only if your game matches this version.
cs166652- Build Running build 166652.
ptrak- Networking Network layer: RakNet, the standard.
$r?- Region code No region code listed.
Mods and access
^z- Modded Plugins or settings alter the game, so it appears under Modded.
^y- Carbon Uses Carbon for plugins.
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.