Rust Data

rustdata.spaceservers142.91.157.60:28026.ipynb

Run all rust-data · live

‹ All servers

Offline 142.91.157.60:28025 checked 5d ago

LOW.MS Linux test H2

Connect

srv = rust.server("142.91.157.60:28026")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,349 # top 69%
last wipe 5d 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, 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 Sep26 Sep2 Oct7 Oct23 Oct29 Oct

Top 69% 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 gap18.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak5players, last three wipes
crowd held0%else halves by day 6

The first 48 hours of its last wipes

Fri 23 OctThu 1 OctThu 17 Sep
02468+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 21:17 UTC5d ago 0 NaN running 0
1 Thu 1 Oct, 17:45 UTC FW27d ago 5 halved by day 2 22.1 days 0
2 Thu 17 Sep, 17:04 UTC41d ago 9 halved by day 10 14 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

4000 · seed 1305034293
Map of LOW.MS Linux test H2
map
Custom Map
size
4000
seed
1305034293

Server

srv.info()
address
142.91.157.60:28025
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 01:13 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
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 549 on average152/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average116/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average13/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 284 on average23/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average12/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average28/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does LOW.MS Linux test H2 rank?

Over the last seven days LOW.MS Linux test H2 sits at #15,349 on player hours, in the top 69% of ranked servers.

How full does LOW.MS Linux test H2 run?

Offline now for LOW.MS Linux test H2, with the last sample 5 days 2 hours ago. Over the last seven days it averaged 0 players.

Server data

What is the Rust version on LOW.MS Linux test H2?

The build is Rust network protocol 2635 and build 168909 on Windows, run by LOW.MS Linux test H2. Steam updates your game for you, but the protocol must match to join.

How reliable is LOW.MS Linux test H2, and is it up?

Offline now for LOW.MS Linux test H2, last seen 5 days 2 hours ago. 4 of 168 hours up over the last 7 full days, or 2%. The first row Rust Data holds for it is dated 13 September 2026.

Which location does LOW.MS Linux test H2 run from?

There is no region published for LOW.MS Linux test H2. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 142.91.157.60:28025.

Settings and map

Which rules apply on LOW.MS Linux test H2, and what settings?

No gather rate appears in the name: LOW.MS Linux test H2. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.

Which map has LOW.MS Linux test H2 selected?

The game generates the map on LOW.MS Linux test H2: procedural, size 4,000, seed 1305034293. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.

Wipe schedule

When does LOW.MS Linux test H2 wipe, and on what schedule?

Irregular wipe times on LOW.MS Linux test H2 leave no next wipe to forecast. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 5 days 2 hours ago.

On LOW.MS Linux test H2, what happens on wipe day?

Recent wipes averaged 5 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 6.

Tags and filters

Which lists on Rust Data hold LOW.MS Linux test H2, and which filters?

On Rust Data, LOW.MS Linux test H2 appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Which meanings do the tags on LOW.MS Linux test H2 hold?

The game's server browser reads these tags from LOW.MS Linux test H2: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): 50 slots in total; 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): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. 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 into LOW.MS Linux test H2?

In Rust, F1 opens the console: type client.connect 142.91.157.60:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8

Game

gmvanilla
Game mode Survival in vanilla form.
mp50
Max players 50 slots in total.
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 The network layer is RakNet, standard for the game.
$r?
Region code Region code: not set.

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 32,896 players 11,657 servers online