Rust Data

rustdata.spaceservers145.239.11.159:28026.ipynb

Run all rust-data · live

‹ All servers

Offline 145.239.11.159:28025 checked 27d ago

TEST 2000

Connect

srv = rust.server("145.239.11.159:28026")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #16,840 # top 70%
last wipe 28d 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
15k10k15k20k29 Sep1 Oct2 Oct4 Oct5 Oct7 Oct

Top 70% 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
145.239.11.159:28025
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
29 Sep 2026, 08:07 UTC
hostname
–
first seen
29 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 · 530 on average244/300
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 329 on average16/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 327 on average32/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average120/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 279 on average47/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average53/100

Quick answers

From the figures on this page.

Population data

What position does TEST 2000 take in the server rankings?

Over the last seven days TEST 2000 sits at #16,840 on player hours, in the top 70% of ranked servers.

How full does TEST 2000 run?

Offline now for TEST 2000, with the last sample 27 days 21 hours ago.

Server data

What is the Rust version on TEST 2000?

Rust network protocol 2633 and build 165217 on Windows is what TEST 2000 runs. Joining needs the same protocol on your game; Steam handles the update.

Is TEST 2000 up, and what does its uptime show?

TEST 2000 is offline at this refresh; the last response came 27 days 21 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 29 September 2026.

Where does TEST 2000 sit?

There is no region published for TEST 2000. Rust Data does not look up where the machine stands; it shows where a server says it is. 145.239.11.159:28025 is its address.

Settings and map

What rules and settings are recorded for TEST 2000?

You will not find a gather rate in the string TEST 2000. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has TEST 2000 loaded?

TEST 2000 runs a procedural map, which the game generates.

Wipe schedule

On what schedule does TEST 2000 wipe?

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

Lists and tags

Where does TEST 2000 appear among Rust Data lists and filters?

These Rust Data lists include TEST 2000: 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.

How should you read the server tags on TEST 2000?

Read by the game's server browser, the tags TEST 2000 publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs165217 (Build): The server runs build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

How can I connect to TEST 2000?

In Rust, F1 opens the console: type client.connect 145.239.11.159:28025. 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 Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2633
Protocol To join, your game must run protocol 2633.
cs165217
Build The server runs build 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 39,046 players 11,640 servers online