Rust StatisticsWorking papers on every public Rust server · 102,135 players now

pavserv137

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 8d ago · 31.132.219.234:28015

Abstract

We describe the public Rust server pavserv137, reached at 31.132.219.234:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,432 of all servers, the top 69%. It last wiped 17d 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/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,432top 69%
Last wipe17d 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

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
15k10k15k20k15 Oct18 Oct20 Oct23 Oct25 Oct28 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

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address31.132.219.234:28015
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe12 Oct 2026, 16:30 UTC
Hostname–
First seen15 Oct 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 player-run rust server list [2] and servers wiping soon [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 · 514 on average366/425
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average457/500
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 280 on average980/1000
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average53/100
Rustoria.co - EU MainEU · groups of 16+ · weekly · 265 on average964/1000
Rustoria.co - US MainNA · groups of 16+ · weekly · 235 on average32/250

Appendix AQuick answers

From the figures on this page.

About the server

A.1What is the location of pavserv137?

No region is published by pavserv137. Rust Statistics does not look up the machine's location; it shows where the server says it is. 31.132.219.234:28015 is its address.

A.2How reliable is pavserv137, and is it currently online?

Right now, pavserv137 is offline, and the last time it was seen was 8 days 4 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. Its first appearance in Rust Statistics's records is 15 October 2026.

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

Rust network protocol 2634 and build 167398 is the version that pavserv137 runs, on Windows. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4On what cycle does pavserv137 wipe?

Too few wipes by pavserv137 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. The current world has been running for 17 days 1 hours.

Player count

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

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

A.6How would you characterise the player activity on pavserv137?

At this moment pavserv137 is offline, having last been seen 8 days 4 hours ago.

Tags and filters

A.7What do the tags associated with pavserv137 signify?

gmrust (Game mode): Rust survival, in its standard form; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs167398 (Build): Build 167398 is the one running; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set: these are the tags pavserv137 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 pavserv137 be found among the Rust Statistics lists and filters?

The Rust Statistics lists that pavserv137 fits are: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Settings and map

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

Its name carries no gather rate for pavserv137. 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. Players may raid and fight one another. It is a community server, as the browser's Community listing shows. VAC is not in use; Valve's anti-cheat is off.

A.10What map is in use on pavserv137?

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

Connection

A.11What steps are required to join pavserv137?

Press F1 inside Rust to open the console and enter client.connect 31.132.219.234: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 mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp10Max players. The slot count is 10.
ts8Group limit. The team cap is 8, which is the game default.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs167398Build. Build 167398 is the one running.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. No region code is set.

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. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.