Rust Server TrendsSeismic network · station log
Recording Stations11,829 Players89,289 Active4,008 Wipes · 3 h28 48 h

Station US-16957 · no signal

Devblog 301 LAN

Offline 185.16.213.70:28015 checked 30d ago

pve
Connect
Players now
0/ 20
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,957
top 71%
Last wipe
35d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station US-16957 · 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 20 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
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

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

Expected events

Wipe schedule

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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
ABYSS | PvE | US | Vanilla | Noob Friendly NA · groups of 8+ · monthly · 53 on average
36/ 200
[EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding EU · groups of 8+ · monthly · 33 on average
37/ 200
[US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding NA · groups of 8+ · monthly · 32 on average
17/ 200
【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 EA · groups of 30+ · monthly · 22 on average
25/ 200
[PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly groups of 8+ · monthly · 21 on average
12/ 150
[EU/GER] Rust Norddeutschland PVE EU · groups of 8+ · biweekly · 17 on average
11/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on Devblog 301 LAN?

A procedural map runs on Devblog 301 LAN, generated by the game.

Which settings and rules apply on Devblog 301 LAN?

You will find no gather rate in the name of Devblog 301 LAN. Groups hold up to 8 players, which is the default for the game. pve is the game mode, no player-versus-player fighting. It is a community server, and the browser lists it under Community. Anti-cheat is off: VAC, from Valve.

Population

How many players are recorded on Devblog 301 LAN right now?

No players are recorded on Devblog 301 LAN at this moment; it is offline, and the last sighting was 30 days 21 hours ago.

How does Devblog 301 LAN rank against other Rust servers?

Over the last seven days, Devblog 301 LAN recorded enough player hours to reach #16,957 worldwide, placing it in the top 71% of all ranked servers.

Server details

How reliably does Devblog 301 LAN stay online?

No contact with Devblog 301 LAN right now, and the last recorded contact was 30 days 21 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 27 September 2026.

Which region does Devblog 301 LAN run from?

No region comes from Devblog 301 LAN, though its region code is us4. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 185.16.213.70:28015.

What build of Rust does Devblog 301 LAN use?

Rust network protocol 2602 and build 132924 on Windows is what Devblog 301 LAN runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

On what timetable does Devblog 301 LAN run its wipes?

The rhythm of Devblog 301 LAN cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 35 days 9 hours.

Server tags

What do the server tags on Devblog 301 LAN mean?

The game's server browser reads the tags Devblog 301 LAN publishes: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): The server has 20 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2602 (Protocol): Game protocol 2602: to join, your game must match this version; cs132924 (Build): The game build is 132924; ptrak (Networking): The network layer is RakNet, the game's standard; $rus4 (Region code): You'll see it listed with the region code us4; ^p (PvE): There's no player combat; the world provides the threat. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does Devblog 301 LAN appear?

These Rust Server Trends lists include Devblog 301 LAN: Rust community servers without the side modes and Rust PvE servers. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

Join the server

What steps get you onto Devblog 301 LAN?

Enter client.connect 185.16.213.70:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp20,ptrak,$rus4,v2602,^p,gmrust,cs132924,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp20
Max players The server has 20 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2602
Protocol Game protocol 2602: to join, your game must match this version.
cs132924
Build The game build is 132924.
ptrak
Networking The network layer is RakNet, the game's standard.
$rus4
Region code You'll see it listed with the region code us4.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

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.