テストサーバー
Online 157.85.88.112:29581 checked 14m ago
Server instruments
last reading Thu 14:00 UTCPlayers now
2% full 7-day avg7-day peakServer fps
48 h low 224 · below 20 is lag, below 10 is badEntities
48 h range 58,259–66,967 · memory 3,445 MBUptime
7 h 0 min since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 19% 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 UTC15d ago | 4 | – | running | 0 |
| Thu 8 Oct, 16:02 UTC21d 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- 68/200
- 36/100
- 32/100
- 50/100
- 15/100
- 17/88
Quick answers
from the figures on this pageReset cycle
What happens on テストサーバー when wipe day comes?
An average of 3 players came at the busiest on its recent wipes. 6 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 33% of its recent wipes. By day 1 it fell below half when it didn't.
How often does テストサーバー wipe, and when?
There is no next wipe to predict: テストサーバー wipes at irregular times. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 15 days 9 hours ago.
Tag meanings
Which tags does テストサーバー carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server from テストサーバー. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does テストサーバー appear in Rust Metrics lists and filters?
Rust Metrics lists featuring テストサーバー: Modded Rust servers, checked live and Rust PvE servers. Check: filters. On the server list it appears under these: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
Where does テストサーバー sit in the rankings?
Ranking for テストサーバー: #4,283 on seven-day player hours, top 19% of all ranked servers.
What is the population on テストサーバー?
Current headcount on テストサーバー: 1 players, 50 slots available. Seven-day check: 0 players on average. Peak reading: 4. The last 48 hours peaked at 08:00 UTC, averaging 3 players at that hour.
Operator and location
Which location does テストサーバー run from?
Reading: location. Nothing in the tags, but the name of テストサーバー points to Asia. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 157.85.88.112:29581.
What Rust version is テストサーバー on?
Reading: テストサーバー, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
How does テストサーバー perform?
Reading: 238 server fps on average across the last 48 hours. It never dropped below 224. Peak entity count: 66,967. Buildings, deployables and all else included. Reading: 4,075 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on テストサーバー, and is it online?
テストサーバー reports online. Status: normal. By its reported uptime, the last restart was roughly 7 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
What settings and rules apply on テストサーバー?
Check: gather rate. The name テストサーバー does not state one. 8 players per group, the default value. pve, fighting between players is off — that is the game mode. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on テストサーバー?
From seed 1, the game generates the procedural map on テストサーバー. Its size is 3,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
How to join
How can you get onto テストサーバー?
Check: join. Open Rust, press F1, then enter client.connect 157.85.88.112:29581. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/uk2Bfmnea is where its website sits.