Rust StatisticsWorking papers on every public Rust server · 33,162 players now

typical test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 6m ago · 104.153.151.75:28015

Abstract

We describe the public Rust server typical test, reached at 104.153.151.75:28015. At the last check it held 0 of 100 places, against a seven-day mean of 0 and a peak of 11. It ranks #15,013 of all servers, the top 67%. It last wiped 3d ago.

Keywordsmodded oxide

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 1
Rank2#15,013top 67%
Last wipe3d 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.

AveragePeak
0123407:0016:0001:0009:0019:0004:00
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
010020030040007:0016:0001:0009:0019:0004:00
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 26 Oct.

4Rank

The server stands in the top 67% 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
15k10k15k20k26 Oct27 Oct28 Oct29 Oct
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

Map of typical test
Figure 4: The map: Procedural Map, size 1000, seed 6738. Open on RustMaps.
Table 3: The server's published settings.
Address104.153.151.75:28015
Region–
Max players100
Group limit8, the default
Wipe schedule–
Last wipe26 Oct 2026, 00:35 UTC
Hostname–
First seen26 Oct 2026
MapProcedural Map
Size1000
Seed6738

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and Rust wipe forecast [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 151 on average52/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average134/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average70/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average20/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average3/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average6/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of typical test smooth?

Over the past 48 hours, it ran at an average of 240 server fps, with a low of 229. Buildings, deployables and all other world objects counted together reached a maximum of 3,795 entities. The peak memory usage was 2,075 MB. When fps is low and entity count climbs, players feel lag.

A.2What is the location of typical test?

There is no region published for typical test. 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 104.153.151.75:28015.

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

At the present moment, typical test is online. Based on the uptime it reports, the last restart occurred about 2 days 8 hours ago. Its uptime over the last full days (2 days) was 98%, with 47 of 48 hours online. Its first appearance in Rust Statistics's records is 26 October 2026.

A.4What version of Rust is run on typical test?

The version of Rust on typical test is network protocol 2635 and build 168909, and the operating system is Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5What schedule does typical test follow for wipes?

There are not yet enough recorded wipes for typical test to reveal 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 current world has been running for 3 days 5 hours.

Population

A.6What is the rank of typical test among Rust servers?

Ranked by player hours across seven days, typical test holds #15,013, in the top 67% of all ranked servers.

A.7At what level does typical test operate in terms of players?

The current population of typical test is 0, drawn from 100 slots. The peak over seven days is 1, against an average of 0.

Tags, lists

A.8What do the tags associated with typical test signify?

gmrust (Game mode): Rust survival, in its standard form; mp100 (Max players): 100 slots are available; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): Build 168909 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; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded: these are the tags typical test 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.9Where can typical test be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that typical test fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Rules, settings, map

A.10Which settings and rules are in force on typical test?

Its name carries no gather rate for typical test. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gather, build and raid: the standard game. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.11What map is in use on typical test?

Size 1,000 and seed 6738 define the procedural, game-generated map on typical test. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.12How do you connect to typical test?

Press F1 inside Rust to open the console and enter client.connect 104.153.151.75:28015. 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?,v2635,gmrust,cs168909,ts8,^o^z.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp100Max players. 100 slots are available.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.