Rust Data

rustdata.spaceservers201.10.76.63:28015.ipynb

Run all rust-data · live

‹ All servers

Offline 201.10.76.63:28015 checked 21d ago

Devblog 65 Legacy Server

Connect

srv = rust.server("201.10.76.63:28015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/30 # 0% full
7-day average 0 # peak –
rank #15,987 # top 71%
last wipe 21d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

srv.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

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
201.10.76.63:28015
region
–
max players
30
group limit
not published
wipe schedule
–
last wipe
6 Oct 2026, 11:16 UTC
hostname
–
first seen
6 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 530 on average257/300
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 329 on average15/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 327 on average30/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average121/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 279 on average44/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average48/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Devblog 65 Legacy Server rank?

Player hours over seven days put Devblog 65 Legacy Server at #15,987, in the top 71% of the ranked set.

How full does Devblog 65 Legacy Server run?

The current row shows Devblog 65 Legacy Server offline; the last response was 21 days 14 hours ago.

Server facts

Which Rust version is Devblog 65 Legacy Server on?

The build is Rust network protocol 2013 on Windows, run by Devblog 65 Legacy Server. The protocol has to match before you can join, and Steam does the updating.

Is Devblog 65 Legacy Server up, and what does its uptime show?

Devblog 65 Legacy Server is offline at this refresh; the last response came 21 days 14 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 6 October 2026.

In which location is Devblog 65 Legacy Server hosted?

There is no region published for Devblog 65 Legacy Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 201.10.76.63:28015 is its address.

Rules, settings, map

What rules and settings are recorded for Devblog 65 Legacy Server?

The name Devblog 65 Legacy Server carries no gather rate. No group limit is published. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Community is its browser category. The VAC field reads off.

What is the map on Devblog 65 Legacy Server?

Devblog 65 Legacy Server runs a procedural map, which the game generates.

Wipe data

On what schedule does Devblog 65 Legacy Server wipe?

A rhythm cannot be read from the wipes of Devblog 65 Legacy Server on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 21 days 15 hours ago.

Tags, lists

Where does Devblog 65 Legacy Server appear among Rust Data lists and filters?

On Rust Data, Devblog 65 Legacy Server appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all.

How should you read the server tags on Devblog 65 Legacy Server?

These tags are published by Devblog 65 Legacy Server and read by the game's server browser: mp30 (Max players): The server lists 30 slots; v2013 (Protocol): The server speaks protocol 2013, so match your game version; h241a841b (Custom tag): This tag comes from the owner or a plugin, not from Rust itself; stok (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to Devblog 65 Legacy Server?

In Rust, F1 opens the console: type client.connect 201.10.76.63:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp30,v2013,h241a841b,stok

Game

mp30
Max players The server lists 30 slots.
v2013
Protocol The server speaks protocol 2013, so match your game version.

Other

h241a841b
Custom tag This tag comes from the owner or a plugin, not from Rust itself.
stok
Custom tag This tag comes from the owner or a plugin, not from Rust itself.

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.

Rust Data 39,744 players 11,644 servers online