テストサーバー
Online 157.85.88.112:29581 checked 10m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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.
Rank
daily · 1 is bestTop 20% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 4, 6 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 54 / 200 |
| QS『鱼山路』pve｜耐玩｜升级｜突袭 | EA · groups of 8+ · 37 on average | 43 / 100 |
| [坚果PVE]宗门/合成/挂机/升级/召唤/副本/拍卖 | EA · groups of 8+ · monthly · 35 on average | 39 / 100 |
| Japan Tokyo - Vanilla PvE|JP|Beginner | EA · groups of 16+ · 34 on average | 22 / 100 |
| Japan Tokyo - Chill PvE|JP | EA · groups of 16+ · 21 on average | 15 / 100 |
| 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 18 / 88 |
Quick answers
from the figures on this pageWipe cycle
When does テストサーバー wipe?
The next wipe on テストサーバー cannot be predicted, because it wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The current world dates from 14 days 22 hours.
On テストサーバー, what happens on wipe day?
Across recent wipes the busiest point averaged 3 players. Peak population for the latest wipe came 6 hours after it began. Recent wipes held the crowd above half that peak until the next wipe in 33% of cases. In the other cases the crowd dropped below half by day 1.
Server
What is the hosting location of テストサーバー?
No region tag is published by テストサーバー, but the name points to Asia. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 157.85.88.112:29581.
What Rust build does テストサーバー run?
The platform is Linux, with Rust network protocol 2635 and build 168909 running on テストサーバー. Joining requires the same protocol on your game; Steam handles the update.
What uptime does テストサーバー show, and is it up?
テストサーバー reports online at the current check. The uptime it reports puts the last restart at about 8 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. The first sighting of it by Rust Server Analytics was on 13 September 2026.
Does テストサーバー perform well?
Over 48 hours the average held at 239 server fps, and the minimum was 224. At its highest the entity count was 66,967, including buildings, deployables and all else. Memory use reached 3,992 MB at peak. Lag, for players, means low fps alongside a growing entity count.
Tags
Which meanings do the tags on テストサーバー carry?
The game's server browser reads the tags テストサーバー publishes: gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): Player slots: 50; ts8 (Group limit): Team cap of 8, the stock game setting; v2635 (Protocol): To join, your game version must match protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): The region code is blank; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Modded listing, where plugins or settings change the game. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.
Where does テストサーバー appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include テストサーバー: Modded Rust servers: live data and PvE Rust servers by live population. It appears on the server list under the following filters: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
What position does テストサーバー hold in the server rankings?
On player hours over seven days, テストサーバー ranks #4,556, within the top 20% of ranked servers.
What is the population of テストサーバー?
Population at the current refresh: 0 players on テストサーバー, against 50 slots. The seven-day mean is 0 players, against a peak of 4. Across the last 48 hours, 05:00 UTC shows the highest average: 3 players.
Settings
How is テストサーバー configured, and what rules apply?
No gather rate is given in the name of テストサーバー. The default group cap of 8 players applies. pve is the game mode, no fighting other players. The Modded category lists it; plugins or settings change the game. The plugin framework is Oxide. The server runs with VAC, Valve's anti-cheat, enabled.
What is the map for テストサーバー?
テストサーバー uses a procedural map of size 3,000 with seed 1, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
How to join
How do you connect to テストサーバー?
In the Rust console (F1), enter client.connect 157.85.88.112:29581. Launch Rust on this page also works, opening Rust through Steam and connecting you. Find it online at https://discord.com/invite/uk2Bfmnea.