Rust Server IndexCard catalogue of Rust servers

Holdings11,829 servers89,289 players90 fresh wipes

Call no.15426 Off the shelf · offline

测试bat

Offline 202.189.5.35:20000 checked 5d ago

Subjects 1. modded2. oxide
Players now
0/ 100
0% full
7-day average
0
peak –
Rank
#15,426
top 69%
Last wipeWiped17 OCT2026 · 11d 6h ago
11d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

No hourly history yet.

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k1 Oct6 Oct12 Oct17 Oct23 Oct28 Oct

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

Record sheet D · loan terms

Wipe schedule

too few wipes seen yet

Not 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

Sat 17 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 24 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
17 OCT 2026Sat 17 Oct, 11:59 UTC11d ago
1 – running 0
4 OCT 2026Sun 4 Oct, 14:48 UTC24d ago
1 halved by day 1 12.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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EA
QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造EA · groups of 20+ · weekly · 24 on average
33/ 100
EA
【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐EA · groups of 8+ · weekly · 18 on average
32/ 200
EA
[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 17 on average
5/ 100
EA
[JP] DON-tacos PvEEA · groups of 8+ · monthly · 11 on average
7/ 100
EA
#10-[搞就完了]10倍/10.28新档/无权/萌新首选EA · no group limit · 11 on average
16/ 100
EA 23/ 100
Reference desk

Quick answers

From the figures on this page.

Rules and settings

On 测试bat, which rules and settings apply?

No gather rate appears in the name 测试bat. The server sets a group limit of 16 players. The server runs survival, building, gathering and raiding in the standard game. Combat and raiding between players are possible. The server browser lists it under Modded; plugins or settings alter the game. Oxide plugins are run on it. The server has VAC, Valve's anti-cheat, turned on.

What is the map on 测试bat?

Generated by the game, the procedural map of 测试bat has size 2,500 and seed 1337. From this page you can view the map on RustMaps; the same size and seed give the same map.

Tags

On Rust Server Index, which lists and filters carry 测试bat?

Filed under these Rust Server Index lists is 测试bat: Modded Rust servers, filed by play style. It appears under the following filters 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.

How should you read the tags listed for 测试bat?

These are the tags 测试bat publishes; the game's server browser reads this list: gmrust (Game mode): Survival on standard Rust rules; mp100 (Max players): The queue ceiling sits at 100; ts16 (Group limit): 16 is the largest team allowed; v2634 (Protocol): The protocol is 2634; older or newer clients cannot join; cs167781 (Build): The game build here is 167781; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): No region code has been set; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipe schedule

What should you expect on 测试bat when wipe day comes?

The average peak across its recent wipes is 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. By day 1 the crowd had fallen below half when it didn't hold.

Which wipe timetable does 测试bat follow?

Its rhythm is not yet clear, since the record holds too few of 测试bat's wipes. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 11 days 6 hours is when its current world was made.

Players and ranking

How is 测试bat ranked compared with the rest?

Filed under rankings: #15,426 for 测试bat on seven-day player hours, top 69% overall.

How many players are on 测试bat at the moment?

At present 测试bat is offline; its last sighting was 5 days 17 hours ago. Filed under seven-day average: 0 players.

Operator and status

What version does 测试bat use?

Rust network protocol 2634 and build 167781 on Windows is what you will find on 测试bat. The protocol must match before you can join, and Steam takes care of updating it.

Is 测试bat reachable, and does it stay up?

Last seen 5 days 17 hours ago, 测试bat is offline right now. Uptime for the last 7 full days came to 29%, 49 hours out of 168. The earliest sighting at Rust Server Index is 1 October 2026.

Which region is 测试bat in?

No region tag is published by 测试bat; the name it carries points to Asia. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. Connection details: 202.189.5.35:20000.

Connecting

What steps lead onto 测试bat?

If you would rather use the console, press F1 in Rust and enter client.connect 202.189.5.35:20000. You can also choose Launch Rust and join here; that opens Rust through Steam and connects you.

Subject headings explained

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2634,gmrust,cs167781,ts16,^o^z

Game

gmrust
Game mode Survival on standard Rust rules.
mp100
Max players The queue ceiling sits at 100.
ts16
Group limit 16 is the largest team allowed.
v2634
Protocol The protocol is 2634; older or newer clients cannot join.
cs167781
Build The game build here is 167781.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide This server uses Oxide (uMod) for plugins.
^z
Modded Modded: the game is changed by plugins or settings.

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.