Rust Data

rustdata.spaceservers157.85.88.185:26844.ipynb

Run all rust-data · live

‹ All servers

Offline 157.85.88.185:26843 checked 4h ago

ほしラス2

teams off moddedoxidehardcore

Connect

srv = rust.server("157.85.88.185:26844")
print(srv.connect_command)

Right now

srv.summary()
players now 1/50 # 2% full
7-day average 1 # peak 2
rank #5,486 # top 25%
last wipe 22h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.511.5223:0002:0006:0009:0013:0016:00Wiped Tue 27 Oct, 23:21 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
010020030040023:0002:0006:0009:0013:0016:00Wiped Tue 27 Oct, 23:21 UTCWIPE

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 19 Oct. 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
15k10k15k20k19 Oct21 Oct23 Oct24 Oct26 Oct28 Oct

Top 25% 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.3 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sat 24 OctFri 23 OctMon 19 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 Tue 27 Oct, 23:21 UTC22h ago NaN NaN running 1
1 Sat 24 Oct, 13:13 UTC4d ago 1 NaN 3.4 days 1
2 Fri 23 Oct, 01:59 UTC5d ago 1 NaN 1.5 days 1
3 Mon 19 Oct, 18:49 UTC9d ago 1 NaN 3.3 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 0
Custom map, no picture published
map
Custom Map
size
4000
seed
–

Server

srv.info()
address
157.85.88.185:26843
region
–
max players
50
group limit
teams off
wipe schedule
–
last wipe
27 Oct 2026, 23:21 UTC
hostname
–
first seen
19 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 24 on average29/100
1【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 18 on average31/200
2[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 17 on average1/100
3[JP] DON-tacos PvEEA · groups of 8+ · monthly · 11 on average1/100
4#10-[搞就完了]10倍/10.28新档/无权/萌新首选EA · no group limit · 11 on average18/100
5[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新EA · no group limit · 11 on average20/100

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does ほしラス2 rank?

Rank #5,486 on seven-day player hours for ほしラス2, within the top 25% of all ranked servers.

How many players does ほしラス2 hold at once?

The current row shows ほしラス2 offline; the last response was 4 hours ago. Over the last seven days it averaged 1 players and peaked at 2. The 48-hour sample puts the busiest hour at 12:00 UTC, averaging 2 players.

Server data

What does performance look like on ほしラス2?

The 48-hour average is 212 server fps, with a low of 173. Buildings, deployables and all else in the world took the count as high as 99,932 entities. The memory field tops out at 4,190 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is ほしラス2 on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by ほしラス2. Steam updates your game for you, but the protocol must match to join.

How reliable is ほしラス2, and is it up?

Offline now for ほしラス2, last seen 4 hours ago. A restart about 16 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 14 of 168, 8%. Rust Data logged it first on 19 October 2026.

Where does ほしラス2 sit?

No region tag is published by ほしラス2, though its name points to Asia. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.88.185:26843 is its address.

Map and rules

What rules and settings are recorded for ほしラス2?

No gather rate appears in the name: ほしラス2. No group limit is published. Recorded as hardcore, Facepunch at its most unforgiving. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.

What is the map on ほしラス2?

Generated by the game at size 4,000, the map on ほしラス2 is procedural. Custom Map is what the map name field says.

Wipe schedule

When does ほしラス2 wipe, and on what schedule?

ほしラス2 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. A new world was started 22 hours ago, and that is the one in play.

What is wipe day on ほしラス2 like?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.

Lists and tags

Which lists on Rust Data hold ほしラス2, and which filters?

On Rust Data, ほしラス2 appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 24 hours.

Which meanings do the tags on ほしラス2 hold?

The game's server browser reads these tags from ほしラス2: gmhardcore (Game mode): Hardcore ruleset, the harsher one; mp50 (Max players): The server lists 50 slots; ts0 (Group limit): The team system is off; 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): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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

How can I connect to ほしラス2?

Enter client.connect 157.85.88.185:26843 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,gmhardcore,cs168909,ts0,^o^z

Game

gmhardcore
Game mode Hardcore ruleset, the harsher one.
mp50
Max players The server lists 50 slots.
ts0
Group limit The team system is off.
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 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 69,961 players 11,800 servers online