Rust StatisticsWorking papers on every public Rust server · 34,156 players now

Testserver

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 15m ago · 157.85.85.43:23120

Abstract

We describe the public Rust server Testserver, reached at 157.85.85.43:23120. At the last check it held 0 of 1 places, against a seven-day mean of 0 and a peak of 11. It ranks #12,095 of all servers, the top 54%. It last wiped 7d 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/10% full
In the queue0no queue
Seven-day mean0peak 1
Rank2#12,095top 54%
Last wipe7d agono schedule published
Next wipe3–too few wipes 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
0123406:0015:0000:0009:0018:0003: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
010020030040006:0015:0000:0009:0018:0003: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 1 Oct.

4Rank

The server stands in the top 54% 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
15k10k15k20k1 Oct6 Oct12 Oct17 Oct23 Oct28 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

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

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap19 daysbetween real wipes
Wipe-day peak1players, last three wipes
Crowd held0%else halves by day 1
Tue 20 OctThu 1 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Tue 20 Oct, 14:507d ago 1 – running 0
Thu 1 Oct, 15:2126d ago 1 halved by day 1 19 d 0

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 Testserver
Figure 5: The map: Procedural Map, size 1500, seed 50000. Open on RustMaps.
Table 4: The server's published settings.
Address157.85.85.43:23120
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe20 Oct 2026, 14:50 UTC
Hostname–
First seen1 Oct 2026
MapProcedural Map
Size1500
Seed50000

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 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 158 on average49/500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average131/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average0/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average29/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average5/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average12/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of Testserver smooth?

Over the past 48 hours, it ran at an average of 237 server fps, with a low of 217. The highest number of entities it carried was 8,424, comprising buildings, deployables and all other objects. Its highest memory usage was 3,472 MB. When fps is low and entity count climbs, players feel lag.

A.2What is the location of Testserver?

There is no region published for Testserver. 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 157.85.85.43:23120.

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

Testserver is currently online. The uptime it reports indicates a restart about 4 days 18 hours ago. Its uptime over the last full days (7 days) was 100%, with 168 of 168 hours online. The first record of it by Rust Statistics dates to 1 October 2026.

A.4What version of Rust is run on Testserver?

Testserver is running Rust network protocol 2635 and build 168909 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5When are wipes carried out on Testserver?

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

A.6What happens on Testserver when wipe day arrives?

The average busiest point of recent wipes was 1 players. The crowd reached its maximum 0 hours after the latest wipe. Half the peak was sustained until the next wipe in 0% of recent wipes. Otherwise, a fall below half took place by day 1.

Player count

A.7How does Testserver compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts Testserver at #12,095, within the top 54% of ranked servers.

A.8What is the population level of Testserver?

On Testserver, 0 of the 1 slots are occupied at present. The peak over seven days is 1, against an average of 0.

Tags, lists

A.9How should the tags on Testserver be interpreted?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp1 (Max players): It offers 1 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): The game build is 168909; 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): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which Testserver publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Testserver be found among the Rust Statistics lists and filters?

The Rust Statistics lists that Testserver fits are: Modded Rust servers. It appears under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.11What 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; the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.

A.12What map is in use on Testserver?

The game generates Testserver's procedural map at size 1,500, from seed 50000. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

How to join

A.13What is the process for joining Testserver?

Press F1 inside Rust to open the console and enter client.connect 157.85.85.43:23120. 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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp1Max players. It offers 1 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. The game build is 168909.
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. The plugin framework in use is Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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.