Rust Data

rustdata.spaceservers144.6.242.42:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 144.6.242.42:28015 checked 3d ago

VIP Stacks Test (local)

moddedoxide

Connect

srv = rust.server("144.6.242.42:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/4 # 25% full
7-day average 1 # peak 1
rank #7,150 # top 32%
last wipe 4d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
No hourly history yet.

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
15k10k15k20k10 Oct14 Oct18 Oct21 Oct25 Oct29 Oct

Top 32% 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.5 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

Thu 22 OctSat 17 OctSun 11 Oct
010203040+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 Sat 24 Oct, 19:19 UTC4d ago NaN NaN running 0
1 Sat 24 Oct, 10:48 UTC5d ago NaN NaN NaN 1
2 Thu 22 Oct, 14:12 UTC7d ago 1 NaN 1.9 days 1
3 Sat 17 Oct, 11:00 UTC12d ago 1 held half 5.1 days 0
4 Sun 11 Oct, 07:18 UTC18d ago 60 NaN 6.2 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

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
144.6.242.42:28015
region
–
max players
4
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 19:41 UTC
hostname
–
first seen
10 Oct 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 · 149 on average186/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average134/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average179/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 94 on average91/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 86 on average284/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 86 on average236/700

Quick answers

From the figures on this page.

Population data

How does VIP Stacks Test (local) compare in the rankings?

Rank #7,150 on seven-day player hours for VIP Stacks Test (local), within the top 32% of all ranked servers.

How many players does VIP Stacks Test (local) hold at once?

Offline now for VIP Stacks Test (local), with the last sample 3 days 19 hours ago. Over the last seven days it averaged 1 players and peaked at 1.

About the server

What Rust version does VIP Stacks Test (local) run?

Version Rust network protocol 2635 and build 168909 on Windows is reported by VIP Stacks Test (local). The protocol has to match before you can join, and Steam does the updating.

How reliable is VIP Stacks Test (local), and is it up?

VIP Stacks Test (local) is offline at this refresh; the last response came 3 days 19 hours ago. Uptime of 11% across the last 7 full days: 19 hours of 168. Its earliest recorded date in Rust Data is 10 October 2026.

In which location is VIP Stacks Test (local) hosted?

There is no region published for VIP Stacks Test (local). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 144.6.242.42:28015 is its address.

Rules, settings, map

Which rules apply on VIP Stacks Test (local), and what settings?

You will not find a gather rate in the string VIP Stacks Test (local). No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.

What is the map on VIP Stacks Test (local)?

The game generates its map: procedural, on VIP Stacks Test (local).

Wipes and dates

On what schedule does VIP Stacks Test (local) wipe?

VIP Stacks Test (local) wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 4 days 19 hours ago.

What is wipe day on VIP Stacks Test (local) like?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Tags, lists

Which Rust Data filters and lists contain VIP Stacks Test (local)?

The Rust Data lists that VIP Stacks Test (local) 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 week.

Which meanings do the tags on VIP Stacks Test (local) hold?

Read by the game's server browser, the tags VIP Stacks Test (local) publishes are: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; 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): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.

Join steps

What is the way to join VIP Stacks Test (local)?

The manual route: launch Rust, F1, then client.connect 144.6.242.42:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp4,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp4
Max players Slot count: 4.
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 No region code is set.

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 90,153 players 11,869 servers online