[JP/Tokyo] Solo/Duo/Trio
Online 160.251.250.21:28015 checked 11m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 7% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 8, 32 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 08:02 UTC6d ago | 8° | – | running | 1 |
| Fri 2 Oct, 11:13 UTC27d ago | 3° | held half | 20.9 days | 0 |
| Fri 25 Sep, 11:07 UTC34d ago | 4° | held half | 7 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on [JP/Tokyo] Solo/Duo/Trio?
At their busiest, its recent wipes averaged 5 players. 32 hours into the latest wipe, player numbers topped out. Above half the peak until the next wipe: that held in 100% of its recent wipes.
What is the wipe schedule on [JP/Tokyo] Solo/Duo/Trio?
Wipes come at irregular times on [JP/Tokyo] Solo/Duo/Trio, so no next wipe can be predicted. Next on Thursday 5 November at 19:00 UTC, the monthly force wipe resets every Rust server. 6 days 7 hours ago the server made the world it is on now.
Player counts
How busy is [JP/Tokyo] Solo/Duo/Trio?
The current population of [JP/Tokyo] Solo/Duo/Trio is 9, against 100 slots. A seven-day average of 4 players, with a peak of 11. Its busiest point in the last 48 hours was 14:00 UTC, averaging 8 players.
How does [JP/Tokyo] Solo/Duo/Trio rank against other Rust servers?
The top 7% of ranked servers includes [JP/Tokyo] Solo/Duo/Trio, at #1,589 for player hours over the last seven days.
Settings and rules
Which map does [JP/Tokyo] Solo/Duo/Trio run?
The map on [JP/Tokyo] Solo/Duo/Trio is procedural, size 3,500 with seed 17761776, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map.
What are the rules and settings on [JP/Tokyo] Solo/Duo/Trio?
A gather rate is not given in the name [JP/Tokyo] Solo/Duo/Trio. 8 players is the default group size, and that is the limit here. survival is the game mode, gather, build and raid in the standard game. You can fight other players and raid their bases. In the server browser it appears under Community, as a community server. Oxide plugins are in use. Anti-cheat: Valve's VAC is on.
About the server
Which version of Rust does [JP/Tokyo] Solo/Duo/Trio run?
Rust network protocol 2635 and build 168909 on Linux is what [JP/Tokyo] Solo/Duo/Trio runs. To join, your game must match the protocol; Steam handles the update.
Is [JP/Tokyo] Solo/Duo/Trio online, and how reliable is it?
Right now [JP/Tokyo] Solo/Duo/Trio shows as online. About 5 days 16 hours ago is when it last restarted, by its own uptime figure. 167 of 168 hours up over the last 7 full days, which is 99%. It first appears in Rust Heatmap records on 13 September 2026.
Where is [JP/Tokyo] Solo/Duo/Trio located?
No region tag comes from [JP/Tokyo] Solo/Duo/Trio, but its name points to Asia. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 160.251.250.21:28015 is its address.
Does [JP/Tokyo] Solo/Duo/Trio run smoothly?
Average server fps over the last 48 hours was 74; it never dropped below 53. The world held as many as 78,837 entities, buildings and deployables included. Memory use reached 4,282 MB at most. Players feel lag when fps falls and the entity count climbs.
Lists and filters
Which Rust Heatmap lists and filters include [JP/Tokyo] Solo/Duo/Trio?
The Rust Heatmap lists that [JP/Tokyo] Solo/Duo/Trio fits are: Best Rust community servers. Filtering the list by Region: Asia; Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week brings it up.
What do the server tags on [JP/Tokyo] Solo/Duo/Trio mean?
gmrust (Game mode): Rust survival, standard rules; mp100 (Max players): This server has 100 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): The game build here is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^o (Oxide): Oxide (uMod) provides the plugin framework here are the tags [JP/Tokyo] Solo/Duo/Trio publishes, and the server browser reads them. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
Connect
How do I join [JP/Tokyo] Solo/Duo/Trio?
Press F1 in Rust to open the console, then enter client.connect 160.251.250.21:28015. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you. You can find it online at https://discord.com/invite/QjJSb4U6T.