RUST METRICSFlight deck · live data
Data live Servers11,685 Players49,486 Populated3,263 Fresh wipes 3 h133 Scan5 min
‹ All servers77.40.62.4:28015
Offline Full Queue Fresh wipe Wipe due No query

dyrashka

Offline 77.40.62.4:28015 checked 23d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% full 7-day avg
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 average0peak –
Rank#13,887top 61%
Last wipe23d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k4 Oct5 Oct7 Oct8 Oct10 Oct11 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 4 Oct, 05:42 UTC23d ago 1 – running 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

Reset cycle

What should you expect from wipe day on dyrashka?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does dyrashka follow?

The rhythm of dyrashka's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 23 days 19 hours ago the current world was made.

Lists and filters

How should you read the tags on dyrashka?

These are the tags dyrashka publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; 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): Region code: none set. 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 dyrashka?

These Rust Metrics lists carry dyrashka: 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 dyrashka hold among Rust servers?

Ranking for dyrashka: #13,887 on seven-day player hours, top 61% of all ranked servers.

What is the population on dyrashka?

Reading for dyrashka: offline at this moment; last seen 23 days 18 hours ago.

Operator and location

Where does dyrashka sit?

No region tag on dyrashka. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 77.40.62.4:28015.

What Rust version is dyrashka on?

Rust network protocol 2634 and build 166652 on Windows is the build dyrashka runs. Matching protocol is required to join. Let Steam update your game.

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

dyrashka reports offline. The last reading came 23 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 4 October 2026.

Rules and settings

What rules does dyrashka enforce, and what are its settings?

Reading the name gives no gather rate for dyrashka. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on dyrashka?

Procedural map on dyrashka, made by the game's generator.

Join

How do you connect to dyrashka?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit Team cap of 8, which is the game default.
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 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.