Statistical profileOnline
yaga test
212.193.10.54:28015 checked 11m ago
Connect to this server
1. Main points
Players now
1/ 2000
0% full
7-day average
1
peak 1
Rank
#3,097
top 14%
Last wipe
26d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- There were 1 players on it, 0% of its 2,000 slots.
- Over the last seven days it averaged 1 players, with a peak of 1.
- It ranks #3,097 of all ranked servers, the top 14%, on player hours over the last seven days.
- Its current map went up 26d ago.
2. Players
Figure 1: Players on yaga test
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 14% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno rhythm it keeps
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
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1,501, 2 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| 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 UTC27d ago | 1,501 | – | 0.5 days | 0 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
8. Server characteristics
Table 3: Characteristics of yaga test
What the server publishes and what was recorded
| 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 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 150 on average | 152 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 98 / 700 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 238 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 347 / 350 |
10. Quick answers
From the figures on this page.
Wipe schedule
This release records the wipe timetable for yaga test: what is it?
No next wipe can be predicted for yaga test, which wipes at irregular times. The monthly force wipe on Thursday 5 November at 19:00 UTC is the next point at which every Rust server wipes. 26 days 1 hours have passed since this world was made.
How is wipe day run on yaga test?
Recent wipes drew an average peak of 1,501 players. The peak of the latest wipe's crowd came 2 hours after it began.
About the server
Is yaga test up, and how well has it held up?
This release records yaga test as online. About 7 days 4 hours ago is when it last restarted, according to the uptime it reports. 167 of 168 hours on across the last 7 full days gives an uptime of 99%. The first sighting of it by Rust Census was on 2 October 2026.
Does yaga test hold a steady frame rate and connection?
Over the last 48 hours, server fps averaged 89; the lowest reading was 50. The world carried up to 17,629 entities, including buildings, deployables and all else. The peak memory use recorded was 2,134 MB. Lag, as players feel it, comes from low fps and a climbing entity count.
What location has been recorded for yaga test?
A region is not published by yaga test. No lookup of where the machine stands is made by Rust Census; it shows where a server says it is. At 212.193.10.54:28015 it is addressed.
What version of Rust has been recorded on yaga test?
The version in use on yaga test is Rust network protocol 2634 and build 166652 on Linux. To join, your game has to be on the same protocol; Steam handles the update.
Player counts
What are the current player figures for yaga test?
yaga test stands at 1 players from 2,000 slots in this release. This release records a seven-day average of 1 players and a peak of 1. An average of 1 players was recorded at 17:00 UTC, the busiest hour of the last 48.
How does yaga test compare with other servers in the rankings?
The rank for yaga test is #3,097 on seven-day player hours, in the top 14% of ranked servers.
Lists and tags
Where does yaga test appear among the Rust Census lists and filters?
The Rust Census lists that yaga test fits are: Modded Rust servers, counted. Under these filters it comes 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 carry?
These are the tags yaga test publishes for the game's server browser to read: gmrust (Game mode): Survival play, in the standard Rust format; mp2000 (Max players): 2,000 slots are available; ts8 (Group limit): 8 per team, which is the game's default limit; v2634 (Protocol): Protocol 2634 is required; a different version cannot join; cs166652 (Build): Game build: 166652; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server carries no region code; ^z (Modded): This server is listed as modded, with plugins or settings that change the game; ^y (Carbon): Plugins are handled by Carbon on this server. The tags also hold the current player count, the queue and the world's creation time, which appear at the top of this page.
Map and rules
Which map is in use on yaga test?
Size 2,000 and seed 12345: that is the procedural map on yaga test, generated by the game. Because one size and seed give one map, RustMaps can display it from this page.
How is yaga test configured, and what rules does it keep?
No gather rate is recorded for yaga test in its name. The group cap stands at 8 players, the default for the game. It runs survival, the standard game: gather, build, raid. Raiding and player combat are permitted. The server browser lists it under Modded: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Connecting
How can you connect to yaga test?
You can open the console in Rust with F1 and enter client.connect 212.193.10.54:28015; or press Launch Rust and join on this page, and you are connected through Steam.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp2000,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y
Game
gmrust | Game mode Survival play, in the standard Rust format. |
|---|---|
mp2000 | Max players 2,000 slots are available. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2634 | Protocol Protocol 2634 is required; a different version cannot join. |
cs166652 | Build Game build: 166652. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code This server carries no region code. |
Mods and access
^z | Modded This server is listed as modded, with plugins or settings that change the game. |
|---|---|
^y | Carbon Plugins are handled by Carbon on this server. |
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.