RUST METRICSFlight deck · live data
Data live Servers11,701 Players42,340 Populated3,047 Fresh wipes 3 h101 Scan5 min
‹ All servers58.191.44.84:28015
Offline Full Queue Fresh wipe Wipe due No query

[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21

Offline EA 58.191.44.84:28015 checked 1d ago

trio weekly wipes vanillaoxide
COM 1 · connect
Launch Rust and join Website

Server instruments

last reading Wed 00:00 UTC
0 45 90 135 180 PAX 0 /180

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 67 SERVER FPS

Server fps

48 h low 26 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 118,855 ×1000

Entities

48 h range 118,855–131,240 · memory 2,617 MB
1239 ET SINCE RESTART 02:32

Uptime

2 h 32 min since its last restart, at the last reading
7-day average30peak 158
Rank#583top 3% · #24 in EA
Last wipe7d agoweekly schedule
Next wipe6d 1hWed 4 Nov, 02:46 UTC
Memory2,617MB48 h peak 6 players
REC 1

Players
AveragePeak
0246802:0006:0011:0015:0020:0000:00

Hourly average and peak, UTC.

REC 2

Server performance
02040608002:0006:0011:0015:0020:0000:00

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.

REC 3

Rank

daily · 1 is best
RankRank in region
120040060080020 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

PLAN

Wipe schedule

fixed weekdays

Next wipe Wednesday 4 November, 02:46 UTC, in 6d 1h. Every Wednesday at 02:46 UTC · high confidence

usual gap7 daysbetween real wipes
on rhythm83%of its recent wipes
wipe-day peak178players, last three wipes
crowd held0%else halves by day 3

Coming wipes

  1. WPT 1Wed 4 Nov, 02:46 UTC6d 1h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 17hFW
  3. WPT 3Wed 11 Nov, 02:46 UTC13d 1h
  4. WPT 4Wed 18 Nov, 02:46 UTC20d 1h
  5. WPT 5Wed 25 Nov, 02:46 UTC27d 1h
  6. WPT 6Wed 2 Dec, 02:46 UTC34d 1h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 17hFW
  8. WPT 8Wed 9 Dec, 02:46 UTC41d 1h

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 178, 11 hours in, with 32 in the queue.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 02:46 UTC7d ago 178+32 queue – running 0
Wed 14 Oct, 02:46 UTC14d ago 179+31 queue halved by day 2 7 days 0
Wed 7 Oct, 02:46 UTC21d ago 178+35 queue halved by day 3 7 days 0
Fri 2 Oct, 02:45 UTC26d ago 150+10 queue halved by day 3 5 days 1
Thu 1 Oct, 18:26 UTC FW27d ago 150+10 queue – 0.3 days 3
Wed 23 Sep, 02:46 UTC35d ago 180+36 queue halved by day 4 8.7 days 2
Wed 16 Sep, 01:35 UTC42d ago 164+46 queue halved by day 3 7 days 2

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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 when wipe day comes?

The busiest point of its recent wipes drew 178 players on average. 11 hours after the wipe the crowd peaked on the latest wipe, with 32 more in the queue. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. It fell below half by day 3 when it didn't.

How often does [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 wipe, and when?

The wipe rhythm of [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 is every Wednesday at 02:46 UTC. On Wednesday 4 November at 02:46 UTC its next wipe is due. The world in play was created 7 days 22 hours ago. The tags state a wipe schedule of one wipe a week.

Tag meanings

How should you read the tags on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?

These are the tags [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp180 (Max players): 180 slots in total; ts3 (Group limit): Team cap: 3; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^w (Weekly): Wipe cycle: weekly; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^o (Oxide): It runs Oxide, also known as uMod; EA (East Asia): Its browser listing: East Asia; rustmaps (Custom tag): Owner or plugin definition: this tag is not a standard Rust one. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which operator is behind [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?

Most likely the same operator runs them: [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 publishes a sorayu.me hostname, and so do 2 other servers we track.

Which lists and filters on Rust Metrics show [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?

These Rust Metrics lists carry [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21: Rust community servers: live readings, Trio servers, group limit 3 and Vanilla Rust servers, 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: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Average players: 25+ on average.

Player count

Where does [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 sit in the rankings?

Player hours over the last seven days put [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 at #583, #24 in Asia, in the top 3% of all ranked servers. Check: group rank. #56 among trio servers.

What is the population on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?

Status for [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21: offline. Last seen 25 hours ago. Seven-day check: 30 players on average. Peak reading: 158. Check: 48-hour peak. 12:00 UTC, 5 players on average.

Operator and location

Where does [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 sit?

Its EA tag places [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 in Asia. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 58.191.44.84:28015.

What Rust version is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?

Over the last 48 hours the average was 44 server fps; the floor was 26. Peak entity count: 131,240. Buildings, deployables and all else included. Check: memory. Peak use was 3,649 MB. Expect lag when fps falls and entities climb.

How reliable is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21, and is it online now?

Check: connection. [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 is offline at this moment. Last contact was 25 hours ago. Check: restart. The uptime it reports puts the last restart about 2 hours ago. Uptime for the last 7 full days: 144 of 168 hours, or 86%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 enforce, and what are its settings?

No gather rate appears in the name: [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21. Groups stop at 3 players. The label given is trio. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: plugins. It runs Oxide of them. Vanilla is the label it uses: the stock game: Facepunch's rates, kits and rules, unchanged. Anti-cheat reading: VAC on, Valve's system.

What map is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 on?

Custom map, size 3,900, on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21. Download the published file from this page.

Join

What do you do to join [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?

To join: start Rust, press F1 and type client.connect 58.191.44.84:28015. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://sorayu.me/.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode The mode is vanilla survival.
mp180
Max players 180 slots in total.
ts3
Group limit Team cap: 3.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Difficulty

^v
Vanilla The stock game: Facepunch's rates, kits and rules, unchanged.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.

Region

EA
East Asia Its browser listing: East Asia.

Other

rustmaps
Custom tag Owner or plugin definition: this tag is not a standard Rust one.

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.