Skip to the story

Live edition97,045 playing on 11,869 servers

Rust Insights

Server profile

yaga test

Online, with 1 of 2000 players on; ranked #3,097 of every public Rust server, the top 14%. It last wiped 26d ago.

Filed under moddedcarbon
Launch Rust and join
1/ 2000 players now 0% full
17-day averagepeak 1
#3,097ranktop 14%
26d agolast wipeno schedule published
–next wipeno rhythm it keeps

The crowd

Players

Who is on it, hour by hour and day by day.

AveragePeak
00.250.50.75117:0002:0011:0021:0006:0015:00

Note: hourly average and peak, UTC.

Under the hood

Server performance

Frames per second, entities and memory, asked of the server itself.

05010015020017:0002:0011:0021:0006:0015:00

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.

The standings

Rank

Its place among every ranked server, day by day; 1 is best.

RankRank in region
15k10k15k20k2 Oct7 Oct13 Oct18 Oct24 Oct29 Oct

Note: Top 14% of all ranked servers. Ranked on player hours over the last seven days.

The wipe cycle

Wipe schedule

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.

0.5 days usual gap between real wipes
100% on rhythm of its recent wipes
1,501 wipe-day peak players, last three wipes

The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe

Sat 3 OctSat 3 OctFri 2 Oct
0200400600800+0h+9h+19h+28h+38h+47h

Note: players each hour, from the hour of the wipe. The latest peaked at 1,501, 2 hours in.

The record

Wipes

Every wipe we saw, newest first.

WipedPeakCrowdLastedPlayers 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 UTC26d ago 1,501 – 0.5 days 0

Note: 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.

If you like this one

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. ShockRust | Blue | NoLimitno group limit · 150 on average161/500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average185/225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average92/700
  5. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 87 on average246/700
  6. RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average345/350

The short version

Quick answers

From the figures on this page.

Wipe days

What should you expect on wipe day at yaga test?

Recent wipes peaked at 1,501 players on average. 2 hours into the latest wipe, the crowd on the server reached its peak.

When does yaga test wipe, and how often?

There is no next wipe to predict: yaga test wipes at irregular times. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. This world dates from 26 days 1 hours ago.

Server details

How well does yaga test perform?

Average server fps over the last 48 hours was 89, with a floor of 50. The world held a peak of 17,629 entities, counting buildings, deployables and all the rest. The highest memory figure was 2,134 MB. A climbing entity count and low fps are what players experience as lag.

Which Rust version is yaga test on?

Rust network protocol 2634 and build 166652 on Linux is what yaga test runs. Joining needs your game on the same protocol, which Steam updates for you.

How reliable is yaga test, and is it up at the moment?

Right now yaga test is up and running. The uptime it reports puts the last restart at about 7 days 4 hours ago. The last 7 full days gave 167 of 168 hours up, or 99% of the time. The first record Rust Insights has of it is 2 October 2026.

Where does yaga test run from?

No region is published by yaga test. Rust Insights takes the location from what a server says about itself; no check is made of where the machine stands. You can reach it at 212.193.10.54:28015.

Tags

How should you read the tags listed for yaga test?

These tags come from yaga test and are read by the game's server browser: gmrust (Game mode): Survival as standard Rust plays; mp2000 (Max players): It holds 2,000 slots; ts8 (Group limit): 8 to a team, which is the default the game ships with; v2634 (Protocol): Your game must run the same version to join: the protocol is 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): The region code field is empty; ^z (Modded): Modded is its listing, because plugins or settings change how the game plays; ^y (Carbon): The plugin framework here is Carbon. Current players, queue length and the age of the world sit in the tags as well, shown at the top of this page.

Which Rust Insights filters and lists feature yaga test?

yaga test appears among the following Rust Insights lists: Modded Rust servers, explained. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

How many players are on yaga test right now, and how does that number move?

yaga test shows 1 players at the moment, against 2,000 slots. A weekly average of 1 players goes with a peak of 1. Look at the last 48 hours and the peak hour is 17:00 UTC, at 1 players on average.

How does yaga test compare with other Rust servers in the ranking?

On player hours for the last seven days, yaga test sits at #3,097, inside the top 14% of ranked servers.

Map and rules

What settings and rules apply on yaga test?

The name of yaga test does not state a gather rate. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. Fighting and raiding between players are allowed. The server browser lists it under Modded: plugins or settings alter the game. It runs plugins, Carbon of them. VAC is on: Valve's anti-cheat is active.

What is the map on yaga test?

yaga test runs a procedural map of size 2,000 with seed 12345, generated by the game. The same size and seed produce the same map, so from this page you can look at it on RustMaps.

Join

How do you connect to yaga test?

To connect, start Rust and enter client.connect 212.193.10.54:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.

The small print

Server tags

What each one means.

Published as mp2000,ptrak,$r?,v2634,gmrust,cs166652,ts8,^z,^y

Game

gmrust
Game mode Survival as standard Rust plays.
mp2000
Max players It holds 2,000 slots.
ts8
Group limit 8 to a team, which is the default the game ships with.
v2634
Protocol Your game must run the same version to join: the protocol is 2634.
cs166652
Build The game build is 166652.
ptrak
Networking RakNet handles the network layer, as it does by default.
$r?
Region code The region code field is empty.

Mods and access

^z
Modded Modded is its listing, because plugins or settings change how the game plays.
^y
Carbon The plugin framework here is Carbon.

Note: 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.