Rust Data

rustdata.spaceservers89.34.97.16:28245.ipynb

Run all rust-data · live

‹ All servers

Online 89.34.97.16:28310 checked 9m ago

Mabels Test Server

moddedoxide

Connect

srv = rust.server("89.34.97.16:28245")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 1
rank #10,323 # top 46%
last wipe 14d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608023:0008:0017:0002:0011:0021: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 Sep5 Oct13 Oct20 Oct28 Oct

Top 46% 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 gap3 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 2

The first 48 hours of its last wipes

Wed 14 OctSat 3 OctWed 30 Sep
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 Wed 14 Oct, 18:14 UTC14d ago 1 NaN running 0
1 Sat 3 Oct, 00:23 UTC25d ago 1 halved by day 2 11.7 days 0
2 Wed 30 Sep, 10:00 UTC28d ago 0 NaN 2.6 days 0
3 Sun 27 Sep, 09:36 UTC31d ago 1 held half 3 days 0
4 Fri 25 Sep, 21:27 UTC33d ago 1 NaN 1.5 days 0
5 Sat 19 Sep, 20:30 UTC39d ago 1 held half 6 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

3500 · seed 1862422565
Map of Mabels Test Server
map
Procedural Map
size
3500
seed
1862422565
Open on RustMaps

Server

srv.info()
address
89.34.97.16:28310
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
14 Oct 2026, 20:41 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 · 157 on average62/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average131/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 · 92 on average51/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average16/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average10/1000

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Mabels Test Server rank?

Over the last seven days Mabels Test Server sits at #10,323 on player hours, in the top 46% of ranked servers.

How many players does Mabels Test Server hold at once?

The sample now reads 0 players for Mabels Test Server, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1.

About the server

How smoothly does Mabels Test Server run?

Averaged over 48 hours: 60 server fps, never under 60. Entity numbers reached 26,371, and that includes buildings, deployables and the rest. The memory field tops out at 1,646 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is Mabels Test Server on?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Mabels Test Server. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Mabels Test Server, and is it online now?

Mabels Test Server reports itself online at the current refresh. The uptime it reports puts the last restart about 14 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 13 September 2026.

In which location is Mabels Test Server hosted?

There is no region published for Mabels Test Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 89.34.97.16:28310 is its address.

Settings and map

Which rules apply on Mabels Test Server, and what settings?

No gather rate appears in the name: Mabels Test Server. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on Mabels Test Server?

Mabels Test Server runs a procedural map of size 3,500 with seed 1862422565, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

When does Mabels Test Server wipe, and on what schedule?

Mabels Test Server 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 14 days 2 hours ago.

What is wipe day on Mabels Test Server like?

Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 67% of recent wipes. In the wipes where it did not hold, half was lost by day 2.

Tags and filters

Which Rust Data filters and lists contain Mabels Test Server?

These Rust Data lists include Mabels Test Server: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meanings do the tags on Mabels Test Server hold?

These tags are published by Mabels Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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.

Join steps

How can I connect to Mabels Test Server?

Enter client.connect 89.34.97.16:28310 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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^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 57,310 players 11,753 servers online