test_server

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 26d ago · 46.63.106.19:28015

Abstract

We describe the public Rust server test_server, reached at 46.63.106.19:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #14,212 of all servers, the top 60%. It last wiped 26d ago.

Keywordsrust server

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	1/10	10% full
In the queue	0	no queue
Seven-day mean	0	peak –
Rank²	#14,212	top 60%
Last wipe	26d ago	no schedule published
Next wipe³	–	no wipe seen yet

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 60% 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

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.

Wiped (UTC)	Peak	Crowd	Lasted	Before
No wipe seen yet.

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 4: The map: Procedural Map.

Table 3: The server's published settings.

Address	`46.63.106.19:28015`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	1 Oct 2026, 10:16 UTC
Hostname	–
First seen	1 Oct 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 player-run rust server list [2] and servers wiping soon [3].

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

Server	Players
Rusty Moose \|EU Mondays\|EU · groups of 12+ · weekly · 532 on average	214/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 327 on average	15/250
Rusty Moose \|EU Main\|EU · groups of 12+ · weekly · 325 on average	19/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average	115/200
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average	40/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average	42/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of test_server?

No region is published by test_server. 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 46.63.106.19:28015.

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

Right now, test_server is offline, and the last time it was seen was 26 days 15 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. It was first observed on 1 October 2026 by Rust Statistics.

A.3What version of Rust is run on test_server?

test_server is running Rust network protocol 2634 and build 166465 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4When are wipes carried out on test_server?

There are not yet enough recorded wipes for test_server to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 26 days 17 hours have passed since the current world was generated.

Player count

A.5What position does test_server occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts test_server at #14,212, within the top 60% of ranked servers.

A.6What is the population level of test_server?

test_server is not online now; 26 days 15 hours have passed since it was last seen.

Tags and filters

A.7What is the meaning of the tags on test_server?

gmrust (Game mode): Rust survival, in its standard form; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs166465 (Build): Build 166465 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset: these are the tags test_server publishes, and the server browser reads them. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.8Where can test_server be found among the Rust Statistics lists and filters?

The Rust Statistics lists that test_server fits are: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

A.9Which settings and rules are in force on test_server?

No gather rate appears in the name of test_server. The group cap is 8 players, which is the default in the game. survival is the game mode here; gather, build and raid: the standard game. Players may raid and fight one another. The server browser lists it under Community. VAC is active: that is Valve's anti-cheat.

A.10What map is in use on test_server?

On test_server the terrain is procedural, built by the game itself.

Connection

A.11How do you connect to test_server?

Enter client.connect 46.63.106.19: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 mp10,ptrak,$r?,v2634,gmrust,cs166465,ts8.

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

Tag	Meaning
Game
`gmrust`	Game mode. Rust survival, in its standard form.
`mp10`	Max players. The slot count is 10.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2634`	Protocol. Joining requires the same game version: protocol 2634.
`cs166465`	Build. Build 166465 is the one running.
`ptrak`	Networking. RakNet is the network layer here, as it is by default in the game.
`$r?`	Region code. The region code is unset.

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