Devblog 301 LAN
Key statistics
the figures behind the quote- Players now
- 0/ 20 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #16,957 top 71%
- Rank · 7d ago
- #15,887 ▼1070 places down
- Last wipe
- 20d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 27 Sep 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEU · groups of 8+ · monthly · 64 on average | 19/200 | ▲+2+8.6% | |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No RaidingNA · groups of 8+ · monthly · 52 on average | 68/200 | ▼−1−0.9% | |
| 3 | ABYSS | PvE | US | Vanilla | Noob FriendlyNA · groups of 8+ · monthly · 40 on average | 62/200 | ▲+18+40.1% | |
| 4 | JP Infinity Connect PvEEA · groups of 8+ · monthly · 32 on average | 20/300 | ▼−1−5.9% | |
| 5 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 30 on average | 9/200 | ▼−10−53.4% | |
| 6 | MadRust PVE - Get AchievementsNA · groups of 8+ · monthly · 21 on average | 15/50 | ▼−5−26.2% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on Devblog 301 LAN?
No gather rate appears in the name of Devblog 301 LAN. Up to 8 players per group, which is the game's default. pve is the mode, no combat against other players. Community is its listing in the server browser. The server has VAC, Valve's anti-cheat, switched off.
Which map is played on Devblog 301 LAN?
The game generates the procedural map on Devblog 301 LAN.
Activity
What is the rank of Devblog 301 LAN?
For the last seven days, Devblog 301 LAN holds rank #16,957 on player hours, in the top 71% of all ranked servers.
How many players does Devblog 301 LAN have?
At present, Devblog 301 LAN is offline; the last sighting was 16 days 3 hours ago.
Wipe Schedule
On what cycle does Devblog 301 LAN wipe?
No rhythm can be told for Devblog 301 LAN yet: too few of its wipes are on record. The monthly force wipe applies to every Rust server. The next one falls on Thursday 5 November at 19:00 UTC. This world has been running for 20 days 16 hours.
Server Info
What is the location of Devblog 301 LAN?
No region from Devblog 301 LAN, and its region code is us4. Rust Analytics reports the location a server claims, not the machine's actual location. 185.16.213.70:28015 is its address.
Devblog 301 LAN runs which version of Rust?
Rust network protocol 2602 and build 132924 on Windows is what Devblog 301 LAN runs. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of Devblog 301 LAN?
No response from Devblog 301 LAN. It was last seen 16 days 3 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. The earliest Rust Analytics saw it was 27 September 2026.
Tags and Rankings
What is the meaning of the tags on Devblog 301 LAN?
The game's server browser reads gmrust (Game mode): Rust's standard survival mode; mp20 (Max players): It holds 20 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2602 (Protocol): Your game must run protocol 2602 to connect; cs132924 (Build): It runs build 132924; ptrak (Networking): RakNet, the network layer the game ships with; $rus4 (Region code): us4 is the region code; ^p (PvE): No fighting between players: the world is the threat, which Devblog 301 LAN publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
Devblog 301 LAN appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature Devblog 301 LAN: Rust community servers and Best Rust PvE servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
How to Join
What steps do I take to join Devblog 301 LAN?
The console route: start Rust, press F1, enter client.connect 185.16.213.70:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp20,ptrak,$rus4,v2602,^p,gmrust,cs132924,ts8
Game
gmrust
mp20
ts8
v2602
cs132924
ptrak
$rus4
Gameplay
^p
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.