[JP/Tokyo] Solo/Duo/Trio
160.251.250.21:28015 checked 9m 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 9% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 7 days between real wipes
- wipe-day peak
- 4 players, last three wipes
- crowd held
- 100% of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 1 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 11:13 UTC 12d ago | 3 | – | running | 0 |
| Fri 25 Sep, 11:07 UTC 19d 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.
Similar servers
Quick answers
Player Numbers
Where does [JP/Tokyo] Solo/Duo/Trio sit in the rankings?
In the top 9% of all ranked servers, [JP/Tokyo] Solo/Duo/Trio is #2,065 on player hours for the last seven days.
How many players are on [JP/Tokyo] Solo/Duo/Trio?
2 of 100 slots are filled on [JP/Tokyo] Solo/Duo/Trio at the moment. The average player count over the last seven days is 3, with a peak of 7. The busiest time in the last 48 hours was 13:00 UTC, when the average player count was 4.
Tags and Filters
What is the meaning of the tags on [JP/Tokyo] Solo/Duo/Trio?
For [JP/Tokyo] Solo/Duo/Trio, the game's server browser reads the following tags: gmrust (Game mode): Survival as standard in Rust; mp100 (Max players): Slot count is 100; ts8 (Group limit): Default team size: 8; v2634 (Protocol): Game protocol 2634; the same version is required to join; cs166652 (Build): Game build number: 166652; ptrak (Networking): RakNet is the network layer in use; $r? (Region code): No region code listed. The top of this page also shows its current players, its queue and the time its world was made, all from the tags.
Where does [JP/Tokyo] Solo/Duo/Trio appear in BestRustServers.xyz lists and filters?
These BestRustServers.xyz lists include [JP/Tokyo] Solo/Duo/Trio: Rust community servers, ranked. It appears under these filters on the server list: Region: Asia; Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server Details
What Rust version is [JP/Tokyo] Solo/Duo/Trio on?
On Linux, [JP/Tokyo] Solo/Duo/Trio runs Rust network protocol 2634 and build 166652. Joining requires the same protocol; Steam updates your game for you.
How smooth is the performance on [JP/Tokyo] Solo/Duo/Trio?
Over 48 hours, it averaged 81 server fps; the lowest was 61. It held up to 74,570 entities: everything from buildings to deployables in the world. Memory use peaked at 4,019 MB. What players experience as lag is low fps combined with a rising entity count.
[JP/Tokyo] Solo/Duo/Trio uptime and reliability: what are they?
At the moment, [JP/Tokyo] Solo/Duo/Trio is up. According to its reported uptime, the last restart was about 10 days 5 hours ago. It was up 100% of the time over the last 7 full days, 168 of 168 hours. It was first seen by BestRustServers.xyz on 13 September 2026.
[JP/Tokyo] Solo/Duo/Trio location: where is it?
Without a region tag, [JP/Tokyo] Solo/Duo/Trio's name points to Asia. BestRustServers.xyz shows the stated location of a server; the actual location of the machine is not looked up. You can reach it at 160.251.250.21:28015.
Rules & Map
Which map is used on [JP/Tokyo] Solo/Duo/Trio?
On [JP/Tokyo] Solo/Duo/Trio, the map is procedural, size 3,500 with seed 714728274, generated by the game. The map can be viewed on RustMaps from this page, since size and seed fix it.
[JP/Tokyo] Solo/Duo/Trio rules and settings: what are they?
A gather rate is not given in the name [JP/Tokyo] Solo/Duo/Trio. No group limit is stated; the game's default of 8 players applies. It runs survival, gather, build, raid: the standard game. Raids and PvP are on. Community is its browser category. VAC: on.
Wipe Cycle
On what schedule does [JP/Tokyo] Solo/Duo/Trio wipe?
The record holds too few wipes for [JP/Tokyo] Solo/Duo/Trio to show a rhythm. The monthly force wipe applies to every Rust server, and the next is on Thursday 5 November at 19:00 UTC. The current world has been running since 12 days 9 hours.
What happens on wipe day on [JP/Tokyo] Solo/Duo/Trio?
An average peak of 4 players was drawn by its recent wipes. 1 hours into the latest wipe, the crowd reached its peak. Half the peak was held until the next wipe in 100% of its recent wipes.
Connect
What is the process to join [JP/Tokyo] Solo/Duo/Trio?
Use the F1 console: client.connect 160.251.250.21:28015. Launch Rust on this page does the same by opening Rust through Steam and connecting. https://discord.com/invite/QjJSb4U6T is its website.
Server tags
Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust- Game mode Survival as standard in Rust.
mp100- Max players Slot count is 100.
ts8- Group limit Default team size: 8.
v2634- Protocol Game protocol 2634; the same version is required to join.
cs166652- Build Game build number: 166652.
ptrak- Networking RakNet is the network layer in use.
$r?- Region code No region code listed.
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.