Rust Data

rustdata.spaceservers88.198.7.190:28117.ipynb

Run all rust-data · live

‹ All servers

Online 88.198.7.190:28115 checked 10m ago

Test Server

solo vanillamoddedcarbon

Connect

srv = rust.server("88.198.7.190:28117")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak 2
rank #9,414 # top 42%
last wipe 6d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123404:0013:0023:0008:0017:0002:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304004:0013:0023:0008:0017:0002: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 18 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 Sep23 Sep27 Sep30 Sep27 Oct30 Oct

Top 42% of all ranked servers, and #177 of the solo servers (top 79%). 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.

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 22:02 UTC6d ago 2 NaN running 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

4250 · seed 1234
Map of Test Server
map
Custom Map
size
4250
seed
1234

Server

srv.info()
address
88.198.7.190:28115
region
–
max players
10
group limit
solo
wipe schedule
–
last wipe
23 Oct 2026, 22:02 UTC
hostname
lagcityrp.p-o-t.net
first seen
18 Sep 2026

Operator · p-o-t.net

rust.servers(operator="p-o-t.net").sort_values("players")
serverplayers
0 LagCity RP [GER] by PoT1/99

2 servers publish a p-o-t.net hostname.

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

rust.similar(srv).head(6)
serverlike_thisplayers
0[LATAM] Estrella Solitaria SOLO ONLY | 29/10 Full WipeSA · solo · weekly · 19 on average45/100
1SOLO ONLY | FULL WIPE 29.10 | UA | EU | ПАЛЯНИЦЯ | UKREU · solo · weekly · 16 on average8/100
2【疾风】5倍|单人|独狼|10.23新档|新手|快速入门EA · solo · weekly · 15 on average1/100
3[GUA] MODDED 2Х | SOLO | EU | MAP WIPE 27.10EU · solo · weekly · 5 on average3/200
4404 RUST SOLO | ВС | ДЛЯ НОВИЧКОВ 25.10EU · solo · monthly · 5 on average0/400
5404 RUST SOLO | ПН | ДЛЯ НОВИЧКОВ 26.10EU · solo · monthly · 4 on average2/400

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Test Server rank?

Rank #9,414 on seven-day player hours for Test Server, within the top 42% of all ranked servers. Within the solo group, its rank is #177.

How many players does Test Server hold at once?

Current row: 0 players on Test Server, against 10 slots. Over the last seven days it averaged 0 players and peaked at 2.

Server facts

What does performance look like on Test Server?

Averaged over 48 hours: 40 server fps, never under 40. Buildings, deployables and all else in the world took the count as high as 61,929 entities. A high of 3,881 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What Rust version does Test Server run?

The build is Rust network protocol 2635 and build 168909 on Linux, run by Test Server. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Test Server, and is it up?

Test Server reports itself online at the current refresh. The uptime it reports puts the last restart about 11 hours ago. Uptime of 76% across the last 7 full days: 127 hours of 168. The first row Rust Data holds for it is dated 18 September 2026.

In which location is Test Server hosted?

No region is published by Test Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 88.198.7.190:28115 is its address.

Settings and map

What rules and settings are recorded for Test Server?

The name Test Server carries no gather rate. No teams here: solo only. survival is the game mode here, and gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. VAC, Valve's anti-cheat, is enabled.

Which map has Test Server loaded?

Test Server runs a procedural map of size 4,250 with seed 1234, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.

Wipe schedule

When does Test Server wipe, and how often?

Too few wipes are on record for Test Server to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 6 days 5 hours ago.

On Test Server, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 22 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain Test Server?

These Rust Data lists include Test Server: Modded Rust servers and Solo Rust servers, group limit 1. It appears under these filters on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: Solo; Last wipe: In the last week.

Which operator runs Test Server?

Test Server and 1 other server we track both publish a p-o-t.net hostname, so the same operator most likely runs them.

How should you read the server tags on Test Server?

Read by the game's server browser, the tags Test Server publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts1 (Group limit): Team size tops out at 1; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is 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 Server?

In Rust, F1 opens the console: type client.connect 88.198.7.190:28115. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://www.lagcity.eu/.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,^z,^y,^v,gmrust,cs168909,ts1

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players The server lists 10 slots.
ts1
Group limit Team size tops out at 1.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla Facepunch's stock game, with rates, kits and rules untouched.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon The plugin framework in use is 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 43,996 players 11,654 servers online