Rust Data

rustdata.spaceservers193.27.19.240:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 193.27.19.240:28015 checked 43d ago

TEST

moddedoxide

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #13,258 # no region published
last wipe 43d 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 Sep22 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
193.27.19.240:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
15 Sep 2026, 13:08 UTC
hostname
–
first seen
15 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 · 149 on average154/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average120/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average186/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average72/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average11/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average23/1000

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 #13,258 on player hours, in the top – of ranked servers.

How full does TEST run?

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

About the server

What is the Rust version on TEST?

The build is Rust network protocol 2633 and build 163794 on Windows, run by TEST. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TEST, and is it up?

Offline now for TEST, last seen 43 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 15 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. You can reach it at 193.27.19.240:28015.

Map and rules

What rules and settings are recorded for TEST?

No gather rate appears in the name: TEST. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has TEST loaded?

TEST runs a procedural map, which the game generates.

Wipe schedule

On what schedule does TEST wipe?

Too few wipes are on record for TEST to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 43 days 22 hours ago, and that is the one in play.

Tags, lists

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

The Rust Data lists that TEST fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

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; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): The server runs build 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way into TEST?

In Rust, F1 opens the console: type client.connect 193.27.19.240: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,cs163794,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol To join, your game must run protocol 2633.
cs163794
Build The server runs build 163794.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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 61,573 players 11,733 servers online