RUST METRICSFlight deck · live data
Data live Servers11,768 Players60,085 Populated3,517 Fresh wipes 3 h135 Scan5 min
‹ All servers31.162.134.110:28015
Offline Full Queue Fresh wipe Wipe due No query

server_yarika

Offline 31.162.134.110:28015 checked 5d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average1peak 3
Rank#7,220top 33%
Last wipe17d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

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

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 schedule

How often does server_yarika wipe, and when?

Its rhythm cannot be told from the wipes of server_yarika on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 17 days 5 hours ago.

Tags

Which tags does server_yarika carry, and what do they mean?

These are the tags server_yarika publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show server_yarika?

Rust Metrics lists featuring server_yarika: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does server_yarika hold among Rust servers?

Player hours over seven days put server_yarika at #7,220, in the top 33% of all ranked servers.

What player count does server_yarika carry?

Reading for server_yarika: offline at this moment; last seen 5 days 4 hours ago. Check: players over seven days. Average 1, peak 3.

Operator and location

Where does server_yarika sit?

No region tag on server_yarika. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 31.162.134.110:28015.

What Rust version is server_yarika on?

Rust network protocol 2635 and build 168909 on Windows is the build server_yarika runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on server_yarika, and is it online?

server_yarika reports offline. The last reading came 5 days 4 hours ago. Uptime for the last 6 full days: 7 of 144 hours, or 5%. Reading: first seen 21 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on server_yarika?

No gather rate appears in the name: server_yarika. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on server_yarika?

The game generates a procedural map for server_yarika.

Connection

How do you connect to server_yarika?

Press F1 in Rust and enter client.connect 31.162.134.110:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.