Rust Data

rustdata.spaceservers201.10.76.60:28015.ipynb

Run all rust-data · live

‹ All servers

Offline 201.10.76.60:28015 checked 21d ago

Devblog 65 Legacy Server

Connect

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

Right now

srv.summary()
players now 1/30 # 3% full
7-day average 0 # peak –
rank #13,146 # top 59%
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
15k10k15k20k5 Oct7 Oct8 Oct10 Oct11 Oct13 Oct

Top 59% 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.60:28015
region
–
max players
30
group limit
not published
wipe schedule
–
last wipe
6 Oct 2026, 11:16 UTC
hostname
–
first seen
5 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 · 511 on average577/625
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 340 on average32/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 337 on average73/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 316 on average290/325
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average114/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 261 on average120/150

Quick answers

From the figures on this page.

Population data

What position does Devblog 65 Legacy Server take in the server rankings?

Over the last seven days Devblog 65 Legacy Server sits at #13,146 on player hours, in the top 59% of ranked servers.

How full does Devblog 65 Legacy Server run?

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

Server data

What is the Rust version on Devblog 65 Legacy Server?

Rust network protocol 2013 on Windows is what Devblog 65 Legacy Server runs. Steam updates your game for you, but the protocol must match to join.

How reliable is Devblog 65 Legacy Server, and is it up?

Offline now for Devblog 65 Legacy Server, last seen 21 days 10 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 5 October 2026.

Where does Devblog 65 Legacy Server sit?

For Devblog 65 Legacy Server, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 201.10.76.60:28015 is its address.

Map and rules

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

You will not find a gather rate in the string Devblog 65 Legacy Server. The field for group size is empty. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. The VAC field reads off.

Which map has Devblog 65 Legacy Server selected?

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

Wipe schedule

On what schedule does Devblog 65 Legacy Server wipe?

The record for Devblog 65 Legacy Server holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 21 days 11 hours ago.

Tags and filters

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?

The game's server browser reads these tags from Devblog 65 Legacy Server: mp30 (Max players): Slot count: 30; v2013 (Protocol): To join, your game must run protocol 2013; h241a841b (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin; stok (Custom tag): Not one of Rust's standard tags: set by the owner or a plugin. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Join steps

How can I connect to Devblog 65 Legacy Server?

Enter client.connect 201.10.76.60:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp30,v2013,h241a841b,stok

Game

mp30
Max players Slot count: 30.
v2013
Protocol To join, your game must run protocol 2013.

Other

h241a841b
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.
stok
Custom tag Not one of Rust's standard tags: set by the owner or a plugin.

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 63,914 players 11,774 servers online