Rust StatisticsWorking papers on every public Rust server · 31,668 players now

typical test2

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 39d ago · 9.244.16.170:28019

Abstract

We describe the public Rust server typical test2, reached at 9.244.16.170:28019. It is offline at the last check, against a seven-day mean of 01. It ranks #15,398 of all servers. It last wiped 39d 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.
MeasureValueNote
Players now0/1000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,398no region published
Last wipe39d agono schedule published
Next wipe3–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 memory4. 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

Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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)PeakCrowdLastedBefore
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.
Address9.244.16.170:28019
Region–
Max players100
Group limit8, the default
Wipe schedule–
Last wipe19 Sep 2026, 06:09 UTC
Hostname–
First seen19 Sep 2026
MapProcedural 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 unmodded rust community servers [2] and upcoming Rust wipes [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 542 on average144/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average136/200
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average14/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average21/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average12/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average52/200

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is typical test2 based?

There is no region published for typical test2. Rust Statistics does not look up the machine's location; it shows where the server says it is. 9.244.16.170:28019 is its address.

A.2What is the reliability of typical test2, and is it online?

At the present moment, typical test2 is offline; it was last seen 39 days 22 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 19 September 2026.

A.3What version of Rust is run on typical test2?

typical test2 is running Rust network protocol 2633 and build 164530 on the Linux 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 typical test2?

The record of typical test2's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. The world currently in use was created 39 days 23 hours ago.

Population

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

The seven-day player-hours ranking puts typical test2 at #15,398, within the top – of ranked servers.

A.6What is the population level of typical test2?

typical test2 is not online now; 39 days 22 hours have passed since it was last seen.

Tags, lists

A.7What is the meaning of the tags on typical test2?

gmrust (Game mode): This is survival as standard Rust plays; mp100 (Max players): It offers 100 slots; 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): This server runs game build 164530; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset: these are the tags typical test2 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.8Where can typical test2 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that typical test2 fits are: Rust community servers, measured. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.9What are the settings and rules that govern typical test2?

The name of typical test2 states no gather rate. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gathering, building and raiding, as the game is usually played. Fighting and raiding between players are both permitted. The server browser lists it under Community. The server has VAC on, Valve's anti-cheat.

A.10What map is in use on typical test2?

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

How to join

A.11How do you connect to typical test2?

Press F1 inside Rust to open the console and enter client.connect 9.244.16.170:28019. 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 mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp100Max players. It offers 100 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs164530Build. This server runs game build 164530.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Unmodded rust community servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Upcoming Rust wipes. ruststatistics.org/rust-servers-wiping-today-list.