Skip to the page
Network live 11,899 servers online 104,128 players aboard 421 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

yaga test

Online 212.193.10.54:28015 checked 10m ago

moddedcarbon
Tracking number · connect
Wipe progress · wiped 26d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
1/ 2000 players now 0% full
17-day averagepeak 1
#3,099ranktop 14%
26d agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeak
00.250.50.75119:0004:0013:0023:0008:0017:00

Hourly average and peak, UTC.

Server performance

05010015020019:0004:0013:0023:0008:0017:00

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 best
RankRank in region
15k10k15k20k2 Oct7 Oct13 Oct18 Oct24 Oct29 Oct

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

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 daysusual gapbetween real wipes
100%on rhythmof its recent wipes
1,501wipe-day peakplayers, last three wipes

The first 48 hours of its last wipes

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

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

Wipes

every wipe as a delivery, newest first
  1. Sat 3 Oct, 15:19 UTC 16:19 UK · 26d ago
    Wipe delivered
    Peak
    1,501
    Crowd
    –
    Lasted
    running
    Players before
    1
  2. Sat 3 Oct, 03:55 UTC 04:55 UK · 26d ago
    Wipe delivered
    Peak
    1,501
    Crowd
    –
    Lasted
    0.5 days
    Players before
    0
  3. Fri 2 Oct, 16:45 UTC 17:45 UK · 27d ago
    Wipe delivered
    Peak
    1,501
    Crowd
    –
    Lasted
    0.5 days
    Players before
    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 parcels

Similar servers

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

  1. ShockRust | Blue | NoLimitno group limit · 151 on average 120 / 500
  2. МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average 122 / 100
  3. RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average 199 / 225
  4. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average 80 / 700
  5. 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 89 on average 223 / 700
  6. RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average 348 / 350
Help desk

Quick answers

From the figures on this page.

Player count

Where does yaga test place among Rust servers?

Over the past seven days, yaga test has climbed to #3,099 for player hours, putting it in the top 14% of all ranked servers.

What is the current population on yaga test?

Checking now: 1 players on 2,000 slots at yaga test. Averaged over the past week: 1 players, peaking at 1. Over the last 48 hours, the peak hour came at 19:00 UTC with an average of 1 players.

Server rules

Which map is active on yaga test?

Generated by the game with seed 12345, the procedural map on yaga test is size 2,000. You can see the map on RustMaps from this page, since one size and seed give one map.

What settings and rules should you know for yaga test?

No gather rate appears in the name of yaga test. The game's default applies: 8 players to a group at most. You get survival here, gather, build and raid, as the standard game goes. You can raid and fight other players. Plugins or settings alter the game on this one, which sits under Modded in the server browser. The plugins run on Carbon. VAC, the anti-cheat from Valve, is active.

Operator and location

What is the location of yaga test?

No region is published by yaga test. Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. You will find it at 212.193.10.54:28015.

Does yaga test perform well?

The 48-hour average for server fps stands at 88, never dipping below 44. The world held as many as 17,756 entities: buildings, deployables and the rest. The highest memory reading was 2,134 MB. Lag, to players, means low fps alongside an entity count on the rise.

What is the uptime of yaga test, and is it online?

You can find yaga test online at present. Its reported uptime suggests a restart roughly 7 days 6 hours ago. 99% is the uptime for the last 7 full days, up for 167 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 2 October 2026.

On what Rust version does yaga test operate?

On Linux, yaga test runs Rust network protocol 2634 and build 166652. Steam keeps your game updated; it has to be on the same protocol to join.

Map resets

How does yaga test handle its wipe days?

At their busiest, its recent wipes drew an average of 1,501 players. On the latest wipe, 2 hours passed before the crowd peaked.

When does yaga test wipe? What schedule does it follow?

No next wipe can be predicted for yaga test, which wipes at irregular times. Next force wipe: Thursday 5 November at 19:00 UTC, when all Rust servers wipe together, once a month. 26 days 3 hours have passed since this world was made.

Server tags

Where does yaga test appear across the Rust Wipe Tracker lists and filters?

These Rust Wipe Tracker lists take yaga test: Modded Rust servers. On the server list, apply Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more and it appears.

What is the meaning of the server tags on yaga test?

gmrust (Game mode): Standard Rust survival is the game mode here; mp2000 (Max players): The server has 2,000 slots; ts8 (Group limit): The game default caps teams at 8; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): The region code is unset; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): It uses Carbon for plugins are the tags yaga test publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

Getting started

What steps do you take to join yaga test?

Enter client.connect 212.193.10.54:28015 in the console, opened with F1 once Rust is running. Joining from this page with Launch Rust also works: it opens Rust through Steam and connects you.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game mode here.
mp2000
Max players The server has 2,000 slots.
ts8
Group limit The game default caps teams at 8.
v2634
Protocol Join only if your game runs protocol 2634.
cs166652
Build The game build is 166652.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code The region code is unset.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon It 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.