Station XX-15411 · no signal
测试bat
Offline 202.189.5.35:20000 checked 5d ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,411
- top 69%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M –not enough readings
Players
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 12.9 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 24 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 17 Oct, 11:59 UTC10d ago | M0.0▲rising | 1 | – | running | 0 | |
| Sun 4 Oct, 14:48 UTC23d ago | M0.0▲rising | 1 | halved by day 1 | 12.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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on 测试bat?
Generated by the game, the map on 测试bat is procedural, size 2,500 with seed 1337. 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 测试bat?
No gather rate appears in the name of 测试bat. The group limit is 16 players. It plays in survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on 测试bat?
测试bat is not responding at this moment and is offline, last seen 5 days 1 hours ago. The seven-day average for this server is 0 players.
How does 测试bat rank against other Rust servers?
The last seven days of player hours place 测试bat at #15,411, in the top 69% of all ranked servers.
Server details
How reliably does 测试bat stay online?
No contact with 测试bat right now, and the last recorded contact was 5 days 1 hours ago. 49 of 168 hours in the last 7 full days were up time, 29% of the total. On 1 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is 测试bat hosted?
Its name points to Asia, but 测试bat 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 202.189.5.35:20000.
What build of Rust does 测试bat use?
测试bat is running Rust network protocol 2634 and build 167781 on a machine with Windows. 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 测试bat?
On average, the busiest point of its recent wipes drew 1 players. 24 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. It fell under half by day 1 in the wipes where it didn't hold.
On what timetable does 测试bat run its wipes?
The rhythm of 测试bat cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 10 days 14 hours is how long the current world has been running.
Lists and tags
What do the server tags on 测试bat mean?
The game's server browser reads the tags 测试bat publishes: gmrust (Game mode): Survival in standard Rust; mp100 (Max players): 100 slots are available; ts16 (Group limit): Each team can hold up to 16; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does 测试bat appear?
These Rust Server Trends lists include 测试bat: Modded Rust servers, tracked live. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
What steps get you onto 测试bat?
You can connect by pressing F1 in Rust and typing client.connect 202.189.5.35:20000 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
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.