Rust Server Analytics 37,258 players11,622 servers
All servers
Drill-through Server detail

ほしラス2

Offline 157.85.88.185:26843 checked 14h ago

Drill-through
FilterServeris ほしラス2
Attributes
teams off moddedoxidehardcore
Last refreshed
Players now 1/ 50
7-day average 1 peak 2
Rank #5,495 top 25%
Last wipe 1d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 2% full

Players

average and peak, with its wipes marked
AveragePeakWipe
00.511.5223:0002:0006:0009:0013:0016:00Wiped Tue 27 Oct, 23:21 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
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
RankRank in region
15k10k15k20k19 Oct21 Oct23 Oct25 Oct27 Oct29 Oct

Top 25% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

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
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 23:21 UTC1d ago – – running 1
Sat 24 Oct, 13:13 UTC4d ago 1 – 3.4 days 1
Fri 23 Oct, 01:59 UTC6d ago 1 – 1.5 days 1
Mon 19 Oct, 18:49 UTC9d ago 1 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 EA · groups of 20+ · weekly · 24 on average 30 / 100
【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐 EA · groups of 8+ · weekly · 20 on average 22 / 200
[JP]初心者PVPサーバー|RaidTime・ Events EA · groups of 10+ · biweekly · 16 on average 8 / 100
[守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新 EA · no group limit · 11 on average 20 / 100
[JP] DON-tacos PvE EA · groups of 8+ · monthly · 11 on average 8 / 100
#10-[搞就完了]10倍/10.29新档/无权/萌新首选 EA · no group limit · 11 on average 19 / 100

Quick answers

from the figures on this page

Wipe cycle

On what cycle does ほしラス2 wipe?

With irregular wipe times, ほしラス2 offers no next wipe to predict. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The current world dates from 31 hours.

Wipe day on ほしラス2: what should you expect?

The average busiest count over recent wipes is 1 players. 0 hours after the latest wipe the crowd peaked.

Server details

In which region does ほしラス2 sit?

Without a region tag, ほしラス2 still has a name that points to Asia. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 157.85.88.185:26843.

What Rust build does ほしラス2 run?

Rust network protocol 2635 and build 168909 on Linux is the setup for ほしラス2. Your game must match the protocol to join, and Steam applies that update.

Is ほしラス2 up, and how steady is its uptime?

Offline at this refresh: ほしラス2, last seen 14 hours ago. Its reported uptime indicates a restart roughly 16 hours ago. Uptime over the last full days (7) was 18%, or 31 of 168 hours. 19 October 2026 is when Rust Server Analytics first recorded it.

What performance does ほしラス2 show?

The 48-hour average was 212 server fps; the low was 173. At its highest the entity count was 99,932, including buildings, deployables and all else. Peak memory was 4,190 MB. A climbing entity count and low fps are the lag players perceive.

Lists and tags

What do ほしラス2's tags stand for?

gmhardcore (Game mode): A harsher ruleset: hardcore; mp50 (Max players): 50 slots in total; ts0 (Group limit): No teams here; v2635 (Protocol): Joining needs your game on protocol 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play are the tags ほしラス2 publishes, and the game's server browser reads them. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does ほしラス2 appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count ほしラス2 among their servers: Modded Rust servers: live data. On the server list, the filters that return it are: Region: Asia; Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o; Last wipe: In the last 3 days.

Population

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

Player hours for the last seven days place ほしラス2 at #5,495, in the top 25% of the ranked field.

What is the population of ほしラス2?

The last sighting of ほしラス2 was 14 hours ago; it is offline at this refresh. The seven-day mean is 1 players, against a peak of 2. Across the last 48 hours, 12:00 UTC shows the highest average: 2 players.

Map and rules

How is ほしラス2 configured, and what rules apply?

Gather rate is not mentioned in the name of ほしラス2. Group limits are not published. hardcore is the game mode, Facepunch's most difficult mode. Both fighting and raiding between players are allowed. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. VAC, Valve's anti-cheat, is enabled.

The map on ほしラス2: which one is it?

The game generates a procedural map of size 4,000 for ほしラス2. The name of the map is Custom Map.

Connection

How do you connect to ほしラス2?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 157.85.88.185:26843.

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmhardcore,cs168909,ts0,^o^z

Game

gmhardcore
Game mode A harsher ruleset: hardcore.
mp50
Max players 50 slots in total.
ts0
Group limit No teams here.
v2635
Protocol Joining needs your game on protocol 2635.
cs168909
Build Game build: 168909.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The Modded section, because plugins or settings modify play.

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.