Test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 12m ago · 66.51.99.64:28035

Abstract

We describe the public Rust server Test, reached at 66.51.99.64:28035. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 1¹. It ranks #14,527 of all servers, the top 65%. It last wiped 27d ago on a published monthly schedule; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.

Keywordsmonthly wipes 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/50	0% full
In the queue	0	no queue
Seven-day mean	0	peak 1
Rank²	#14,527	top 65%
Last wipe	27d ago	monthly schedule
Next wipe³	7d 17h	Thu 5 Nov, 19:00 UTCfw

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.

AveragePeak

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

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, measured since 17 Sep.

4Rank

The server stands in the top 65% 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: force wipes only

The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 17h. The force wipe (high confidence).

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

Measure	Value	Note
Usual gap	0.6 days	between real wipes
Wipe-day peak	1	players, last three wipes

Table 3: Coming wipes, as expected.

When (UTC)	In	Kind
Thu 5 Nov, 19:00	7d 17h	force wipefw
Thu 3 Dec, 19:00	35d 17h	force wipefw

Thu 1 OctThu 1 Oct

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

5.2History

Table 4: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Thu 1 Oct, 17:57fw27d ago	1	–	running	0
Thu 1 Oct, 04:1727d ago	1	–	0.6 d	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

Map of Test — Figure 5: The map: Custom Map, size 5000, seed 1337.

Table 5: The server's published settings.

Address	`66.51.99.64:28035`
Region	–
Max players	50
Group limit	8, the default
Wipe schedule	monthly
Last wipe	1 Oct 2026, 17:57 UTC
Hostname	–
First seen	13 Sep 2026
Map	Custom Map
Size	5000
Seed	1337

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 predicted wipe schedule [3].

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

Server	Players
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average	34/700
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average	5/1000
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 78 on average	74/700
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|МОСКОВСКИЙ 26.10EU · groups of 16+ · monthly · 70 on average	33/1000
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РОССИЯ 22.10EU · groups of 16+ · monthly · 67 on average	1/1000
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РОССИЙСКИЙ 28.10EU · groups of 16+ · monthly · 63 on average	121/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of Test smooth?

Over the past 48 hours, it ran at an average of 5 server fps, with a low of 5. Its entity count reached a maximum of 124,959, including buildings, deployables and all other world objects. Its highest memory usage was 6,722 MB. When fps is low and entity count climbs, players feel lag.

A.2What location does Test have?

A region is not published by Test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 66.51.99.64:28035.

A.3What is the online status and reliability of Test?

Test is online at this time. The uptime it reports indicates a restart about 6 days 2 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first observed on 13 September 2026 by Rust Statistics.

A.4What version of Rust is run on Test?

Test is running Rust network protocol 2635 and build 168909 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5What schedule does Test follow for wipes?

Once a month, Test wipes in line with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. 27 days 7 hours have passed since the current world was generated. The tags show that the server wipes monthly.

A.6What characterises wipe day on Test?

The average busiest point of recent wipes was 1 players. The peak on the latest wipe came 1 hours after it began.

Population

A.7How does Test compare with other Rust servers in the rankings?

Ranked by player hours across seven days, Test holds #14,527, in the top 65% of all ranked servers.

A.8At what level does Test operate in terms of players?

The current population of Test is 0, drawn from 50 slots. The peak over seven days is 1, against an average of 0.

Tags and filters

A.9What do the tags associated with Test signify?

gmrust (Game mode): This is survival as standard Rust plays; mp50 (Max players): The slot count is 50; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^m (Monthly): A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game: these are the tags Test publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Test be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Test fits are: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Settings and map

A.11What are the settings and rules that govern Test?

No gather rate appears in the name of Test. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. 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. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on Test?

Size 5,000 and seed 1337 define the procedural, game-generated map on Test. Equal size and seed yield an identical map, which this page offers to view on RustMaps. The name of the map is Custom Map.

How to join

A.13What is the process for joining Test?

Enter client.connect 66.51.99.64:28035 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp50,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o^z.

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

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp50`	Max players. The slot count is 50.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2635`	Protocol. The game protocol is 2635; your client must match it to join.
`cs168909`	Build. This server runs game build 168909.
`ptrak`	Networking. RakNet is the network layer here, as it is by default in the game.
`$r?`	Region code. The region code is unset.
Wipe schedule
`^m`	Monthly. A monthly wipe cycle applies, timed to coincide with Facepunch's force wipe.
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. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.