Rust Data

rustdata.spaceservers212.3.149.11:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 212.3.149.11:28015 checked 27d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #15,705 # top 66%
last wipe 27d 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
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

Top 66% 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
212.3.149.11:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
30 Sep 2026, 14:26 UTC
hostname
–
first seen
30 Sep 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 · 532 on average216/250
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 327 on average14/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 325 on average17/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average125/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average43/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average39/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does TEST rank?

Over the last seven days TEST sits at #15,705 on player hours, in the top 66% of ranked servers.

How full does TEST run?

TEST returns no live count at this refresh, having last been seen 27 days 14 hours ago.

About the server

What Rust version does TEST run?

Rust network protocol 2633 and build 165217 on Windows is what TEST runs. Steam updates your game for you, but the protocol must match to join.

Is TEST up, and what does its uptime show?

TEST is offline at this refresh; the last response came 27 days 14 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 30 September 2026.

Which location does TEST run from?

For TEST, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 212.3.149.11:28015.

Settings and map

What rules and settings are recorded for TEST?

The name TEST carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

Which map has TEST loaded?

A procedural map runs on TEST, generated by the game.

Wipe data

When does TEST wipe, and how often?

The record for TEST 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 27 days 14 hours ago.

Tags, lists

Which lists on Rust Data hold TEST, and which filters?

The Rust Data lists that TEST 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.

Which meanings do the tags on TEST hold?

Read by the game's server browser, the tags TEST publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

What is the way to join TEST?

In Rust, F1 opens the console: type client.connect 212.3.149.11: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 mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs165217
Build Build number: 165217.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

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 34,117 players 11,596 servers online