Rust Data

rustdata.spaceservers141.95.13.69:26112.ipynb

Run all rust-data · live

‹ All servers

Online 141.95.13.69:26111 checked 9m ago

TESTSERVER

moddedcarbon

Connect

srv = rust.server("141.95.13.69:26112")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 1
rank #11,780 # top 53%
last wipe 20d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75105:0014:0023:0008:0017:0003:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020005:0014:0023:0008:0017:0003:00

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, measured since 17 Sep. 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 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap7 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 8 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 8 Oct, 18:07 UTC20d ago 0 NaN running 0
1 Thu 1 Oct, 18:07 UTC FW27d ago 0 NaN 7 days 0

# 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

4500 · seed 246426222
Map of TESTSERVER
map
Procedural Map
size
4500
seed
246426222
Open on RustMaps

Server

srv.info()
address
141.95.13.69:26111
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
8 Oct 2026, 18:07 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 · 152 on average38/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average62/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average14/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average2/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average3/1000

Quick answers

From the figures on this page.

Population

How does TESTSERVER compare in the rankings?

Player hours over seven days put TESTSERVER at #11,780, in the top 53% of the ranked set.

How many players does TESTSERVER hold at once?

Current row: 0 players on TESTSERVER, against 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 05:00 UTC is the busiest, at 0 players.

Server data

How smoothly does TESTSERVER run?

The 48-hour average is 79 server fps, with a low of 51. Buildings, deployables and all else in the world took the count as high as 122,652 entities. A high of 7,010 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on TESTSERVER?

Version Rust network protocol 2635 and build 168909 on Linux is reported by TESTSERVER. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TESTSERVER, and is it online now?

TESTSERVER reports itself online at the current refresh. A restart about 2 days 17 hours ago is what its reported uptime implies. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does TESTSERVER sit?

There is no region published for TESTSERVER. 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 141.95.13.69:26111.

Rules, settings, map

Which settings and rules does TESTSERVER run?

The name TESTSERVER carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

What is the map on TESTSERVER?

The game generates the map on TESTSERVER: procedural, size 4,500, seed 246426222. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does TESTSERVER wipe, and on what schedule?

The record for TESTSERVER holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 20 days 10 hours ago.

What is wipe day on TESTSERVER like?

Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.

Lists and tags

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

These Rust Data lists include TESTSERVER: 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 TESTSERVER?

These tags are published by TESTSERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. 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 TESTSERVER?

In Rust, F1 opens the console: type client.connect 141.95.13.69:26111. 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 50 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

Mods and access

^z
Modded Plugins or settings alter the game, so it sits under Modded.
^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 32,314 players 11,621 servers online