Rust StatisticsWorking papers on every public Rust server · 66,602 players now

yaga test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 10m ago · 212.193.10.54:28015

Abstract

We describe the public Rust server yaga test, reached at 212.193.10.54:28015. At the last check it held 1 of 2000 places, against a seven-day mean of 1 and a peak of 11. It ranks #3,095 of all servers, the top 14%. It last wiped 25d ago.

Keywordsmodded carbon

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/20000% full
In the queue0no queue
Seven-day mean1peak 1, 48 h peak 1
Rank2#3,095top 14%
Last wipe25d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

AveragePeak
00.250.50.75113:0022:0007:0015:0001:0010:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
05010015020013:0022:0007:0015:0001:0010:00
Figure 2: 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.

4Rank

The server stands in the top 14% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k2 Oct7 Oct13 Oct18 Oct24 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap0.5 daysbetween real wipes
On rhythm100%of its recent wipes
Wipe-day peak1,501players, last three wipes
Sat 3 OctSat 3 OctFri 2 Oct
0200400600800+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sat 3 Oct, 15:1925d ago 1,501 – running 1
Sat 3 Oct, 03:5526d ago 1,501 – 0.5 d 0
Fri 2 Oct, 16:4526d ago 1,501 – 0.5 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

Map of yaga test
Figure 5: The map: Procedural Map, size 2000, seed 12345. Open on RustMaps.
Table 4: The server's published settings.
Address212.193.10.54:28015
Region–
Max players2000
Group limit8, the default
Wipe schedule–
Last wipe3 Oct 2026, 15:19 UTC
Hostname–
First seen2 Oct 2026
MapProcedural Map
Size2000
Seed12345

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 149 on average168/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average135/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average184/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average71/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average13/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average21/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of yaga test smooth?

Over the past 48 hours, it ran at an average of 88 server fps, with a low of 57. Buildings, deployables and all other world objects counted together reached a maximum of 17,728 entities. Its highest memory usage was 2,134 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is yaga test based?

There is no region published for yaga test. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 212.193.10.54:28015 is its address.

A.3What is the reliability of yaga test, and is it online?

yaga test is online at this time. Based on the uptime it reports, the last restart occurred about 6 days 23 hours ago. Of the 168 hours in the last 7 full days, 167 were served, an availability of 99%. It was first observed on 2 October 2026 by Rust Statistics.

A.4What is the Rust version for yaga test?

Rust network protocol 2634 and build 166652 is the version that yaga test runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.5What schedule does yaga test follow for wipes?

No next wipe can be predicted for yaga test since its wipes occur at irregular intervals. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The current world has been running for 25 days 21 hours.

A.6What happens on yaga test when wipe day arrives?

Across its recent wipes, the average peak population was 1,501 players. The peak on the latest wipe came 2 hours after it began.

Player count

A.7How does yaga test compare with other Rust servers in the rankings?

Ranked by player hours across seven days, yaga test holds #3,095, in the top 14% of all ranked servers.

A.8At what level does yaga test operate in terms of players?

On yaga test, 1 of the 2,000 slots are occupied at present. Averaged over the last seven days: 1 players; the same period peaks at 1. The busiest hour of the last 48 is 13:00 UTC, averaging 1 players.

Tags, lists

A.9What is the meaning of the tags on yaga test?

Tags from yaga test, read by the game's server browser, are gmrust (Game mode): This is survival as standard Rust plays; mp2000 (Max players): 2,000 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166652 (Build): This server runs game build 166652; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^z (Modded): Modded listing: plugins or settings modify the game; ^y (Carbon): Plugins run through Carbon. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.10Where can yaga test be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that yaga test fits. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Settings and map

A.11Which settings and rules are in force on yaga test?

Its name carries no gather rate for yaga test. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Carbon on this server. VAC, Valve's anti-cheat, is enabled.

A.12What is the map for yaga test?

Size 2,000 and seed 12345 define the procedural, game-generated map on yaga test. Because size and seed determine the map, RustMaps can show it, linked from this page.

Connection

A.13What is the process for joining yaga test?

Press F1 inside Rust to open the console and enter client.connect 212.193.10.54:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp2000,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp2000Max players. 2,000 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs166652Build. This server runs game build 166652.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.
Mods and access
^zModded. Modded listing: plugins or settings modify the game.
^yCarbon. Plugins run through Carbon.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.