Rust Server TrendsSeismic network · station log
Recording Stations11,824 Players75,694 Active3,728 Wipes · 3 h230 48 h

Station XX-4333 · recording

テストサーバー

Online 157.85.88.112:29581 checked 10m ago

moddedoxidepve
Connect
Players now
2/ 50
4% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 4
Rank
#4,333
top 19%
Last wipe
15d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-4333 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
2of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+2into Wed 04:00 UTC
Peak · 48 h
4most players in any hour
Channel 1 · calibrated

Players

AveragePeak
0123415:0000:0009:0017:0003:0012:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

010020030040015:0000:0009:0017:0003:0012: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.

Channel 3 · rank movement

Rank

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

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

Expected events

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
5.6 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
33%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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 14 Oct, 07:09 UTC15d ago M0.6rising 4 – running 0
Thu 8 Oct, 16:02 UTC20d ago M0.6rising 4 halved by day 1 5.6 days 0
Fri 2 Oct, 03:08 UTC27d ago M0.0rising 1 halved by day 1 6.5 days 0
Tue 29 Sep, 04:50 UTC30d ago M0.5rising 3 held half 2.9 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 58 on average
99/ 200
QS『鱼山路』pve|耐玩|升级|突袭 EA · groups of 8+ · 37 on average
8/ 100
[坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱 EA · groups of 8+ · monthly · 35 on average
39/ 100
Japan Tokyo - Vanilla PvE|JP|Beginner EA · groups of 16+ · 33 on average
66/ 100
Japan Tokyo - Chill PvE|JP EA · groups of 16+ · 21 on average
30/ 100
爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 EA · groups of 8+ · monthly · 20 on average
20/ 88
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on テストサーバー?

テストサーバー runs a procedural map of size 3,000 with seed 1, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on テストサーバー?

You will find no gather rate in the name of テストサーバー. Groups hold up to 8 players, which is the default for the game. It plays in pve mode, no player-versus-player fighting. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Live population

What is the current population on テストサーバー?

A reading taken now shows 2 players on テストサーバー, which has 50 slots. The seven-day average is 0 players, with a peak of 4. The last 48 hours show their highest activity at 08:00 UTC, averaging 3 players.

How does テストサーバー rank against other Rust servers?

Over the last seven days, テストサーバー recorded enough player hours to reach #4,333 worldwide, placing it in the top 19% of all ranked servers.

Operator and location

How reliably does テストサーバー stay online?

テストサーバー is up at the moment. The uptime it reports puts its last restart about 5 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.

Does テストサーバー hold a steady tick rate?

Its average server fps over the last 48 hours was 238, and it never dropped below 224. At its highest, it carried 66,967 entities: buildings, deployables and the world's other contents. It reached a ceiling of 4,075 MB of memory. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Where in the world is テストサーバー hosted?

Its name points to Asia, but テストサーバー publishes no region tag. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 157.85.88.112:29581.

What build of Rust does テストサーバー use?

テストサーバー is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on テストサーバー?

The recent wipes averaged a busiest count of 3 players. 6 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 33% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.

On what timetable does テストサーバー run its wipes?

There is no next wipe to predict at テストサーバー, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 15 days 6 hours.

Tags

What do the server tags on テストサーバー mean?

The game's server browser reads the tags テストサーバー publishes: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does テストサーバー appear?

These Rust Server Trends lists include テストサーバー: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Connecting

What steps get you onto テストサーバー?

You can connect by pressing F1 in Rust and typing client.connect 157.85.88.112:29581 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. https://discord.com/invite/uk2Bfmnea is where its website lives.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build It runs game build 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code A region code has not been set.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under 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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.