Rust StatisticsWorking papers on every public Rust server · 67,310 players now

Savage's Primrust - LOCAL TEST

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 7d ago · 35.132.96.40:28015

Abstract

We describe the public Rust server Savage's Primrust - LOCAL TEST, reached at 35.132.96.40:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,344 of all servers, the top 69%. It last wiped 7d ago.

Keywordsmodded carbon

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,344top 69%
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.

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
15k10k15k20k26 Sep29 Sep3 Oct21 Oct25 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 gap2.1 daysbetween real wipes
Wipe-day peak0players, last three wipes
Crowd held0%else halves by day 1
Wed 21 OctMon 19 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 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 21 Oct, 23:147d ago 0 – running 0
Mon 19 Oct, 20:439d ago 1 halved by day 1 2.1 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

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address35.132.96.40:28015
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe21 Oct 2026, 23:14 UTC
Hostname–
First seen26 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 browse modded Rust servers [2], live primitive server counts [3] and next Rust wipe times [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
RustForNoobs.com Primitive | Bow / Melee | MedievalNA · groups of 16+ · biweekly · 1 on average1/50
[US East] Facepunch Primitive 1NA · groups of 8+ · monthly · 22 on average9/400
[EU] Facepunch Primitive 1EU · groups of 8+ · monthly · 16 on average21/400
JumpRust.com - EU 3x|Primitive|Full PVP|Shop|Kits|TP|Clans|EU · groups of 16+ · 3x · biweekly · 5 on average4/120
JumpRust.com - US 3x|Primitive|Full PVP|Shop|Kits|TP|Clans|NA · groups of 16+ · 3x · biweekly · 4 on average2/120
Rust4Noobs | Solo/Duo | Primitive Monthly | No BP WipeEU · duo · monthly · 6 on average3/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of Savage's Primrust - LOCAL TEST?

No region is published by Savage's Primrust - LOCAL TEST. Rust Statistics does not look up the machine's location; it shows where the server says it is. 35.132.96.40:28015 is its address.

A.2What is the online status and reliability of Savage's Primrust - LOCAL TEST?

At the present moment, Savage's Primrust - LOCAL TEST is offline; it was last seen 7 days 13 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 26 September 2026.

A.3What version of Rust is run on Savage's Primrust - LOCAL TEST?

Rust network protocol 2634 and build 167781 is the version that Savage's Primrust - LOCAL TEST runs, on Windows. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe schedule

A.4What schedule does Savage's Primrust - LOCAL TEST follow for wipes?

The record of Savage's Primrust - LOCAL TEST's wipes is not yet sufficient to establish its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when every Rust server is wiped. 7 days 13 hours have passed since the current world was generated.

A.5How would you describe wipe day on Savage's Primrust - LOCAL TEST?

The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe. For 0% of recent wipes, the population did not fall below half the peak before the next wipe. If not, the population dropped below half by day 1.

Population

A.6What position does Savage's Primrust - LOCAL TEST occupy in the ranking of Rust servers?

Ranked by player hours across seven days, Savage's Primrust - LOCAL TEST holds #15,344, in the top 69% of all ranked servers.

A.7At what level does Savage's Primrust - LOCAL TEST operate in terms of players?

At this moment Savage's Primrust - LOCAL TEST is offline, having last been seen 7 days 13 hours ago.

Tags, lists

A.8How should the tags on Savage's Primrust - LOCAL TEST be interpreted?

The game's server browser reads gmprimitive (Game mode): Primitive: bows, spears and melee, and no guns; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2634 (Protocol): Your game must run protocol 2634 to connect; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): Plugins run through Carbon, which Savage's Primrust - LOCAL TEST publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can Savage's Primrust - LOCAL TEST be found among the Rust Statistics lists and filters?

These Rust Statistics lists include Savage's Primrust - LOCAL TEST: Modded Rust servers and Primitive Rust servers. These filters on the server list return it: Type: Modded; Game mode: Primitive; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules, settings, map

A.10What are the settings and rules that govern Savage's Primrust - LOCAL TEST?

The name of Savage's Primrust - LOCAL TEST states no gather rate. No cap is given beyond the game's default of 8 players per group. The mode is primitive, which means melee, bows and spears, with no guns. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. The plugin count is Carbon. The server has VAC on, Valve's anti-cheat.

A.11What is the map for Savage's Primrust - LOCAL TEST?

The game generates the map on Savage's Primrust - LOCAL TEST; that format is procedural.

Connection

A.12What steps are required to join Savage's Primrust - LOCAL TEST?

Press F1 inside Rust to open the console and enter client.connect 35.132.96.40: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,gmprimitive,cs167781,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmprimitiveGame mode. Primitive: bows, spears and melee, and no guns.
mp10Max players. 10 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2634Protocol. Your game must run protocol 2634 to connect.
cs167781Build. The game build is 167781.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.
Mods and access
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
^yCarbon. Plugins run through Carbon.

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. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Live primitive server counts. ruststatistics.org/top-primitive-rust-servers.
  4. [4]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.