Rust Data

rustdata.spaceservers31.23.183.90:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 31.23.183.90:28015 checked 43d ago

TEST

moddedcarbon

Connect

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

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #14,060 # no region published
last wipe 44d 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
15k10k15k20k20 Sep21 Sep

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
31.23.183.90:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
14 Sep 2026, 00:32 UTC
hostname
–
first seen
14 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 155 on average171/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average124/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average186/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average136/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average14/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average53/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does TEST rank?

Rank #14,060 on seven-day player hours for TEST, within the top – of all ranked servers.

What population does TEST carry?

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

Server data

What is the Rust version on TEST?

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

Is TEST up, and what does its uptime show?

Offline now for TEST, last seen 43 days 20 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 14 September 2026.

Where does TEST sit?

No region is published by TEST. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 31.23.183.90:28015 is its address.

Settings and map

Which settings and rules does TEST run?

No gather rate appears in the name: TEST. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.

Which map has TEST selected?

TEST runs a procedural map, which the game generates.

Wipe schedule

When does TEST wipe, and how often?

Too few wipes are on record for TEST to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 44 days 10 hours ago, and that is the one in play.

Tags, lists

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

These Rust Data lists include TEST: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

How should you read the server tags on TEST?

These tags are published by TEST and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Plugin framework: Carbon. 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.

How to join

What is the way into TEST?

Enter client.connect 31.23.183.90: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 mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8,^z,^y

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Team limit of 8, as shipped by default.
v2633
Protocol To join, your game must run protocol 2633.
cs163794
Build Build number: 163794.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon Plugin framework: Carbon.

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 59,961 players 11,689 servers online