[JP/Tokyo] Solo/Duo/Trio
160.251.250.21:28015 checked 8m 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
daily · 1 is bestTop 9% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. 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 3, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 11:13 UTC12d ago | 3 | – | running | 0 |
| Fri 25 Sep, 11:07 UTC19d 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
Rules and settings
What is the setup on [JP/Tokyo] Solo/Duo/Trio when it comes to rules and settings?
You will not find a gather rate in the name [JP/Tokyo] Solo/Duo/Trio. The group cap is 8 players, the default for the game. It runs survival, gather, build and raid: the standard game. You can fight and raid other players here. The server browser lists it under Community. VAC, Valve's anti-cheat, is switched on.
Which map is active on [JP/Tokyo] Solo/Duo/Trio?
Size 3,500, seed 714728274, generated by the game: the procedural map on [JP/Tokyo] Solo/Duo/Trio. From this page, RustMaps can show it: size and seed produce the same map each time.
Server population
What is the population like on [JP/Tokyo] Solo/Duo/Trio?
Right now, 1 players are on [JP/Tokyo] Solo/Duo/Trio, which has 100 slots. The seven-day average is 3 players, with a peak of 7. The highest average over the last 48 hours came at 13:00 UTC, with 4 players.
What is [JP/Tokyo] Solo/Duo/Trio's ranking?
For player hours over the last week, [JP/Tokyo] Solo/Duo/Trio is #2,070, which puts it in the top 9% of all ranked servers.
Server tags
What is the meaning of the tags on [JP/Tokyo] Solo/Duo/Trio?
What the game's server browser gets from [JP/Tokyo] Solo/Duo/Trio is this tag list: gmrust (Game mode): Survival in the standard Rust mode; mp100 (Max players): It holds 100 players; ts8 (Group limit): This uses the standard team limit of 8; v2634 (Protocol): You'll need protocol 2634 on your game to join; cs166652 (Build): It runs build 166652; ptrak (Networking): The network layer is RakNet, which is standard; $r? (Region code): There's no region code here. Also in the tags: its players now, its queue and the time its world was made, and the top of this page shows them.
Which Rust Zerg Life filters and lists cover [JP/Tokyo] Solo/Duo/Trio?
Rust community servers for clans: that is where you will find [JP/Tokyo] Solo/Duo/Trio among the Rust Zerg Life rankings. These filters bring it up 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.
About the server
Is [JP/Tokyo] Solo/Duo/Trio currently online and stable?
Right now, [JP/Tokyo] Solo/Duo/Trio is online. The uptime figure it gives suggests it restarted around 10 days 13 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. Rust Zerg Life has been tracking it since 13 September 2026.
Is [JP/Tokyo] Solo/Duo/Trio smooth to play on?
Over the past 48 hours, server fps averaged 79 and never dropped below 58. The world held as many as 74,529 entities, including buildings, deployables and everything else. Memory use peaked at 4,019 MB. Lag, as players feel it, is caused by low fps and an increasing number of entities.
What version is [JP/Tokyo] Solo/Duo/Trio using?
On Linux, [JP/Tokyo] Solo/Duo/Trio runs Rust network protocol 2634 and build 166652. You can only join if your game uses the same protocol, and Steam takes care of updating it.
Where can you find [JP/Tokyo] Solo/Duo/Trio?
No region tag comes from [JP/Tokyo] Solo/Duo/Trio, but its name points to Asia. Rust Zerg Life displays the location a server claims, not where the machine actually stands. Connect to it at 160.251.250.21:28015.
Wipe schedule
What can you expect on wipe day on [JP/Tokyo] Solo/Duo/Trio?
At their busiest, its recent wipes drew an average of 4 players. On the latest wipe, 1 hours after the wipe, the crowd hit its peak. The crowd kept above half that peak until the next wipe in 100% of its recent wipes.
How often does [JP/Tokyo] Solo/Duo/Trio wipe, and on what days?
So few of [JP/Tokyo] Solo/Duo/Trio's wipes are recorded that its rhythm cannot be told yet. Next on Thursday 5 November at 19:00 UTC: the monthly force wipe that every Rust server gets. The world it is running now dates from 12 days 17 hours ago.
Connect
What steps do I take to join [JP/Tokyo] Solo/Duo/Trio?
You can join by opening the console with F1 and typing client.connect 160.251.250.21:28015. Or hit Launch Rust on this page to open Rust through Steam and connect. For more, visit its website: https://discord.com/invite/QjJSb4U6T.
Server tags
Published as mp100,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
mp100
ts8
v2634
cs166652
ptrak
$r?
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.
