Rust Data

rustdata.spaceservers90.154.71.158:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 90.154.71.158:28015 checked 2d ago

Test

Connect

srv = rust.server("90.154.71.158:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,388 # top 70%
last wipe 2d 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
15k10k15k20k24 Oct25 Oct26 Oct27 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
90.154.71.158:28015
region
– · ger
max players
100
group limit
not published
wipe schedule
–
last wipe
24 Oct 2026, 20:38 UTC
hostname
–
first seen
24 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 · 504 on average782/825
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 345 on average48/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 340 on average119/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 314 on average393/500
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average253/300
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 259 on average188/300

Quick answers

From the figures on this page.

Population data

What position does Test take in the server rankings?

Player hours over seven days put Test at #15,388, in the top 70% of the ranked set.

How full does Test run?

Offline now for Test, with the last sample 2 days 22 hours ago. Over the last seven days it averaged 0 players.

About the server

Which Rust version is Test on?

Rust network protocol 2556 and build 104071 on Windows is what Test runs. The protocol has to match before you can join, and Steam does the updating.

Is Test up, and what does its uptime show?

Test is offline at this refresh; the last response came 2 days 22 hours ago. Uptime of 0% across the last 2 full days: 0 hours of 48. Rust Data logged it first on 24 October 2026.

In which location is Test hosted?

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

Rules, settings, map

What rules and settings are recorded for Test?

The name Test carries no gather rate. Group limits do not appear in its data. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC is not running; Valve's anti-cheat is off.

What is the map on Test?

Test runs a procedural map, which the game generates.

Wipes and dates

When does Test wipe, and how often?

A rhythm cannot be read from the wipes of Test on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 2 days 23 hours ago.

Lists and tags

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

These Rust Data lists include Test: Rust community servers, unfiltered. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Last wipe: In the last 3 days.

How should you read the server tags on Test?

The game's server browser reads these tags from Test: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; v2556 (Protocol): Protocol 2556 is required; a different game version cannot connect; cs104071 (Build): Recorded game build: 104071; ptrak (Networking): The network layer is RakNet, standard for the game; $rger (Region code): The row gives ger as its region code. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

How can I connect to Test?

Enter client.connect 90.154.71.158: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 mp100,ptrak,$rger,v2556,gmrust,cs104071

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players Slot count: 100.
v2556
Protocol Protocol 2556 is required; a different game version cannot connect.
cs104071
Build Recorded game build: 104071.
ptrak
Networking The network layer is RakNet, standard for the game.
$rger
Region code The row gives ger as its region code.

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 89,250 players 11,880 servers online