Rust Server TrendsSeismic network · station log
Recording Stations11,681 Players55,814 Active3,378 Wipes · 3 h100 48 h

Station XX-6399 · no signal

server_yarika

Offline 31.162.134.110:28015 checked 4d ago

Connect
Players now
1/ 50
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
2
peak 3
Rank
#6,399
top 29%
Last wipe
16d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-6399 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

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

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 540 on average
536/ 575
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
358/ 400
Rustoria.co - EU Main EU · groups of 16+ · weekly · 314 on average
36/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 313 on average
43/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 273 on average
159/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average
78/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on server_yarika?

server_yarika uses a procedural map, which the game generates.

Which settings and rules apply on server_yarika?

No gather rate appears in the name of server_yarika. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched off.

Player counts

What is the current population on server_yarika?

A reading taken now finds server_yarika offline; the most recent activity was 4 days 16 hours ago. Averaged across the last seven days the population was 2 players, reaching a peak of 3.

How does server_yarika rank against other Rust servers?

Over the last seven days, server_yarika recorded enough player hours to reach #6,399 worldwide, placing it in the top 29% of all ranked servers.

Server facts

How reliably does server_yarika stay online?

server_yarika is down at the moment; the last recorded contact was 4 days 16 hours ago. It was up 5% of the time across the last 6 full days: 7 of 144 hours. 21 October 2026 is when Rust Server Trends first recorded it.

Where in the world is server_yarika hosted?

A region is not published by server_yarika. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 31.162.134.110:28015.

Which Rust version is server_yarika running?

On Windows, server_yarika runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

How often does server_yarika wipe, and on which days?

Too few wipes of server_yarika are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 16 days 17 hours.

Lists and tags

What do the server tags on server_yarika mean?

The game's server browser reads the tags server_yarika publishes: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does server_yarika appear?

You will find server_yarika on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

How do you connect to server_yarika?

To join, enter client.connect 31.162.134.110:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players Slots: 50.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.