TESTING

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 11m ago · 51.83.150.41:28015

Abstract

We describe the public Rust server TESTING, reached at 51.83.150.41:28015. At the last check it held 0 of 500 places, against a seven-day mean of 0 and a peak of 4¹. It ranks #8,846 of all servers, the top 40%. It last wiped 10d ago.

Keywordsmodded carbon

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/500	0% full
In the queue	0	no queue
Seven-day mean	0	peak 4, 48 h peak 1
Rank²	#8,846	top 40%
Last wipe	10d ago	no schedule published
Next wipe³	–	no rhythm it keeps

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 40% 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: no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

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

Measure	Value	Note
Usual gap	3 days	between real wipes
On rhythm	50%	of its recent wipes
Wipe-day peak	15	players, last three wipes
Crowd held	80%	else halves by day 1

Sat 17 OctThu 15 OctMon 12 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, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
Sat 17 Oct, 19:1210d ago	1	–	running	0
Thu 15 Oct, 14:5812d ago	18	held half	2.2 d	3
Mon 12 Oct, 14:5915d ago	25	held half	3 d	0
Thu 8 Oct, 14:5819d ago	12	held half	4 d	4
Mon 5 Oct, 15:0022d ago	24	held half	3 d	2
Thu 1 Oct, 17:57fw26d ago	23	halved by day 1	3.9 d	1
Mon 28 Sep, 15:5829d ago	24	held half	3.1 d	2
Fri 25 Sep, 17:0332d ago	22	held half	3 d	2
Mon 21 Sep, 15:5736d ago	6	halved by day 1	4 d	0
Mon 14 Sep, 15:5643d ago	25	halved by day 2	7 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 TESTING — Figure 5: The map: Procedural Map, size 1000, seed 612351. Open on RustMaps.

Table 4: The server's published settings.

Address	`51.83.150.41:28015`
Region	–
Max players	500
Group limit	8, the default
Wipe schedule	–
Last wipe	17 Oct 2026, 19:12 UTC
Hostname	–
First seen	13 Sep 2026
Map	Procedural Map
Size	1000
Seed	612351

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded server list with rates [2] and servers wiping soon [3].

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

Server	Players
ShockRust \| Blue \| NoLimitno group limit · 156 on average	121/500
МИНИ-КАРТА 2Х \| STORM \| FPS+ 24.10EU · groups of 8+ · weekly · 128 on average	135/100
RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average	125/225
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average	49/700
RustSpain.com \| EU MainEU · groups of 12+ · weekly · 87 on average	6/200
404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average	23/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does TESTING perform well?

Its average server fps over the last 48 hours was 128, with a minimum of 125. The highest number of entities it carried was 4,021, comprising buildings, deployables and all other objects. Its highest memory usage was 1,061 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is TESTING based?

A region is not published by TESTING. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 51.83.150.41:28015 is its address.

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

TESTING is currently online. It last restarted around 2 days 11 hours ago, according to its reported uptime. The server was up 76% of the time over the last 7 full days, 127 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.

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

TESTING is running Rust network protocol 2635 and build 168909 on the Windows operating system. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.5When are wipes carried out on TESTING?

With irregular wipe times, TESTING offers no next wipe to predict. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 10 days 12 hours ago.

A.6What characterises wipe day on TESTING?

Across its recent wipes, the average peak population was 15 players. The peak on the latest wipe came 0 hours after it began. Half the peak was sustained until the next wipe in 80% of recent wipes. Otherwise, a fall below half took place by day 1.

Player count

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

The seven-day player-hours ranking puts TESTING at #8,846, within the top 40% of ranked servers.

A.8What is the population level of TESTING?

On TESTING, 0 of the 500 slots are occupied at present. Over the last week the count averages 0 players and reaches 4 at its height. Averaging 0 players, 09:00 UTC was the busiest hour of the past 48.

Tags, lists

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

gmrust (Game mode): This is survival as standard Rust plays; mp500 (Max players): The slot count is 500; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: plugins or settings modify the game; ^y (Carbon): This server uses Carbon for its plugins: these are the tags TESTING publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

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

Modded Rust servers are the Rust Statistics lists that TESTING fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.11Under what rules and settings does TESTING operate?

The name of TESTING states no gather rate. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is gather, build and raid: the standard game. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Carbon plugins are running. VAC is active: that is Valve's anti-cheat.

A.12What map is in use on TESTING?

Generated by the game from seed 612351, the procedural map on TESTING measures 1,000. Because size and seed determine the map, RustMaps can show it, linked from this page.

Connection

A.13What is the process for joining TESTING?

Enter client.connect 51.83.150.41:28015 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 mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y.

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

Tag	Meaning
Game
`gmrust`	Game mode. This is survival as standard Rust plays.
`mp500`	Max players. The slot count is 500.
`ts8`	Group limit. 8 per team, the value the game sets by default.
`v2635`	Protocol. The game protocol is 2635; your client must match it to join.
`cs168909`	Build. The game build is 168909.
`ptrak`	Networking. The network layer is RakNet, standard for the game.
`$r?`	Region code. No region code is set.
Mods and access
`^z`	Modded. Modded listing: plugins or settings modify the game.
`^y`	Carbon. This server uses Carbon for its plugins.

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 server list with rates. ruststatistics.org/top-modded-rust-servers.
[3]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.