Rust Server TrendsSeismic network · station log
Recording Stations11,700 Players41,781 Active3,029 Wipes · 3 h99 48 h

Station XX-15327 · no signal

Devblog 240-Meshki

Offline 62.84.33.34:28015 checked 15d ago

Connect
Players now
0/ 10
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,327
top 71%
Last wipe
15d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15327 · 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
0of 10 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

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

Expected events

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 peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 13 Oct, 14:10 UTC15d ago M0.0rising 1 – running 0

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 · 565 on average
198/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average
123/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average
24/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 289 on average
11/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average
23/ 100
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 251 on average
29/ 225
Readings, in words

Quick answers

from the figures on this page

Server rules

Which settings and rules apply on Devblog 240-Meshki?

The name of Devblog 240-Meshki gives no gather rate. It gives no group limit in its listing. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched off.

Population

How many players are recorded on Devblog 240-Meshki right now?

A reading taken now finds Devblog 240-Meshki offline; the most recent activity was 15 days 8 hours ago.

How does Devblog 240-Meshki rank against other Rust servers?

On player hours for the past week, Devblog 240-Meshki sits at #15,327, which puts it inside the top 71% of every ranked server.

Server details

How reliably does Devblog 240-Meshki stay online?

As recorded now, Devblog 240-Meshki is not reachable, the last contact having been 15 days 8 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 13 October 2026 is when Rust Server Trends first recorded it.

Where in the world is Devblog 240-Meshki hosted?

Nothing about a region comes from Devblog 240-Meshki. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 62.84.33.34:28015.

What build of Rust does Devblog 240-Meshki use?

Rust network protocol 2279 on Windows is what Devblog 240-Meshki runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe day

What does wipe day look like on Devblog 240-Meshki?

The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked.

On what timetable does Devblog 240-Meshki run its wipes?

The rhythm of Devblog 240-Meshki cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 15 days 11 hours is how long the current world has been running.

Lists and tags

What do the server tags on Devblog 240-Meshki mean?

These are the tags Devblog 240-Meshki publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): Slots: 10; v2279 (Protocol): Game protocol 2279: to join, your game must match this version; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; hab366af3 (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust; stok (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Devblog 240-Meshki appear?

These Rust Server Trends lists include Devblog 240-Meshki: 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.

How to join

How do you connect to Devblog 240-Meshki?

To join, enter client.connect 62.84.33.34: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 mp10,ptrak,v2279,hab366af3,stok,gmrust

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players Slots: 10.
v2279
Protocol Game protocol 2279: to join, your game must match this version.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.

Other

hab366af3
Custom tag The owner or a plugin applied this tag, which isn't part of standard Rust.
stok
Custom tag The owner or a plugin applied this tag, which isn't part of standard Rust.

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.