RUST METRICSFlight deck · live data
Data live Servers11,800 Players69,961 Populated3,675 Fresh wipes 3 h123 Scan5 min
‹ All servers62.84.33.34:28015
Offline Full Queue Fresh wipe Wipe due No query

Devblog 240-Meshki

Offline 62.84.33.34:28015 checked 15d ago

COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% 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#15,327top 71%
Last wipe15d 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 71% 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
Tue 13 Oct, 14:10 UTC15d 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

Wipe timing

What should you expect from wipe day on Devblog 240-Meshki?

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 Devblog 240-Meshki follow?

To tell the rhythm of Devblog 240-Meshki, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 15 days 7 hours ago.

Tag meanings

How should you read the tags on Devblog 240-Meshki?

These are the tags Devblog 240-Meshki publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; v2279 (Protocol): Protocol 2279: join only on the same game version; ptrak (Networking): Network layer: RakNet, the standard for the game; hab366af3 (Custom tag): A plugin or the owner set this tag; Rust does not ship it; stok (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Devblog 240-Meshki appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Devblog 240-Meshki: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all.

Player count

What position does Devblog 240-Meshki hold among Rust servers?

Ranking for Devblog 240-Meshki: #15,327 on seven-day player hours, top 71% of all ranked servers.

What player count does Devblog 240-Meshki carry?

Devblog 240-Meshki is not responding; status offline, last seen 15 days 4 hours ago.

Server details

Which location does Devblog 240-Meshki run from?

No region comes from Devblog 240-Meshki. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 62.84.33.34:28015.

What Rust version is Devblog 240-Meshki on?

Version check: Rust network protocol 2279 on Windows, run by Devblog 240-Meshki. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Devblog 240-Meshki, and is it online?

Check: connection. Devblog 240-Meshki is offline at this moment. Last contact was 15 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Devblog 240-Meshki?

No gather rate appears in the name: Devblog 240-Meshki. Check: group limit. None published. 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 under Community. Check: anti-cheat. VAC, Valve's system, is off.

Join

What do you do to join Devblog 240-Meshki?

To join: start Rust, press F1 and type client.connect 62.84.33.34:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,v2279,hab366af3,stok,gmrust

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
v2279
Protocol Protocol 2279: join only on the same game version.
ptrak
Networking Network layer: RakNet, the standard for the game.

Other

hab366af3
Custom tag A plugin or the owner set this tag; Rust does not ship it.
stok
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.