StatusLive Servers online11,882 Players97,865 Populated3,914 Wiped · 3 h398 Interval5 min Date29 OCT 2026

DWG RG-S15848Server sheetchecked 21d ago

[JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]

Offline 160.251.142.144:28015 checked 21d ago

vanillaoxide
Connect
Players now 0/ 100 0% full
7-day average0peak –
Rank#15,848top 72%
Last wipe27d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

No hourly history yet.

Hourly average and peak, UTC.

Fig. 1Players on [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]
Fig. 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep25 Sep30 Sep5 Oct10 Oct15 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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 gap2.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak18players, last three wipes
crowd held67%else halves by day 4

The first 48 hours of its last wipes

Fri 2 OctTue 29 SepMon 21 Sep
010203040+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 08:37 UTC27d ago 8 – running 0
Tue 29 Sep, 11:57 UTC30d ago 24 held half 2.9 days 1
Mon 21 Sep, 07:26 UTC38d ago 23 halved by day 4 8.2 days 0
Sat 19 Sep, 01:10 UTC40d ago 14 held half 2.3 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Rustoria.co - SEA MainEA · groups of 16+ · weekly · 181 on average
414 / 450
02
Japan Tokyo - Main|10/23|JP/KR/SEA|金曜日|JumpRust.comEA · groups of 16+ · weekly · 119 on average
23 / 550
03
Rustoria.co - SEA LongEA · groups of 12+ · monthly · 102 on average
64 / 200
04
Rustafied.com - SEA MainEA · groups of 16+ · weekly · 81 on average
190 / 450
05
Rustoria.co - SEA Medium | JUST WIPED 29.10EA · no group limit · 65 on average
68 / 100
06
Japan Beginner Server - BPwipe 10/23 [JP/KR/SEA|初心者]EA · groups of 8+ · weekly · 53 on average
21 / 200
Ref.Similar
General notes

Quick answers

from the figures on this page

Server details

How reliable is [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped], and is it online now?

Last seen 21 days 2 hours ago; right now [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] is offline. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 15 September 2026 is when Rust Graphs first saw it.

What location is recorded for [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]?

Its name points to Asia, though [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] publishes no region tag. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. You will find it at 160.251.142.144:28015.

What Rust version is recorded for [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]?

On Linux, [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] runs Rust network protocol 2634 and build 166586. To join, your game must be on the same protocol; Steam handles the update.

Population

How many players are plotted on [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]?

[JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] is not responding at the latest refresh; the last record of it online is 21 days 2 hours ago.

Against other Rust servers, where is [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] placed?

Over the last seven days, [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] records #15,848 for player hours: the top 72% of all ranked servers.

Wipe times

What happens on [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] on the day of a wipe?

At their busiest, its recent wipes drew 18 players on average. At 4 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 67% of its recent wipes. In the other cases the crowd was below half by day 4.

On [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped], when do wipes occur?

[JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] wipes at times that follow no pattern, so no next wipe can be predicted. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 27 days 6 hours ago the current world was made.

Rules and settings

Which rules and settings are recorded for [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]?

The name of [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] records no gather rate. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. The server browser lists it under Community. Oxide plugins are run on it. It describes itself as vanilla, by which it means rates, kits and rules are unchanged from Facepunch's release. VAC is on: that is Valve's anti-cheat.

What is the map for [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]?

Seed 435135887 and size 3,500 define the procedural map [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] generates in game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map.

Tags

Where does [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped] appear among the Rust Graphs lists and filters?

These Rust Graphs lists include [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]: Rust community servers, plotted and Vanilla Rust servers. These filters on the server list return it: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Vanilla ^v and Oxide ^o; Group limit: 5 or more.

On [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped], what is meant by each tag?

The game's server browser reads these tags from [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2634 (Protocol): To join, your game must be on protocol 2634; cs166586 (Build): 166586 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^v (Vanilla): Rates, kits and rules are unchanged from Facepunch's release; ^o (Oxide): The plugin framework is Oxide (uMod). Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

How to join

What is the way to connect to [JP]ReiwaServer|Solo/Duo/Trio [10/2 Just wiped]?

Enter client.connect 160.251.142.144:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,^v,gmrust,cs166586,ts8,^o

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players 100 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2634
Protocol To join, your game must be on protocol 2634.
cs166586
Build 166586 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code Region code not set.

Difficulty

^v
Vanilla Rates, kits and rules are unchanged from Facepunch's release.

Mods and access

^o
Oxide The plugin framework is 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.

KeyTag string decoded