Rust Server TrendsSeismic network · station log
Recording Stations11,865 Players103,410 Active3,960 Wipes · 3 h555 48 h

Station EA-726 · recording

[JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28

Online EA 160.251.231.184:28015 checked 10m ago

solo weekly wipes vanillaoxide
Connect
Players now
18/ 100
18% full
Motion · 24 h
M1.2falling
−17 players on the day
7-day average
16
peak 61
Rank
#726
top 3% · #46 in EA
Last wipe
1d ago
weekly schedule
Next wipe
5d 13h
Wed 4 Nov, 08:46 UTC
Seismic record · station EA-726 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
18of 100 slots
Motion · 24 h
M1.2falling−17 players
Sharpest hour
+21into Wed 09:00 UTC
Peak · 48 h
61most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
02040608020:0008:0016:0002:0010:0018:00Wiped Wed 28 Oct, 08:46 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
025507510020:0008:0016:0002:0010:0018:00Wiped Wed 28 Oct, 08:46 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15001k1.5k2k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 3% of all ranked servers, top 9% in EA, and #32 of the solo servers (top 14%). Ranked on player hours over the last seven days.

Expected events

Wipe schedule

a steady gap

Next wipe Wednesday 4 November, 08:46 UTC, in 5d 13h. Every 7 days · medium confidence

usual gap
7 daysbetween real wipes
on rhythm
67%of its recent wipes
wipe-day peak
52players, last three wipes
crowd held
0%else halves by day 3

Coming wipes

  1. 5d 13hWed 4 Nov, 08:46 UTC
  2. 6d 23hThu 5 Nov, 19:00 UTCFW
  3. 12d 13hWed 11 Nov, 08:46 UTC
  4. 19d 13hWed 18 Nov, 08:46 UTC
  5. 26d 13hWed 25 Nov, 08:46 UTC
  6. 33d 13hWed 2 Dec, 08:46 UTC
  7. 34d 23hThu 3 Dec, 19:00 UTCFW
  8. 40d 13hWed 9 Dec, 08:46 UTC

The first 48 hours of its last wipes

Wed 21 OctWed 14 OctWed 7 Oct
020406080+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 28 Oct, 08:46 UTC1d ago – – – – running 2
Wed 21 Oct, 08:46 UTC8d ago M1.7rising 58 halved by day 3 7 days 3
Wed 14 Oct, 08:46 UTC15d ago M1.7rising 56 halved by day 3 7 days 1
Wed 7 Oct, 08:46 UTC22d ago M1.6rising 41 halved by day 3 7 days 1
Fri 2 Oct, 08:46 UTC27d ago M1.5rising 32 halved by day 4 5 days 0
Wed 23 Sep, 05:10 UTC36d ago M1.7rising 48 halved by day 3 9.1 days 2
Wed 16 Sep, 08:48 UTC43d ago M1.9rising 72 halved by day 2 6.8 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
4/ 100
单宇宙|10.25号|独狼|萌新|禁止组队 EA · solo · weekly · 30 on average
0/ 200
独角兽|10.29号|12:00清档|独狼|萌新 EA · solo · weekly · 30 on average
51/ 200
单世界|10.29号|独狼|萌新|禁止组队 EA · solo · weekly · 30 on average
3/ 200
青山仿官-萌新养老,周清,独狼,10.23-19:15新 EA · solo · weekly · 2 on average
0/ 119
25/ 100
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28?

At size 3,700, the map on [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 is custom and its published file can be downloaded from this page.

Which settings and rules apply on [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28?

The name of [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 gives no gather rate. Teams are not allowed here; it is solo only. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. It is a community server, and the browser lists it under Community. The plugins run on Oxide. By its own description it is vanilla: rates, kits and rules are as Facepunch ships them. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28?

At this moment, [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 records 18 players across 100 slots. Across seven days this server recorded an average of 16 players and a peak of 61. Averaged over the last 48 hours, the busiest hour was 12:00 UTC at 57 players.

How does [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 rank against other Rust servers?

The last seven days of player hours place [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 at #726, in the top 3% of all ranked servers and #46 in Asia. The ranking for solo puts it at #32.

Server details

How reliably does [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 stay online?

[JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 is up at the moment. Its reported uptime points to a restart about 21 hours ago. It was up 97% of the time across the last 7 full days: 163 of 168 hours. On 13 September 2026 it was recorded for the first time by Rust Server Trends.

How well does [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 perform under load?

The 48-hour average is 48 server fps; 25 is the lowest observed. The world held up to 115,852 entities at its peak, buildings and deployables included. It reached a ceiling of 3,837 MB of memory. Low fps together with a growing entity count is what players experience as lag.

Where in the world is [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 hosted?

The EA tag is how [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 lists itself in Asia. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 160.251.231.184:28015.

What build of Rust does [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 use?

Rust network protocol 2635 and build 168909 on Linux is what [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

What does wipe day look like on [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28?

52 players, on average, was the busiest crowd at its recent wipes. 5 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell under half by day 3 in the wipes where it didn't hold.

How often does [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 wipe, and on which days?

About every 7 days is how often [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 has wiped lately. Wednesday 4 November at 08:46 UTC is when its next wipe is due. The present world dates from 34 hours. A weekly wipe schedule is published in its tags.

Tags

What do the server tags on [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 mean?

Tags published by [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 and read by the game's server browser include gmvanilla (Game mode): Survival in vanilla mode; mp100 (Max players): 100 slots are available; ts1 (Group limit): Teams are capped at 1 players; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^w (Weekly): A wipe comes once a week; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; EA (East Asia): In the server browser it appears under East Asia; rustmaps (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 appear?

You will find [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 on the following Rust Server Trends lists: Rust community servers without the side modes, Solo Rust servers and Vanilla Rust servers, recorded live. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Vanilla ^v and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last 3 days; Players now: At least 10; Average players: 10+ on average.

Which person or group runs [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28?

One operator most likely runs these: [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28 and 2 other servers we track, all publishing a sorayu.me hostname.

Join the server

How do you connect to [JP] RUST☆STAR - SoloOnly/Under3000H|Wed/水曜日|10/28?

You can connect by pressing F1 in Rust and typing client.connect 160.251.231.184:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. You can find its website at https://rust-star.sorayu.me/.

Instrument codes

Server tags

what each one means

Published as mp100,ptrak,$r?,v2635,^w,^v,EA,gmvanilla,cs168909,ts1,rustmaps,^o,rustmaps

Game

gmvanilla
Game mode Survival in vanilla mode.
mp100
Max players 100 slots are available.
ts1
Group limit Teams are capped at 1 players.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Wipe schedule

^w
Weekly A wipe comes once a week.

Difficulty

^v
Vanilla Rates, kits and rules are as Facepunch ships them.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.

Region

EA
East Asia In the server browser it appears under East Asia.

Other

rustmaps
Custom tag The owner or a plugin set this tag, and it's not one of Rust's standard tags.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.