Rust StatisticsWorking papers on every public Rust server · 41,011 players now

RustDockerServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 6m ago · 70.237.29.165:28015

Abstract

We describe the public Rust server RustDockerServer, reached at 70.237.29.165:28015. At the last check it held 0 of 1 places, against a seven-day mean of 01. It ranks #15,349 of all servers, the top 69%. It last wiped 26d 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/10% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,349top 69%
Last wipe26d 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
0123402:0011:0020:0005:0014:0000: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
05010015020002:0011:0020:0005:0014:0000: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 17 Sep.

4Rank

The server stands in the top 69% 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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 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
Wipe-day peak0players, last three wipes
01234+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 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 2 Oct, 09:1426d ago 0 – running 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 RustDockerServer
Figure 5: The map: Procedural Map, size 4500, seed 1337. Open on RustMaps.
Table 4: The server's published settings.
Address70.237.29.165:28015
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe2 Oct 2026, 09:14 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4500
Seed1337

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are player-run rust server list [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 565 on average195/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average114/200
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average21/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 289 on average12/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average21/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 251 on average27/225

Appendix AQuick answers

From the figures on this page.

About the server

A.1How well does RustDockerServer run?

The server fps averaged 129 over the last 48 hours, never dropping below 95. The highest number of entities it carried was 121,769, comprising buildings, deployables and all other objects. Memory use peaked at 3,506 MB. When fps is low and entity count climbs, players feel lag.

A.2In which location is RustDockerServer based?

There is no region published for RustDockerServer. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 70.237.29.165:28015.

A.3What is the reliability of RustDockerServer, and is it online?

RustDockerServer is online at this time. The uptime it reports indicates a restart about 14 hours ago. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. Its first appearance in Rust Statistics's records is 13 September 2026.

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

RustDockerServer is running Rust network protocol 2635 and build 168909 on the Linux operating system. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5On what cycle does RustDockerServer wipe?

The record of RustDockerServer's wipes is not yet sufficient to establish its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 26 days 16 hours have passed since the current world was generated.

A.6What characterises wipe day on RustDockerServer?

The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Population

A.7What position does RustDockerServer occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts RustDockerServer at #15,349, within the top 69% of ranked servers.

A.8What is the population level of RustDockerServer?

At this moment 0 players are on RustDockerServer, which has 1 slots in total. Averaged across the last seven days, the population is 0 players.

Tags and filters

A.9What do the tags associated with RustDockerServer signify?

gmrust (Game mode): This is survival as standard Rust plays; mp1 (Max players): 1 slots are available; 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): This server runs game build 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: these are the tags RustDockerServer 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.10Where can RustDockerServer be found among the Rust Statistics lists and filters?

Rust community servers, measured are the Rust Statistics lists that RustDockerServer 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.

Settings and map

A.11What are the settings and rules that govern RustDockerServer?

The name of RustDockerServer states no gather rate. At 8 players, the group limit equals the game's default. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Community is its category in the server browser. VAC is active: that is Valve's anti-cheat.

A.12What map is in use on RustDockerServer?

Size 4,500 and seed 1337 define the procedural, game-generated map on RustDockerServer. Equal size and seed yield an identical map, which this page offers to view on RustMaps.

Connection

A.13What is the process for joining RustDockerServer?

Enter client.connect 70.237.29.165: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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. This is survival as standard Rust plays.
mp1Max players. 1 slots are available.
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. This server runs game build 168909.
ptrakNetworking. RakNet is the network layer here, as it is by default in 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. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.