Rust Data

rustdata.spaceservers91.245.44.75:28520.ipynb

Run all rust-data · live

‹ All servers

Offline 91.245.44.75:28018 checked 17h ago

Vitality Local LiveTest

moddedoxide

Connect

srv = rust.server("91.245.44.75:28520")
print(srv.connect_command)

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123415:0021:0003:0009:0015:0021: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
15k10k15k20k20 Sep27 Sep5 Oct13 Oct21 Oct28 Oct

Top 50% 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 gap0.9 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

Wed 21 OctThu 15 OctWed 14 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 Wed 21 Oct, 12:41 UTC7d ago 1 NaN running 0
1 Thu 15 Oct, 12:50 UTC13d ago 1 NaN 6 days 0
2 Wed 14 Oct, 18:26 UTC13d ago 1 NaN 0.8 days 0
3 Sun 11 Oct, 03:29 UTC17d ago 1 held half 3.6 days 1
4 Sat 10 Oct, 08:08 UTC18d ago 1 NaN 0.8 days 0
5 Fri 9 Oct, 22:26 UTC18d ago 1 NaN 0.4 days 1
6 Wed 30 Sep, 11:49 UTC28d ago 2 NaN 9.4 days 1
7 Tue 29 Sep, 09:38 UTC29d ago 2 NaN 1.1 days 0
8 Mon 28 Sep, 14:40 UTC29d ago 2 NaN 0.8 days 0
9 Sun 27 Sep, 10:26 UTC31d ago 1 NaN 1.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
91.245.44.75:28018
region
–
max players
10
group limit
32 max
wipe schedule
–
last wipe
15 Oct 2026, 12:50 UTC
hostname
–
first seen
16 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 · 156 on average187/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average125/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average188/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 89 on average149/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average20/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average44/1000

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Vitality Local LiveTest rank?

Player hours over seven days put Vitality Local LiveTest at #11,080, in the top 50% of the ranked set.

How full does Vitality Local LiveTest run?

The current row shows Vitality Local LiveTest offline; the last response was 17 hours ago. Over the last seven days it averaged 0 players and peaked at 1.

Server facts

What is the Rust version on Vitality Local LiveTest?

The build is Rust network protocol 2635 and build 168909 on Windows, run by Vitality Local LiveTest. Joining needs the same protocol on your game; Steam handles the update.

How reliable is Vitality Local LiveTest, and is it online now?

Offline now for Vitality Local LiveTest, last seen 17 hours ago. 88 of 168 hours up over the last 7 full days, or 52%. Its earliest recorded date in Rust Data is 16 September 2026.

In which location is Vitality Local LiveTest hosted?

There is no region published for Vitality Local LiveTest. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 91.245.44.75:28018.

Rules, settings, map

Which rules apply on Vitality Local LiveTest, and what settings?

The name Vitality Local LiveTest carries no gather rate. The cap on a group is 32 players. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. The VAC field reads off.

Which map has Vitality Local LiveTest loaded?

The game generates its map: procedural, on Vitality Local LiveTest.

Wipes and dates

When does Vitality Local LiveTest wipe, and how often?

Irregular wipe times on Vitality Local LiveTest leave no next wipe to forecast. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 13 days 1 hours ago, and that is the one in play.

What is wipe day on Vitality Local LiveTest like?

Across recent wipes the busiest point averaged 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 Vitality Local LiveTest, and which filters?

The Rust Data lists that Vitality Local LiveTest fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Which meanings do the tags on Vitality Local LiveTest hold?

These tags are published by Vitality Local LiveTest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts32 (Group limit): Team size tops out at 32; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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

How can I connect to Vitality Local LiveTest?

Enter client.connect 91.245.44.75:28018 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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts32,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts32
Group limit Team size tops out at 32.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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 80,834 players 11,765 servers online