Devblog 301 LAN
Offline 185.16.213.70:28015 checked 31d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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- 67/200
- 5/200
- 33/200
- 19/200
- 23/150
- 1/100
Quick answers
from the figures on this pageReset cycle
How often does Devblog 301 LAN wipe, and when?
To tell the rhythm of Devblog 301 LAN, 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 35 days 18 hours ago.
Tags
How should you read the tags on Devblog 301 LAN?
Tags published by Devblog 301 LAN, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): 20 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2602 (Protocol): Your game must run protocol 2602 to get in; cs132924 (Build): Game build reading: 132924; ptrak (Networking): This is RakNet, Rust's usual network layer; $rus4 (Region code): The code for this server's region is us4; ^p (PvE): No fighting between players: the world itself is the hazard. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Devblog 301 LAN?
These Rust Metrics lists carry Devblog 301 LAN: Rust community servers: live readings and 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.
Population
Where does Devblog 301 LAN sit in the rankings?
Player hours over seven days put Devblog 301 LAN at #16,957, in the top 71% of all ranked servers.
What is the population on Devblog 301 LAN?
Devblog 301 LAN is not responding; status offline, last seen 31 days 5 hours ago.
Server details
Where does Devblog 301 LAN sit?
No region tag on Devblog 301 LAN, whose region code is us4. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 185.16.213.70:28015.
What Rust version is Devblog 301 LAN on?
Rust network protocol 2602 and build 132924 on Windows is the build Devblog 301 LAN runs. To get in, your game needs the same protocol; Steam applies the update.
How reliable is Devblog 301 LAN, and is it online now?
Check: connection. Devblog 301 LAN is offline at this moment. Last contact was 31 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 27 September 2026.
Settings and map
How is Devblog 301 LAN configured, and what rules are in force?
Reading the name gives no gather rate for Devblog 301 LAN. 8 players per group, the default value. The mode is pve. Note the following: no combat against other players. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.
Which map is live on Devblog 301 LAN?
The game generates a procedural map for Devblog 301 LAN.
Join
How can you get onto Devblog 301 LAN?
Press F1 in Rust and enter client.connect 185.16.213.70:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.