Online 160.251.250.21:28015 checked 10m ago
[JP/Tokyo] Solo/Duo/Trio
Connect
srv = rust.server("160.251.250.21:28017")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 7% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its 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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 08:02 UTC6d ago | 8 | NaN | running | 1 |
| 1 | Fri 2 Oct, 11:13 UTC27d ago | 3 | held half | 20.9 days | 0 |
| 2 | 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.
display(srv.map, srv.info())Map
3500 · seed 17761776![Map of [JP/Tokyo] Solo/Duo/Trio](https://files.facepunch.com/rust/map-images/faaaa8c0f6ac4bfa60216af0089efaa19a7d7ddc530740d49077af1afb7e1e0e/proceduralmap.3500.1792742526773.289_faaaa8c0f6ac4bfa60216af0089efaa1.jpg)
- map
- Procedural Map
- size
- 3500
- seed
- 17761776
Server
srv.info()- address
- 160.251.250.21:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 08:02 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rustoria.co - SEA Main | EA · groups of 16+ · weekly · 181 on average | 140/200 |
| 1 | Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.com | EA · groups of 16+ · weekly · 119 on average | 1/550 |
| 2 | Rustoria.co - SEA Long | EA · groups of 12+ · monthly · 100 on average | 28/200 |
| 3 | Rustafied.com - SEA Main | EA · groups of 16+ · weekly · 79 on average | 48/100 |
| 4 | Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者] | EA · groups of 8+ · weekly · 54 on average | 0/200 |
| 5 | [ASIA] Siam Rust | Vanilla | Weekly | EA · groups of 8+ · weekly · 38 on average | 28/150 |
Quick answers
From the figures on this page.
Population data
What position does [JP/Tokyo] Solo/Duo/Trio take in the server rankings?
Player hours over seven days put [JP/Tokyo] Solo/Duo/Trio at #1,561, in the top 7% of the ranked set.
What population does [JP/Tokyo] Solo/Duo/Trio carry?
The sample now reads 3 players for [JP/Tokyo] Solo/Duo/Trio, out of 100 slots. Over the last seven days it averaged 4 players and peaked at 11. Averaged by hour over 48 hours, 15:00 UTC is the busiest, at 9 players.
Server data
How well does [JP/Tokyo] Solo/Duo/Trio perform?
The 48-hour average is 71 server fps, with a low of 50. Entity numbers reached 78,837, and that includes buildings, deployables and the rest. A high of 4,282 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
What Rust version does [JP/Tokyo] Solo/Duo/Trio run?
Rust network protocol 2635 and build 168909 on Linux is what [JP/Tokyo] Solo/Duo/Trio runs. Steam updates your game for you, but the protocol must match to join.
How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it online now?
The current sample puts [JP/Tokyo] Solo/Duo/Trio online. Count back 6 days from its reported uptime to get the last restart. 167 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
In which location is [JP/Tokyo] Solo/Duo/Trio hosted?
The name of [JP/Tokyo] Solo/Duo/Trio points to Asia, even though no region tag is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 160.251.250.21:28015.
Settings and map
Which rules apply on [JP/Tokyo] Solo/Duo/Trio, and what settings?
You will not find a gather rate in the string [JP/Tokyo] Solo/Duo/Trio. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has [JP/Tokyo] Solo/Duo/Trio loaded?
Size 3,500, seed 17761776: the procedural map on [JP/Tokyo] Solo/Duo/Trio, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipes and dates
On what schedule does [JP/Tokyo] Solo/Duo/Trio wipe?
No next wipe can be predicted for [JP/Tokyo] Solo/Duo/Trio, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 6 days 15 hours ago.
What is wipe day on [JP/Tokyo] Solo/Duo/Trio like?
Across recent wipes the busiest point averaged 5 players. 32 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Which Rust Data filters and lists contain [JP/Tokyo] Solo/Duo/Trio?
On Rust Data, [JP/Tokyo] Solo/Duo/Trio appears in these lists: Rust community servers, unfiltered. It appears under these filters on the server list: 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.
Which meanings do the tags on [JP/Tokyo] Solo/Duo/Trio hold?
Read by the game's server browser, the tags [JP/Tokyo] Solo/Duo/Trio publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): 100 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into [JP/Tokyo] Solo/Duo/Trio?
The manual route: launch Rust, F1, then client.connect 160.251.250.21:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://discord.com/invite/QjJSb4U6T is the website recorded for it.