Station XX-15344 · no signal
Savage's Primrust - LOCAL TEST
Offline 35.132.96.40:28015 checked 7d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,344
- top 69%
- Last wipe
- 7d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 2.1 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
- crowd held
- 0%else halves by day 1
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 21 Oct, 23:14 UTC7d ago | M0.0■steady | 0 | – | – | running | 0 |
| Mon 19 Oct, 20:43 UTC9d ago | M0.0▲rising | 1 | halved by day 1 | 2.1 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Savage's Primrust - LOCAL TEST?
The map on Savage's Primrust - LOCAL TEST is procedural, produced by the game.
Which settings and rules apply on Savage's Primrust - LOCAL TEST?
You will find no gather rate in the name of Savage's Primrust - LOCAL TEST. At the game's default, groups can have up to 8 players. primitive is the game mode, guns are absent; bows, spears and melee remain. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Live population
What is the current population on Savage's Primrust - LOCAL TEST?
Savage's Primrust - LOCAL TEST is not responding at this moment and is offline, last seen 7 days 8 hours ago.
How does Savage's Primrust - LOCAL TEST rank against other Rust servers?
Over the last seven days, Savage's Primrust - LOCAL TEST recorded enough player hours to reach #15,344 worldwide, placing it in the top 69% of all ranked servers.
Server facts
How reliably does Savage's Primrust - LOCAL TEST stay online?
As recorded now, Savage's Primrust - LOCAL TEST is not reachable, the last contact having been 7 days 8 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 26 September 2026 is when Rust Server Trends first recorded it.
Which region does Savage's Primrust - LOCAL TEST run from?
A region is not published by Savage's Primrust - LOCAL TEST. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 35.132.96.40:28015.
What build of Rust does Savage's Primrust - LOCAL TEST use?
Savage's Primrust - LOCAL TEST is running Rust network protocol 2634 and build 167781 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Savage's Primrust - LOCAL TEST?
The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
How often does Savage's Primrust - LOCAL TEST wipe, and on which days?
Too few wipes of Savage's Primrust - LOCAL TEST are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 7 days 9 hours is how long the current world has been running.
Tags
What do the server tags on Savage's Primrust - LOCAL TEST mean?
The game's server browser reads the tags Savage's Primrust - LOCAL TEST publishes: gmprimitive (Game mode): No guns here; it's primitive, with bows, spears and melee only; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Savage's Primrust - LOCAL TEST appear?
The Rust Server Trends lists that take in Savage's Primrust - LOCAL TEST are: Modded Rust servers, tracked live and Primitive Rust servers, live. You will find it under these filters on the server list: Type: Modded; Game mode: Primitive; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto Savage's Primrust - LOCAL TEST?
To join, enter client.connect 35.132.96.40:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.