Rust Data

rustdata.spaceservers213.35.168.82:28017.ipynb

Run all rust-data · live

‹ All servers

Online 213.35.168.82:28015 checked 11m ago

Local Test Server

Connect

srv = rust.server("213.35.168.82:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/5 # 0% full
7-day average 0 # peak 2
rank #8,150 # top 37%
last wipe 1d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.511.5221:0002:0008:0013:0020:0001:00Wiped Tue 27 Oct, 22:08 UTCWIPE

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
15k10k15k20k18 Oct20 Oct22 Oct25 Oct27 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap9.4 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 22:08 UTC1d ago NaN NaN running 2
1 Sun 18 Oct, 11:35 UTC10d ago 1 held half 9.4 days 0

# 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
213.35.168.82:28015
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 22:08 UTC
hostname
–
first seen
18 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 · 560 on average169/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average121/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average17/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 288 on average15/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average18/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average29/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does Local Test Server rank?

Over the last seven days Local Test Server sits at #8,150 on player hours, in the top 37% of ranked servers.

How full does Local Test Server run?

The sample now reads 0 players for Local Test Server, out of 5 slots. Over the last seven days it averaged 0 players and peaked at 2. Averaged by hour over 48 hours, 23:00 UTC is the busiest, at 2 players.

Server data

What is the Rust version on Local Test Server?

Rust network protocol 2635 and build 168909 on Windows is what Local Test Server runs. Steam updates your game for you, but the protocol must match to join.

Is Local Test Server up, and what does its uptime show?

Online is the state at the latest refresh for Local Test Server. 29 of 168 hours up over the last 7 full days, or 17%. Rust Data logged it first on 18 October 2026.

Where does Local Test Server sit?

No region is published by Local Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 213.35.168.82:28015 is its address.

Map and rules

Which settings and rules does Local Test Server run?

No gather rate appears in the name: Local Test Server. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. The VAC field reads off.

Which map has Local Test Server selected?

The game generates its map: procedural, on Local Test Server.

Wipe schedule

On what schedule does Local Test Server wipe?

The record for Local Test Server holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 28 hours ago.

On Local Test Server, what happens on wipe day?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began. Half the peak or more was held to the next wipe in 100% of recent wipes.

Lists and tags

Where does Local Test Server appear among Rust Data lists and filters?

The Rust Data lists that Local Test Server fits are: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

How should you read the server tags on Local Test Server?

The game's server browser reads these tags from Local Test Server: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

What is the way into Local Test Server?

The manual route: launch Rust, F1, then client.connect 213.35.168.82:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp5,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp5
Max players 5 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

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 38,590 players 11,700 servers online