Open every day, at every hour Admission free 11,694 servers and 49,675 players on view The records renewed every five minutes
Rust Server HistoryMuseum and archive of Rust servers

The server's own banner, as it publishes it

Exhibit no. 1,563Acc. 2026.1563

[JP/Tokyo] Solo/Duo/Trio

Rust server · in the archive since 13 September 2026

Online 160.251.250.21:28015 checked 13m ago

oxide
To visit
Players now 3/ 100
3% full
7-day average4peak 11
Rank#1,563top 7%
Last wipe6d agoFri 23 Oct, 08:02 UTC · no schedule published
Next wipe–no rhythm it keeps

The timeline

Wipes

Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.

a wipe on recordthe monthly force wipeexpectednow, 30 Oct 2026, 02:10 UTCAll times UTC.

The record of each wipe

  1. Fri 23 Oct 202608:02 UTC6d ago
    Peak
    8
    Crowd
    –
    Lasted
    running
    Players before
    1
  2. Fri 2 Oct 202611:13 UTC27d ago
    Peak
    3
    Crowd
    held half
    Lasted
    20.9 days
    Players before
    0
  3. Fri 25 Sep 202611:07 UTC34d ago
    Peak
    4
    Crowd
    held half
    Lasted
    7 days
    Players before
    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.

The rhythm

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.

13.9 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
5wipe-day peakplayers, last three wipes
100%crowd heldof 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.

The record

Population, performance and rank

Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.

Folder 1

Players

AveragePeak
02.557.51003:0012:0022:0007:0016:0001:00

Hourly average and peak, UTC.

Folder 2

Server performance

025507510003:0012:0022:0007:0016:0001: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.

Folder 3

Rank

RankRank in region
11k2k3k4k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

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

Related exhibits

Similar servers

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

Visitors' questions about this exhibit

Quick answers

Answered from the figures on this page.

Tags, lists

What do the server tags on [JP/Tokyo] Solo/Duo/Trio mean?

These tags from [JP/Tokyo] Solo/Duo/Trio, read by the game's server browser, are: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): 100 slots are set on this server; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): The server runs game protocol 2635; matching it is required to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles the network layer, as standard for the game; $r? (Region code): The server has no region code; ^o (Oxide): Plugins run through Oxide (uMod). At the top of this page you also see the current players, the queue and when the world was made, all from the tags.

Which Rust Server History lists and filters include [JP/Tokyo] Solo/Duo/Trio?

These Rust Server History lists include [JP/Tokyo] Solo/Duo/Trio: Rust community servers. 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.

The record

Does [JP/Tokyo] Solo/Duo/Trio run smoothly?

Across the last 48 hours it averaged 71 server fps; the low was 50. Buildings, deployables and everything else in the world came to as many as 78,837 entities. Up to 4,282 MB of memory was used. What players feel as lag comes from low fps and a climbing entity count.

Which version of Rust does [JP/Tokyo] Solo/Duo/Trio run?

The recorded build for [JP/Tokyo] Solo/Duo/Trio is Rust network protocol 2635 and build 168909 on Linux. The protocol must match to join, and Steam handles that update.

Is [JP/Tokyo] Solo/Duo/Trio online, and how reliable is it?

[JP/Tokyo] Solo/Duo/Trio is listed as online now. About 6 days 3 hours ago is when it last restarted, judged by the uptime it reports. It was up for 167 of 168 hours in the last 7 full days, 99% of the time. First seen by Rust Server History on 13 September 2026.

Where is [JP/Tokyo] Solo/Duo/Trio located?

Its name points to Asia, though [JP/Tokyo] Solo/Duo/Trio publishes no region tag. Where a server says it is is shown on Rust Server History; where the machine stands is not looked up. Its entry gives 160.251.250.21:28015 as the address.

Wipe record

What does wipe day look like on [JP/Tokyo] Solo/Duo/Trio?

5 players on average was the busiest its recent wipes drew. On the latest wipe, 32 hours after the wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.

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

There is no next wipe to predict on [JP/Tokyo] Solo/Duo/Trio, which wipes at irregular times. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, when every Rust server wipes. Made 6 days 18 hours ago, the current world is what it runs now.

Player record

How does [JP/Tokyo] Solo/Duo/Trio rank against other Rust servers?

Player hours over the last seven days put [JP/Tokyo] Solo/Duo/Trio at #1,563: a place in the top 7% of all ranked servers.

How busy is [JP/Tokyo] Solo/Duo/Trio?

3 players are on [JP/Tokyo] Solo/Duo/Trio at present, from 100 slots. Stored history gives a seven-day average of 4 players and a peak of 11. An average of 9 players at 15:00 UTC made that the busiest hour of the last 48.

Map and rules

What are the rules and settings on [JP/Tokyo] Solo/Duo/Trio?

You will not find a gather rate in the name of [JP/Tokyo] Solo/Duo/Trio. No group may exceed 8 players, the default set by the game. survival is the game mode, gather, build, raid: the standard game. Fighting and raiding between players are permitted. Under Community in the server browser, this community server is listed. Plugins in use: Oxide. The anti-cheat VAC from Valve is active.

Which map does [JP/Tokyo] Solo/Duo/Trio run?

Generated by the game at size 3,500 with seed 17761776, the map on [JP/Tokyo] Solo/Duo/Trio is procedural. One size and seed produce one map, which RustMaps can show you from this page.

How to join

How do I join [JP/Tokyo] Solo/Duo/Trio?

Entering client.connect 160.251.250.21:28015 in the console (F1) connects you to this server. The Launch Rust button on this page does the same: it opens the game via Steam and connects on your behalf. You will find its website at https://discord.com/invite/QjJSb4U6T.

The label explained

Server tags

What each tag this server publishes means.

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp100
Max players 100 slots are set on this server.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol The server runs game protocol 2635; matching it is required to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet handles the network layer, as standard for the game.
$r?
Region code The server has no region code.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).

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.