Devblog 301 LAN
Offline 94.139.255.199:28015 checked 33d 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- 36/200
- 6/200
- 28/200
- 31/200
- 17/150
- 0/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does Devblog 301 LAN follow?
The rhythm of Devblog 301 LAN's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 35 days 19 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): Slots: 20; ts8 (Group limit): Team cap of 8, which is the game default; v2602 (Protocol): Match the game version: protocol 2602 is required; cs132924 (Build): The server runs game build 132924; ptrak (Networking): Network layer: RakNet, the standard for the game; $reu1 (Region code): eu1 is the region code on record; ^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?
Rust Metrics lists featuring Devblog 301 LAN: Rust community servers: live readings and Rust PvE servers. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Player count
What position does Devblog 301 LAN hold among Rust servers?
Player hours over seven days put Devblog 301 LAN at #16,363, in the top 71% of all ranked servers.
What player count does Devblog 301 LAN carry?
Devblog 301 LAN is not responding; status offline, last seen 33 days 14 hours ago.
Server details
Where does Devblog 301 LAN sit?
No region comes from Devblog 301 LAN, and its region code is eu1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 94.139.255.199: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. Matching protocol is required to join. Let Steam update your game.
How reliable is Devblog 301 LAN, and is it online now?
Check: connection. Devblog 301 LAN is offline at this moment. Last contact was 33 days 14 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 24 September 2026.
Rules and settings
What settings and rules apply on Devblog 301 LAN?
No gather rate appears in the name: Devblog 301 LAN. 8 players per group, the default value. The mode is pve. Note the following: other players are not fought. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.
Which map is live on Devblog 301 LAN?
Check: map. Procedural, generated by the game, on Devblog 301 LAN.
Join
What do you do to join Devblog 301 LAN?
Check: join. Open Rust, press F1, then enter client.connect 94.139.255.199:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.