Rust Data

rustdata.spaceservers93.115.23.170:28506.ipynb

Run all rust-data · live

‹ All servers

Online 93.115.23.170:28505 checked 11m ago

TestServer

moddedcarbon

Connect

srv = rust.server("93.115.23.170:28506")
print(srv.connect_command)

Right now

srv.summary()
players now 1/50 # 2% full
7-day average 1 # peak 1
rank #4,529 # top 20%
last wipe 4d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75119:0021:0010:0012:0015:0017:00

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
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 20% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 25 OctWed 14 OctFri 9 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 25 Oct, 10:22 UTC4d ago 1 NaN running 1
1 Wed 14 Oct, 19:11 UTC14d ago 1 held half 10.6 days 1
2 Fri 9 Oct, 22:11 UTC19d ago 1 held half 4.9 days 0
3 Thu 8 Oct, 20:05 UTC20d ago 1 NaN 1.1 days 1
4 Thu 8 Oct, 10:38 UTC21d ago 1 NaN 0.4 days 0
5 Wed 7 Oct, 19:48 UTC21d ago 1 NaN 0.6 days 0
6 Fri 2 Oct, 13:09 UTC27d ago 1 halved by day 1 5.3 days 1
7 Wed 30 Sep, 18:09 UTC29d ago 1 NaN 1.8 days 1
8 Tue 29 Sep, 18:24 UTC29d ago 1 NaN 1 days 0
9 Fri 25 Sep, 12:29 UTC34d ago 1 held half 4.2 days 1

# 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
93.115.23.170:28505
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
25 Oct 2026, 10:22 UTC
hostname
–
first seen
13 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 · 151 on average144/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average127/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average201/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average79/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 89 on average229/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average351/350

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does TestServer rank?

Over the last seven days TestServer sits at #4,529 on player hours, in the top 20% of ranked servers.

How many players does TestServer hold at once?

The sample now reads 1 players for TestServer, out of 50 slots. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 19:00 UTC, averaging 1 players.

Server facts

What Rust version does TestServer run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by TestServer. Steam updates your game for you, but the protocol must match to join.

How reliable is TestServer, and is it online now?

Online is the state at the latest refresh for TestServer. Over the last 7 full days the hours up number 61 of 168, 36%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does TestServer sit?

For TestServer, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 93.115.23.170:28505.

Settings and map

Which rules apply on TestServer, and what settings?

No gather rate appears in the name: TestServer. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.

What is the map on TestServer?

TestServer runs a procedural map, which the game generates.

Wipe data

On what schedule does TestServer wipe?

Irregular wipe times on TestServer leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 4 days 7 hours ago, and that is the one in play.

What is wipe day on TestServer like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 100% of recent wipes.

Tags and filters

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

On Rust Data, TestServer appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on TestServer hold?

These tags are published by TestServer and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Runs on Carbon for plugins. 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 TestServer?

In Rust, F1 opens the console: type client.connect 93.115.23.170:28505. 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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players Slot count: 50.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Modded listing: the game is changed by plugins or settings.
^y
Carbon Runs on Carbon for plugins.

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 103,131 players 11,899 servers online