Devblog 65 Legacy Server
Offline 201.10.76.63:28015 checked 21d 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- 231/250
- 14/250
- 22/250
- 114/200
- 46/200
- 42/100
Quick answers
from the figures on this pageReset cycle
How often does Devblog 65 Legacy Server wipe, and when?
To tell the rhythm of Devblog 65 Legacy Server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 21 days 16 hours ago.
Tags
Which tags does Devblog 65 Legacy Server carry, and what do they mean?
These are the tags Devblog 65 Legacy Server publishes, and the server browser reads them: mp30 (Max players): The server holds 30 slots; v2013 (Protocol): Protocol 2013: join only on the same game version; h241a841b (Custom tag): A plugin or the owner set this tag; Rust does not ship it; stok (Custom tag): A plugin or the owner set this tag; Rust does not ship it. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Devblog 65 Legacy Server appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Devblog 65 Legacy Server: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all.
Occupancy
Where does Devblog 65 Legacy Server sit in the rankings?
Ranking for Devblog 65 Legacy Server: #15,987 on seven-day player hours, top 71% of all ranked servers.
How full does Devblog 65 Legacy Server get?
Status for Devblog 65 Legacy Server: offline. Last seen 21 days 14 hours ago.
Server details
Which location does Devblog 65 Legacy Server run from?
Reading: location. Devblog 65 Legacy Server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 201.10.76.63:28015.
What Rust version is Devblog 65 Legacy Server on?
Version check: Rust network protocol 2013 on Windows, run by Devblog 65 Legacy Server. Matching protocol is required to join. Let Steam update your game.
Is Devblog 65 Legacy Server up, and how often does it stay up?
Devblog 65 Legacy Server reports offline. The last reading came 21 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 6 October 2026.
Map and rules
What settings and rules apply on Devblog 65 Legacy Server?
Reading the name gives no gather rate for Devblog 65 Legacy Server. Check: group limit. None published. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is off. That is Valve's anti-cheat.
Which map is live on Devblog 65 Legacy Server?
The game generates a procedural map for Devblog 65 Legacy Server.
Connection
How can you get onto Devblog 65 Legacy Server?
Press F1 in Rust and enter client.connect 201.10.76.63:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.