Rust Server TrendsSeismic network · station log
Recording Stations11,694 Players35,972 Active2,914 Wipes · 3 h94 48 h

Station XX-15987 · no signal

Rust Devblog 240

Offline 13.143.172.30:28015 checked 22d ago

modded
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,987
top 71%
Last wipe
22d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15987 · 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 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 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
0players, last three wipes

The first 48 hours of its last wipes

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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 6 Oct, 11:14 UTC22d ago M0.0steady 0 – 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
ShockRust | Blue | NoLimit no group limit · 154 on average
15/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
123/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
31/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
14/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
5/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
1/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Rust Devblog 240?

Rust Devblog 240 uses a procedural map, which the game generates.

Which settings and rules apply on Rust Devblog 240?

No gather rate appears in the name of Rust Devblog 240. The group limit is not published. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The server has VAC off, Valve's anti-cheat.

Live population

What is the current population on Rust Devblog 240?

No players are recorded on Rust Devblog 240 at this moment; it is offline, and the last sighting was 22 days 14 hours ago.

How does Rust Devblog 240 rank against other Rust servers?

Over the last seven days, Rust Devblog 240 recorded enough player hours to reach #15,987 worldwide, placing it in the top 71% of all ranked servers.

Operator and location

How reliably does Rust Devblog 240 stay online?

As recorded now, Rust Devblog 240 is not reachable, the last contact having been 22 days 14 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 6 October 2026 it was recorded for the first time by Rust Server Trends.

Where in the world is Rust Devblog 240 hosted?

Nothing about a region comes from Rust Devblog 240. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 13.143.172.30:28015.

What build of Rust does Rust Devblog 240 use?

Rust network protocol 2283 on Windows is what Rust Devblog 240 runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on Rust Devblog 240?

The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.

How often does Rust Devblog 240 wipe, and on which days?

The rhythm of Rust Devblog 240 cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 22 days 15 hours.

Lists and tags

What do the server tags on Rust Devblog 240 mean?

These are the tags Rust Devblog 240 publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp50 (Max players): 50 slots are available; v2283 (Protocol): Your game needs to be on protocol 2283 to join; ptrak (Networking): The network layer is RakNet, the game's standard; oxide (Oxide): Oxide (uMod) is the plugin framework running here; modded (Modded): Plugins or settings alter the game, so it's listed under Modded; hd53cb39f (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin; stok (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. 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 Rust Devblog 240 appear?

These Rust Server Trends lists include Rust Devblog 240: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded.

Join the server

What steps get you onto Rust Devblog 240?

To join, enter client.connect 13.143.172.30: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,v2283,hd53cb39f,stok,gmrust,oxide,modded

Game

gmrust
Game mode You'll find standard Rust survival here.
mp50
Max players 50 slots are available.
v2283
Protocol Your game needs to be on protocol 2283 to join.
ptrak
Networking The network layer is RakNet, the game's standard.

Mods and access

oxide
Oxide Oxide (uMod) is the plugin framework running here.
modded
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

hd53cb39f
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.
stok
Custom tag A custom tag, not standard Rust: set by the owner or a plugin.

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.