Element card · group PvE · atomic number 16,957, its rank
Devblog 301 LAN
Offline 185.16.213.70:28015 checked 31d ago
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 best
Top 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 wipesQuick answers
from the figures on this pageMap and rules
What map is in play on Devblog 301 LAN?
The map on Devblog 301 LAN is procedural, made by the game.
What settings and rules apply on Devblog 301 LAN?
The name of Devblog 301 LAN carries no gather rate. With no change from the default, groups can hold up to 8 players. pve is the game mode, other players cannot be fought. The server browser lists it under Community. Anti-cheat is off: Valve's VAC.
About the server
Which location is Devblog 301 LAN based in?
No region comes from Devblog 301 LAN; it does give us4 as its region code. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. You will find it at 185.16.213.70:28015.
On what Rust version does Devblog 301 LAN operate?
On Windows, Devblog 301 LAN is running Rust network protocol 2602 and build 132924. Joining requires the same protocol on your game; Steam takes care of updating it.
How dependable is Devblog 301 LAN for staying online?
Currently offline, Devblog 301 LAN was last seen 31 days 4 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. The first sighting by Rust Data Lab was on 27 September 2026.
Wipe days
When does Devblog 301 LAN wipe, and how often?
Devblog 301 LAN's wipe history on record is too thin yet to tell its rhythm. A monthly force wipe happens on every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. Counting back, the current world began 35 days 17 hours ago.
Tags, lists
Which meanings sit behind the tags on Devblog 301 LAN?
These are the tags Devblog 301 LAN makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp20 (Max players): Player slots: 20; ts8 (Group limit): 8 per team, the default the game ships with; v2602 (Protocol): To join, your game must match protocol 2602; cs132924 (Build): Build number: 132924; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $rus4 (Region code): Region code: us4; ^p (PvE): The threat comes from the world, not from other players. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.
Which Rust Data Lab filters and lists does Devblog 301 LAN appear in?
You will find Devblog 301 LAN on the following Rust Data Lab lists: Rust community servers, measured and Best Rust PvE servers, measured live. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Population
What position does Devblog 301 LAN hold among Rust servers?
Devblog 301 LAN sits at #16,957 for seven-day player hours, placing it in the top 71% of ranked servers.
What does the current player count on Devblog 301 LAN tell you?
Devblog 301 LAN is offline at the moment; the last sighting was 31 days 4 hours ago.
How to join
What steps get you onto Devblog 301 LAN?
In Rust, press F1 and enter client.connect 185.16.213.70:28015. Or click Launch Rust here to open Rust via Steam and connect automatically.