Online 157.85.88.112:29581 checked 10m ago
テストサーバー
Connect
srv = rust.server("157.85.88.112:29582")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 19% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its 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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 14 Oct, 07:09 UTC15d ago | 4 | NaN | running | 0 |
| 1 | Thu 8 Oct, 16:02 UTC21d ago | 4 | halved by day 1 | 5.6 days | 0 |
| 2 | Fri 2 Oct, 03:08 UTC27d ago | 1 | halved by day 1 | 6.5 days | 0 |
| 3 | 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.
display(srv.map, srv.info())
Map
3000 · seed 1
- map
- Procedural Map
- size
- 3000
- seed
- 1
Server
srv.info()- address
- 157.85.88.112:29581
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 14 Oct 2026, 07:09 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 59 on average | 30/200 |
| 1 | QS『鱼山路』pve|耐玩|升级|突袭 | EA · groups of 8+ · 37 on average | 36/100 |
| 2 | [坚果PVE]宗门师徒/死亡不掉/技能强化/养殖钓鱼 | EA · groups of 8+ · monthly · 34 on average | 32/100 |
| 3 | Japan Tokyo - Vanilla PvE|JP|Beginner | EA · groups of 16+ · 33 on average | 18/100 |
| 4 | Japan Tokyo - Chill PvE|JP | EA · groups of 16+ · 21 on average | 11/100 |
| 5 | 爱酱PVE|1服|十倍|死亡不掉|装备强化|突袭基地 | EA · groups of 8+ · monthly · 20 on average | 16/88 |
Quick answers
From the figures on this page.
Population data
How does テストサーバー compare in the rankings?
Over the last seven days テストサーバー sits at #4,236 on player hours, in the top 19% of ranked servers.
What population does テストサーバー carry?
Current row: 0 players on テストサーバー, against 50 slots. Over the last seven days it averaged 0 players and peaked at 4. The 48-hour sample puts the busiest hour at 08:00 UTC, averaging 3 players.
Server data
What does performance look like on テストサーバー?
Server fps over the last 48 hours averages 237; the floor is 224. Buildings, deployables and all else in the world took the count as high as 67,517 entities. The memory field tops out at 4,075 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does テストサーバー run?
The build is Rust network protocol 2635 and build 168909 on Linux, run by テストサーバー. The protocol has to match before you can join, and Steam does the updating.
Is テストサーバー up, and what does its uptime show?
テストサーバー reports itself online at the current refresh. Count back 5 hours from its reported uptime to get the last restart. Uptime of 99% across the last 7 full days: 167 hours of 168. The first row Rust Data holds for it is dated 13 September 2026.
Which location does テストサーバー run from?
The name of テストサーバー points to Asia, even though no region tag is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 157.85.88.112:29581 is its address.
Map and rules
What rules and settings are recorded for テストサーバー?
No gather rate appears in the name: テストサーバー. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has テストサーバー selected?
The game generates the map on テストサーバー: procedural, size 3,000, seed 1. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
On what schedule does テストサーバー wipe?
No next wipe can be predicted for テストサーバー, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 15 days 18 hours ago, and that is the one in play.
What is wipe day on テストサーバー like?
Recent wipes averaged 3 players at their peak. 6 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 33% of recent wipes. Otherwise the crowd fell below half by day 1.
Lists and tags
Which Rust Data filters and lists contain テストサーバー?
These Rust Data lists include テストサーバー: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on テストサーバー hold?
Read by the game's server browser, the tags テストサーバー publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join テストサーバー?
Enter client.connect 157.85.88.112:29581 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/uk2Bfmnea is the website recorded for it.