Rust Data

rustdata.spaceservers95.189.108.10:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 95.189.108.10:28015 checked 8h ago

ТЕСТ

moddedoxide

Connect

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

Right now

srv.summary()
players now 1/?
7-day average 1 # peak 1
rank #5,004 # top 22%
last wipe 3d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75112:0017:0003:0008:0012:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020012:0017:0003:0008:0012:0017: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 21 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
15k10k15k20k21 Sep29 Sep7 Oct14 Oct22 Oct30 Oct

Top 22% 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 gap2.7 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 26 OctThu 22 OctSun 18 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, 4 hours in, with 1 in the queue.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 26 Oct, 01:52 UTC4d ago 1+1 queue NaN running 0
1 Thu 22 Oct, 03:48 UTC7d ago 0 NaN 3.9 days 0
2 Sun 18 Oct, 08:49 UTC11d ago 0 NaN 3.8 days 0
3 Tue 13 Oct, 15:30 UTC16d ago 0 NaN 4.7 days 0
4 Sat 10 Oct, 04:04 UTC19d ago 0 NaN 3.5 days 0
5 Fri 9 Oct, 10:12 UTC20d ago 0 NaN 0.7 days 0
6 Thu 8 Oct, 11:01 UTC21d ago 0 NaN 1 days 0
7 Wed 7 Oct, 12:28 UTC22d ago 1 NaN 0.9 days 1
8 Mon 5 Oct, 12:18 UTC24d ago 1 held half 2 days 0
9 Sun 4 Oct, 16:12 UTC25d ago 1 NaN 0.8 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

4250 · seed 62340382
Map of ТЕСТ
map
Procedural Map
size
4250
seed
62340382
Open on RustMaps

Server

srv.info()
address
95.189.108.10:28015
region
–
max players
–
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 04:43 UTC
hostname
^
first seen
21 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average132/100
1RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 122 on average34/225
2404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 97 on average2/700
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 94 on average6/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average127/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 85 on average3/1000

Quick answers

From the figures on this page.

Population

What position does ТЕСТ take in the server rankings?

Over the last seven days ТЕСТ sits at #5,004 on player hours, in the top 22% of ranked servers.

How many players does ТЕСТ hold at once?

The current row shows ТЕСТ offline; the last response was 8 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 13:00 UTC is the busiest, at 1 players.

Server facts

How smoothly does ТЕСТ run?

The 48-hour average is 158 server fps, with a low of 115. Buildings, deployables and all else in the world took the count as high as 115,647 entities. Memory peaked at 3,703 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on ТЕСТ?

Rust network protocol 2635 and build 168909 on Windows is what ТЕСТ runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is ТЕСТ, and is it online now?

Offline now for ТЕСТ, last seen 8 hours ago. Count back 14 hours from its reported uptime to get the last restart. 58 of 168 hours up over the last 7 full days, or 35%. Its earliest recorded date in Rust Data is 21 September 2026.

In which location is ТЕСТ hosted?

The name of ТЕСТ points to Europe, even though no region tag is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 95.189.108.10:28015.

Settings and map

Which settings and rules does ТЕСТ run?

The name ТЕСТ carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has ТЕСТ selected?

ТЕСТ runs a procedural map of size 4,250 with seed 62340382, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does ТЕСТ wipe, and on what schedule?

ТЕСТ wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 3 days 21 hours ago.

What is wipe day on ТЕСТ like?

The average peak over recent wipes is 0 players. On the latest wipe the peak came 4 hours after the wipe, with a queue of 1.

Tags, lists

Which Rust Data filters and lists contain ТЕСТ?

The Rust Data lists that ТЕСТ fits are: EU Rust servers and Modded Rust servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

How should you read the server tags on ТЕСТ?

Read by the game's server browser, the tags ТЕСТ publishes are: gmvanilla (Game mode): Survival in vanilla form; mp0 (Max players): Slot count: 0; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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

What is the way into ТЕСТ?

Enter client.connect 95.189.108.10: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 mp0,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp0
Max players Slot count: 0.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded The Modded section lists it, because plugins or settings change the game.

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 49,472 players 11,703 servers online