TestSerwer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 10d ago · 217.97.60.253:28015

Abstract

We describe the public Rust server TestSerwer, reached at 217.97.60.253:28015. It is offline at the last check, against a seven-day mean of 0¹. It ranks #12,982 of all servers, the top 60%. It last wiped 11d 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²	#12,982	top 60%
Last wipe	11d 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	`217.97.60.253:28015`
Region	–
Max players	10
Group limit	8, the default
Wipe schedule	–
Last wipe	16 Oct 2026, 15:40 UTC
Hostname	–
First seen	16 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 rust community servers listed [2] and predicted wipe schedule [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 · 540 on average	536/575
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average	358/400
Rustoria.co - EU MainEU · groups of 16+ · weekly · 314 on average	36/250
Rusty Moose \|EU Main\|EU · groups of 12+ · weekly · 313 on average	43/250
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 273 on average	159/200
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average	78/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does TestSerwer have?

A region is not published by TestSerwer. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 217.97.60.253:28015 is its address.

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

TestSerwer is currently offline, with the last sighting 10 days 20 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. The first record of it by Rust Statistics dates to 16 October 2026.

A.3What is the Rust version for TestSerwer?

TestSerwer is running Rust network protocol 2634 and build 167781 on the Windows operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4On what cycle does TestSerwer wipe?

The record of TestSerwer's wipes is not yet sufficient to establish its rhythm. 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 11 days 18 hours ago.

Player count

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

Ranked by player hours across seven days, TestSerwer holds #12,982, in the top 60% of all ranked servers.

A.6What is the population level of TestSerwer?

The last recorded sighting of TestSerwer was 10 days 20 hours ago; it is offline now.

Tags and filters

A.7How should the tags on TestSerwer be interpreted?

gmrust (Game mode): Rust survival, in its standard form; mp10 (Max players): 10 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167781 (Build): The game build is 167781; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set: these are the tags TestSerwer 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 TestSerwer be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that TestSerwer fits. 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; Last wipe: In the last 2 weeks.

Rules, settings, map

A.9Under what rules and settings does TestSerwer operate?

Its name carries no gather rate for TestSerwer. No cap is given beyond the game's default of 8 players per group. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Players may raid and fight one another. It is a community server, as the browser's Community listing shows. VAC is not in use; Valve's anti-cheat is off.

A.10What map is in use on TestSerwer?

A procedural map, generated by the game, is what TestSerwer runs.

Connection

A.11What is the process for joining TestSerwer?

Enter client.connect 217.97.60.253: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,cs167781,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. 10 slots are available.
`ts8`	Group limit. The team cap is 8, which is the game default.
`v2634`	Protocol. The game protocol is 2634; your client must match it to join.
`cs167781`	Build. The game build is 167781.
`ptrak`	Networking. Networking runs on RakNet, the game's standard layer.
`$r?`	Region code. No region code is set.

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. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
[3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.