Rust StatisticsWorking papers on every public Rust server · 88,657 players now

TestServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 44d ago · 91.11.200.94:28015

Abstract

We describe the public Rust server TestServer, reached at 91.11.200.94:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,034 of all servers. It last wiped 49d 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 now1/520% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,034no region published
Last wipe49d 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.

No rank history yet.
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.
Address91.11.200.94:28015
Region–
Max players5
Group limit8, the default
Wipe schedule–
Last wipe8 Sep 2026, 08:18 UTC
Hostname–
First seen13 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 busiest community rust servers [2] and predicted wipe schedule [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 · 504 on average780/825
Rustoria.co - EU MainEU · groups of 16+ · weekly · 345 on average47/250
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 340 on average124/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 314 on average412/500
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 280 on average247/300
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 259 on average190/300

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does TestServer have?

There is no region published for TestServer. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 91.11.200.94:28015 is its address.

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

At the present moment, TestServer is offline; it was last seen 44 days 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 13 September 2026.

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

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

Wipe timing

A.4What schedule does TestServer follow for wipes?

Too few wipes by TestServer have been recorded to determine the pattern. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 49 days 11 hours have passed since the current world was generated.

Player count

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

The seven-day player-hours ranking puts TestServer at #13,034, within the top – of ranked servers.

A.6At what level does TestServer operate in terms of players?

The last recorded sighting of TestServer was 44 days ago; it is offline now.

Tags and filters

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

gmrust (Game mode): Survival on standard Rust rules; mp5 (Max players): It offers 5 slots; ts8 (Group limit): The team cap is 8, which is the game default; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs163207 (Build): The game build is 163207; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset: these are the tags TestServer 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.8Where can TestServer be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that TestServer fits. These filters on the server list return it: 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 TestServer?

The name of TestServer states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gather, build and raid: the standard game. Fighting and raiding between players are both permitted. It is a community server, as the browser's Community listing shows. VAC, Valve's anti-cheat, is enabled.

A.10What is the map for TestServer?

The game generates the map on TestServer; that format is procedural.

Connection

A.11How do you connect to TestServer?

Enter client.connect 91.11.200.94: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 mp5,ptrak,$r?,v2633,gmrust,cs163207,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp5Max players. It offers 5 slots.
ts8Group limit. The team cap is 8, which is the game default.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs163207Build. The game build is 163207.
ptrakNetworking. The network layer is RakNet, standard for 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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Busiest community rust servers. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.