RUST METRICSFlight deck · live data
Data live Servers11,842 Players74,292 Populated3,699 Fresh wipes 3 h224 Scan5 min
‹ All servers212.193.10.54:28015
Online Full Queue Fresh wipe Wipe due No query

yaga test

Online 212.193.10.54:28015 checked 8m ago

moddedcarbon
COM 1 · connect

Server instruments

last reading Thu 12:00 UTC
0 500 1000 1500 2000 PAX 1 /2,000

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 50 SERVER FPS

Server fps

48 h low 50 · below 20 is lag, below 10 is bad
0 5 10 15 20 ENT 17,627 ×1000

Entities

48 h range 15,331–17,728 · memory 1,838 MB
1239 ET SINCE RESTART 7D 01H

Uptime

7 days 1 hours since its last restart, at the last reading
7-day average1peak 1
Rank#3,095top 14%
Last wipe25d agono schedule published
Next wipe–no rhythm it keeps
Memory1,838MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75114:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020014:0023:0008:0017:0003:0012: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.

REC 3

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.

PLAN

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.

usual gap0.5 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1,501players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 15:19 UTC25d 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

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on yaga test when wipe day comes?

An average of 1,501 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 2 hours.

When does yaga test wipe?

No next wipe can be predicted for yaga test, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 25 days 22 hours ago.

Tags

Which tags does yaga test carry, and what do they mean?

Tags published by yaga test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp2000 (Max players): Slots: 2,000; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show yaga test?

Rust Metrics lists featuring yaga test: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

Where does yaga test sit in the rankings?

Ranking for yaga test: #3,095 on seven-day player hours, top 14% of all ranked servers.

What player count does yaga test carry?

1 of 2,000 slots are filled on yaga test right now. Check: players over seven days. Average 1, peak 1. Average at the busiest hour was 1 players, at 14:00 UTC over the last 48 hours.

Server details

Where does yaga test sit?

No region tag on yaga test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 212.193.10.54:28015.

What Rust version is yaga test on?

Reading: yaga test, Rust network protocol 2634 and build 166652, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is performance on yaga test within range?

Check: fps. Average 88 server fps over the last 48 hours, low of 50. Within range. Check: entities. The peak was 17,728, counting buildings, deployables and the rest of the world. Memory peak: 2,134 MB. Expect lag when fps falls and entities climb.

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

Reading: online. yaga test answers right now. Reading: uptime. About 7 days 1 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 2 October 2026.

Settings and map

How is yaga test configured, and what rules are in force?

No gather rate appears in the name: yaga test. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

What map is yaga test on?

Check: map. Procedural, size 2,000, seed 12345, generated by the game on yaga test. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

Connection

What do you do to join yaga test?

Check: join. Open Rust, press F1, then enter client.connect 212.193.10.54:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

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 it.
mp2000
Max players Slots: 2,000.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

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.