StatusLive Servers online11,615 Players32,207 Populated2,774 Wiped · 3 h66 Interval5 min Date29 OCT 2026

DWG RG-S4556Server sheetchecked 12m ago

テストサーバー

Online 157.85.88.112:29581 checked 12m ago

moddedoxidepve
Connect
Players now 0/ 50 0% full
7-day average0peak 4
Rank#4,556top 20%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0123406:0015:0000:0009:0019:0004:00

Hourly average and peak, UTC.

Fig. 1Players on テストサーバー
Fig. 2

Server performance

010020030040006:0015:0000:0009:0019:0004: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 20% 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 gap5.6 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak3players, last three wipes
crowd held33%else halves by day 1

The first 48 hours of its last wipes

Wed 14 OctThu 8 OctFri 2 Oct
01234+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 4, 6 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 14 Oct, 07:09 UTC14d ago 4 – running 0
Thu 8 Oct, 16:02 UTC20d ago 4 halved by day 1 5.6 days 0
Fri 2 Oct, 03:08 UTC27d ago 1 halved by day 1 6.5 days 0
Tue 29 Sep, 04:50 UTC30d ago 3 held half 2.9 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
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 59 on average
53 / 200
02
QS『鱼山路』pve|耐玩|升级|突袭EA · groups of 8+ · 37 on average
43 / 100
03
[坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖EA · groups of 8+ · monthly · 35 on average
35 / 100
04
Japan Tokyo - Vanilla PvE|JP|BeginnerEA · groups of 16+ · 34 on average
24 / 100
05
Japan Tokyo - Chill PvE|JPEA · groups of 16+ · 21 on average
18 / 100
06
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地EA · groups of 8+ · monthly · 20 on average
19 / 88
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

What uptime is recorded for テストサーバー, and is it up?

Right now, テストサーバー is recorded as online. Counted from its reported uptime, the last restart was about 9 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. On 13 September 2026 is when Rust Graphs first saw it.

What does the recorded performance of テストサーバー show?

Average server fps over the last 48 hours is 239; the lowest was 224. Counted at its highest: 66,967 entities, buildings, deployables and the rest of the world included. 3,992 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for テストサーバー?

Asia is where the name of テストサーバー points, with no region tag published. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 157.85.88.112:29581 is its address.

What Rust version is recorded for テストサーバー?

On Linux, テストサーバー runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Population

What does the population history show for テストサーバー?

0 of 50 slots on テストサーバー are taken at the latest refresh. Averaged across seven days, the player count is 0, with a peak of 4. Over the last 48 hours the busiest hour was 05:00 UTC, at an average of 3 players.

In the rankings, which position does テストサーバー hold?

Player hours over seven days place テストサーバー at #4,556, within the top 20% of ranked servers.

Wipe data

On テストサーバー, what does the data show for wipe day?

The recent wipes averaged a busiest count of 3 players. 6 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 33% of its recent wipes. In the other cases the crowd was below half by day 1.

On テストサーバー, when do wipes occur?

テストサーバー 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. The world it runs now was made 14 days 22 hours ago.

Settings

Which settings does テストサーバー run, and what rules?

The name of テストサーバー records no gather rate. The group limit is 8 players, the game's default. pve, no fighting other players, is the game mode. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Oxide. VAC is on: that is Valve's anti-cheat.

On which map is テストサーバー played?

Seed 1 and size 3,000 define the procedural map テストサーバー generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Filters

On Rust Graphs, which lists and filters contain テストサーバー?

The Rust Graphs lists that carry テストサーバー are: Modded Rust servers and PvE Rust servers, plotted. These filters on the server list return it: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Which meaning is attached to each tag on テストサーバー?

The game's server browser reads these tags from テストサーバー: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): 50 player slots; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^p (PvE): No player combat: the threat comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

How is テストサーバー joined?

Enter client.connect 157.85.88.112:29581 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. You will find its website at https://discord.com/invite/uk2Bfmnea.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players 50 player slots.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Gameplay

^p
PvE No player combat: the threat comes from the world.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

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