Rust Server IndexCard catalogue of Rust servers

Holdings11,854 servers99,188 players532 fresh wipes

Call no.1561 On the shelf · online

[JP/Tokyo] Solo/Duo/Trio

Online 160.251.250.21:28015 checked 11m ago

Subjects 1. oxide
Players now
1/ 100
1% full
7-day average
4
peak 11
Rank
#1,561
top 7%
Last wipeWiped23 OCT2026 · 6d 12h ago
6d ago · no schedule published
Next wipe
–
no rhythm it keeps
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
02.557.51021:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

025507510021:0006:0015:0001:0010:0019:00

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 7% of all ranked servers. Ranked on player hours over the last seven days.

Record sheet D · loan terms

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap
13.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
5players, last three wipes
crowd held
100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 23 OctFri 2 OctFri 25 Sep
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 8, 32 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
23 OCT 2026Fri 23 Oct, 08:02 UTC6d ago
8 – running 1
2 OCT 2026Fri 2 Oct, 11:13 UTC27d ago
3 held half 20.9 days 0
25 SEP 2026Fri 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EA
Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average
237/ 300
EA
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average
5/ 550
EA
Rustoria.co - SEA LongEA · groups of 12+ · monthly · 101 on average
50/ 200
EA
Rustafied.com - SEA MainEA · groups of 16+ · weekly · 80 on average
112/ 250
EA
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 54 on average
2/ 200
EA
[ASIA] Siam Rust | Vanilla | WeeklyEA · groups of 8+ · weekly · 38 on average
50/ 180
Reference desk

Quick answers

From the figures on this page.

Map and rules

Where can you read the rules and settings that apply on [JP/Tokyo] Solo/Duo/Trio?

No gather rate appears in the name [JP/Tokyo] Solo/Duo/Trio. The default group limit of 8 players applies. The server runs survival, gather, build and raid: the standard game. PvP and raiding are allowed. Filed under Community in the server browser, it is a community server. Filed under plugins: Oxide. VAC is on: Valve's anti-cheat is enabled.

What is the map on [JP/Tokyo] Solo/Duo/Trio?

Size 3,500, seed 17761776: the game generates the procedural map on [JP/Tokyo] Solo/Duo/Trio. The map can be seen on RustMaps from this page, because the same size and seed give the same map.

Tags

Where does [JP/Tokyo] Solo/Duo/Trio appear among the Rust Server Index lists and filters?

These lists on Rust Server Index take [JP/Tokyo] Solo/Duo/Trio: Community Rust servers, indexed. Filed 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.

What is meant by the tags on [JP/Tokyo] Solo/Duo/Trio?

Filed under these tags, as published by [JP/Tokyo] Solo/Duo/Trio and read by the game's server browser: gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): The queue ceiling sits at 100; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs168909 (Build): The game build here is 168909; ptrak (Networking): RakNet is the network layer, as standard for Rust; $r? (Region code): No region code has been set; ^o (Oxide): This server uses Oxide (uMod) for plugins. See also the top of this page, where the tags carry the current players, the queue and the time the world was made.

Wipes and resets

What should you expect on [JP/Tokyo] Solo/Duo/Trio when wipe day comes?

The average peak across its recent wipes is 5 players. 32 hours into the latest wipe, the crowd reached its peak. The crowd held above half the peak until the next wipe in 100% of its recent wipes.

Which wipe timetable does [JP/Tokyo] Solo/Duo/Trio follow?

No next wipe can be predicted for [JP/Tokyo] Solo/Duo/Trio: its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives, and every Rust server wipes with it. The world it runs now was made 6 days 12 hours.

Population

Where does [JP/Tokyo] Solo/Duo/Trio sit in the rankings?

Filed under rankings: #1,561 for [JP/Tokyo] Solo/Duo/Trio on seven-day player hours, top 7% overall.

How many players are on [JP/Tokyo] Solo/Duo/Trio at the moment?

[JP/Tokyo] Solo/Duo/Trio is currently showing 1 players on 100 slots. Filed under seven-day figures: an average of 4 players and a peak of 11. Filed under busiest hour: 15:00 UTC in the last 48 hours, averaging 9 players.

Server facts

Which Rust build is [JP/Tokyo] Solo/Duo/Trio running?

Rust network protocol 2635 and build 168909 on Linux is what you will find on [JP/Tokyo] Solo/Duo/Trio. The protocol must match before you can join, and Steam takes care of updating it.

How reliable is [JP/Tokyo] Solo/Duo/Trio, and is it online now?

Right now [JP/Tokyo] Solo/Duo/Trio is up and running. The uptime it reports puts the last restart at about 5 days 21 hours ago. Uptime for the last 7 full days came to 99%, 167 hours out of 168. The earliest sighting at Rust Server Index is 13 September 2026.

What is performance like on [JP/Tokyo] Solo/Duo/Trio?

The last 48 hours give an average of 73 server fps and a floor of 53. Buildings, deployables and everything else in the world came to as many as 78,837 entities. The peak memory figure stood at 4,282 MB. Lag, to players, is low fps and an entity count that climbs.

What is the location of [JP/Tokyo] Solo/Duo/Trio?

The name of [JP/Tokyo] Solo/Duo/Trio points to Asia, though no region tag is published. Rust Server Index takes the server's word for its location and does not look up the machine's position. You will reach it at 160.251.250.21:28015.

How to join

How can you connect to [JP/Tokyo] Solo/Duo/Trio?

If you would rather use the console, press F1 in Rust and enter client.connect 160.251.250.21:28015. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you. The website can be found at https://discord.com/invite/QjJSb4U6T.

Subject headings explained

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Survival on standard Rust rules.
mp100
Max players The queue ceiling sits at 100.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs168909
Build The game build here is 168909.
ptrak
Networking RakNet is the network layer, as standard for Rust.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.

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.