测试

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 36d ago · 183.221.149.16:26690

Abstract

We describe the public Rust server 测试, reached at 183.221.149.16:26690. It is offline at the last check, against a seven-day mean of 0¹. It ranks #15,477 of all servers, the top 68%. It last wiped 36d ago on a published biweekly schedule; the next wipe is expected Monday 2 November, 04:17 UTC, its biweekly schedule tag.

Keywordsbiweekly wipes vanilla modded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.

Measure	Value	Note
Players now	0/2	0% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#15,477	top 68%
Last wipe	36d ago	biweekly schedule
Next wipe³	5d 0h	Mon 2 Nov, 04:17 UTC

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.

Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory⁴. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure

range

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

Figure 2: 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.

4Rank

The server stands in the top 68% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region

Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: from its schedule tag

The next wipe is expected Monday 2 November, 04:17 UTC, in 5d 0h. Its biweekly schedule tag (low confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.

Measure	Value	Note
Wipe-day peak	0	players, last three wipes

Table 3: Coming wipes, as expected.

When (UTC)	In	Kind
Mon 2 Nov, 04:17	5d 0h	its own schedule
Thu 5 Nov, 19:00	8d 14h	force wipefw
Mon 16 Nov, 04:17	19d 0h	its own schedule
Mon 30 Nov, 04:17	33d 0h	its own schedule
Thu 3 Dec, 19:00	36d 14h	force wipefw

No hourly players around its wipes yet.

Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 4: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Mon 21 Sep, 04:1736d ago	0	–	running	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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published

Figure 5: The map: Procedural Map.

Table 5: The server's published settings.

Address	`183.221.149.16:26690`
Region	–
Max players	2
Group limit	8, the default
Wipe schedule	biweekly
Last wipe	21 Sep 2026, 04:17 UTC
Hostname	–
First seen	21 Sep 2026
Map	Procedural Map
Size	–
Seed	–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2] and upcoming Rust wipes [3].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.

Server	Players
［JP］初心者PVPサーバー｜RaidTime・ EventsEA · groups of 10+ · biweekly · 19 on average	6/100
[JP] RUST SOLO ONLY \| PvP \| Beginner [ L.R.S. ] 10/16~10/29EA · no group limit · biweekly · 5 on average	1/20
瞌睡熊『5倍10废\|10.28\|萌新首选\|无权限』EA · groups of 8+ · biweekly · 4 on average	4/100
[JP/PvE][BPリサーチ]MatoyServer初しん者〇EA · groups of 8+ · biweekly · 2 on average	1/50
[JPN] Apple Server \| PvP \| Vanilla \| 2WeeklyEA · groups of 8+ · biweekly · 2 on average	3/50
cczsbwd/solo/独狼/原倍半月清/月图/公益服EA · no group limit · biweekly · 1 on average	4/50

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is 测试 based?

Without a region tag from 测试, its name still points to Asia. Rust Statistics does not look up the machine's location; it shows where the server says it is. 183.221.149.16:26690 is its address.

A.2How reliable is 测试, and is it currently online?

测试 is currently offline, with the last sighting 36 days 23 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. The first record of it by Rust Statistics dates to 21 September 2026.

A.3What version of Rust is run on 测试?

测试 is running Rust network protocol 2633 and build 164530 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.4What schedule does 测试 follow for wipes?

The record of 测试's wipes is too sparse to confirm the schedule, so the prediction is based on its tag. On Monday 2 November at 04:17 UTC the next wipe is expected. 36 days 23 hours have passed since the current world was generated. A fortnightly wipe schedule appears in its tags.

A.5How would you describe wipe day on 测试?

Recent wipes saw an average peak of 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.6How does 测试 compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts 测试 at #15,477, within the top 68% of ranked servers.

A.7At what level does 测试 operate in terms of players?

At this moment 测试 is offline, having last been seen 36 days 23 hours ago.

Tags and filters

A.8What do the tags associated with 测试 signify?

The game's server browser reads gmvanilla (Game mode): This is survival in its vanilla form; mp2 (Max players): 2 slots are available; ts8 (Group limit): 8 per team, the value the game sets by default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs164530 (Build): The game build is 164530; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set; ^b (Biweekly): Wipes take place once a fortnight; ^v (Vanilla): This is the game as Facepunch ships it, with rates, kits and rules unaltered; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which 测试 publishes as its tags. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can 测试 be found among the Rust Statistics lists and filters?

These Rust Statistics lists include 测试: Modded Rust servers. You will find it on the server list filtered by: Region: Asia; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Settings and map

A.10What are the settings and rules that govern 测试?

Its name carries no gather rate for 测试. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. The plugin count is Oxide. It describes itself as vanilla, which is to say this is the game as Facepunch ships it, with rates, kits and rules unaltered. VAC is not in use; Valve's anti-cheat is off.

A.11What map is in use on 测试?

On 测试 the terrain is procedural, built by the game itself.

Connection

A.12What steps are required to join 测试?

Press F1 inside Rust to open the console and enter client.connect 183.221.149.16:26690. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp2,ptrak,$r?,v2633,^b,^v,gmvanilla,cs164530,ts8,^o^z.

Table 7: The server's tags and their meanings.

Tag	Meaning
Game
`gmvanilla`	Game mode. This is survival in its vanilla form.
`mp2`	Max players. 2 slots are available.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2633`	Protocol. The game protocol is 2633; your client must match it to join.
`cs164530`	Build. The game build is 164530.
`ptrak`	Networking. RakNet is the network layer here, as it is by default in the game.
`$r?`	Region code. No region code is set.
Wipe schedule
`^b`	Biweekly. Wipes take place once a fortnight.
Difficulty
`^v`	Vanilla. This is the game as Facepunch ships it, with rates, kits and rules unaltered.
Mods and access
`^o`	Oxide. The plugin framework in use is Oxide (uMod).
`^z`	Modded. Modded listing: plugins or settings modify the game.

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.

References

[1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
[2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.