Station XX-15348 · no signal
replays
Offline 79.165.151.88:28015 checked 9d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,348
- top 70%
- Last wipe
- 21d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 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 70% 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
- 13.8 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
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.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 8 Oct, 09:25 UTC21d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 24 Sep, 13:21 UTC35d ago | M0.0▲rising | 1 | held half | 13.8 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 pageServer rules
Which map is running on replays?
The map on replays is procedural, produced by the game.
Which settings and rules apply on replays?
No gather rate appears in the name of replays. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on replays?
A reading taken now finds replays offline; the most recent activity was 9 days 12 hours ago.
How does replays rank against other Rust servers?
On player hours for the past week, replays sits at #15,348, which puts it inside the top 70% of every ranked server.
Server facts
How reliably does replays stay online?
replays is down at the moment; the last recorded contact was 9 days 12 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 24 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is replays hosted?
Nothing about a region comes from replays. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 79.165.151.88:28015.
Which Rust version is replays running?
replays is running Rust network protocol 2634 and build 167058 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on replays?
The recent wipes averaged a busiest count of 1 players. 0 hours after the latest wipe, the crowd peaked. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
On what timetable does replays run its wipes?
Too few wipes of replays 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. It has run its current world for 21 days 11 hours.
Server tags
What do the server tags on replays mean?
The game's server browser reads the tags replays publishes: gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): The server has 1 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167058 (Build): It runs game build 167058; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does replays appear?
You will find replays on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to replays?
To join, enter client.connect 79.165.151.88: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.