DWG RG-S0633Server sheetchecked 1d ago
[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21
Offline EA 58.191.44.84:28015 checked 1d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 3% of all ranked servers, top 5% in EA, and #61 of the trio servers (top 10%). Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Wednesday 4 November, 02:46 UTC, in 5d 17h. Every Wednesday at 02:46 UTC · high confidence
Coming wipes
- 5d 17hWed 4 Nov, 02:46 UTC
- 7d 10hThu 5 Nov, 19:00 UTCFW
- 12d 17hWed 11 Nov, 02:46 UTC
- 19d 17hWed 18 Nov, 02:46 UTC
- 26d 17hWed 25 Nov, 02:46 UTC
- 33d 17hWed 2 Dec, 02:46 UTC
- 35d 10hThu 3 Dec, 19:00 UTCFW
- 40d 17hWed 9 Dec, 02:46 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 178, 11 hours in, with 32 in the queue.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 21 Oct, 02:46 UTC8d ago | 178+32 queue | – | running | 0 |
| Wed 14 Oct, 02:46 UTC15d ago | 179+31 queue | halved by day 2 | 7 days | 0 |
| Wed 7 Oct, 02:46 UTC22d ago | 178+35 queue | halved by day 3 | 7 days | 0 |
| Fri 2 Oct, 02:45 UTC27d 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 UTC36d ago | 180+36 queue | halved by day 4 | 8.7 days | 2 |
| Wed 16 Sep, 01:35 UTC43d 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.
Similar servers
Quick answers
Recorded details
How reliable is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21, and is it online now?
Last seen 32 hours ago; right now [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 is offline. About 2 hours ago is when it last restarted, measured from the uptime it reports. 144 of 168 hours up over the last 7 full days, which is 86% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
Is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 stable in the figures recorded?
Average server fps over the last 48 hours is 43; the lowest was 26. Counted at its highest: 126,597 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,649 MB. A climbing entity count and low fps are the source of what players feel as lag.
In which location is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 hosted?
With its EA tag, [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 lists itself in Asia. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 58.191.44.84:28015.
What Rust version is recorded for [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?
The platform is Linux and the version is Rust network protocol 2635 and build 168909 on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21. To join, your game must be on the same protocol; Steam handles the update.
Population
What does the population history show for [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?
The latest refresh records [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 as offline, last seen 32 hours ago. Averaged across seven days, the player count is 28, with a peak of 158. Averaged over the last 48 hours, the player count is highest at 12:00 UTC: 5 players.
Against other Rust servers, where is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 placed?
The same seven-day player-hour count places [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 at #28 within Asia, #633 across all ranked servers and in the top 3% of them. Within the trio group it places #61.
Wipe times
On [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21, what does the data show for wipe day?
The recent wipes averaged a busiest count of 178 players. 11 hours after the latest wipe the crowd peaked, with 32 further players waiting in the queue. The crowd stayed above half the peak until the next wipe in 0% of its recent wipes. On the wipes where it did not hold, the crowd dropped below half by day 3.
On [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21, when do wipes occur?
The wipe rhythm at [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 is every Wednesday at 02:46 UTC. Wednesday 4 November at 02:46 UTC is the date its next wipe is due. 8 days 6 hours ago the current world was made. A wipe every week is the schedule its tags set out.
Map and rules
Which rules and settings are recorded for [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?
No gather rate is stated in the name of [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21. A group tops out at 3 players (trio). It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. It appears under Community in the server browser. Oxide plugins are run on it. It describes itself as vanilla, by which it means no changed rates, kits or rules: the game as Facepunch ships it. VAC is on: that is Valve's anti-cheat.
What is the map for [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?
Size 3,900, custom, on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21: the map file is published and can be downloaded from this page.
Tags
Where does [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 are: Rust community servers, plotted, Trio Rust servers, plotted live and Vanilla Rust servers. It is returned by these filters 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.
Which meaning is attached to each tag on [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?
The game's server browser reads these tags from [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21: gmvanilla (Game mode): The mode is vanilla survival; mp180 (Max players): Slots: 180; ts3 (Group limit): Team size is capped at 3; v2635 (Protocol): Your game must match protocol 2635 to join; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^w (Weekly): The wipe cycle is one week; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): The browser's listing places it under East Asia; rustmaps (Custom tag): The owner or a plugin set this tag; it is not standard Rust. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Which operator runs [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21?
[JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 publishes a sorayu.me hostname. 2 other servers we track publish one too, so the same operator most likely runs them.
Connect
How is [JP/Tokyo] SORAYU.ME - Solo/Duo/Trio|PVP|Wed/水曜日|10/21 joined?
In Rust, press F1 and type client.connect 58.191.44.84:28015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://sorayu.me/ is its website.
Server tags
Published as mp180,ptrak,$r?,v2635,^w,^v,EA,gmvanilla,cs168909,ts3,^o,rustmaps
Game
gmvanilla
mp180
ts3
v2635
cs168909
ptrak
$r?
Wipe schedule
^w
Difficulty
^v
Mods and access
^o
Region
EA
Other
rustmaps
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.