Station XX-12442 · no signal
RPTEST
Offline 192.154.104.162:28016 checked 4d ago
- Players now
- 1/ 500
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #12,442
- top 56%
- Last wipe
- 4d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 500 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 56% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 1.3 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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 |
|---|---|---|---|---|---|---|
| Sat 24 Oct, 08:35 UTC4d ago | M0.0■steady | 1 | – | – | running | 1 |
| Thu 22 Oct, 20:44 UTC6d ago | M0.0▲rising | 1 | – | 1.5 days | 0 | |
| Wed 21 Oct, 02:01 UTC8d ago | M0.0▲rising | 1 | – | 1.8 days | 0 | |
| Tue 20 Oct, 17:42 UTC8d ago | M0.0▲rising | 1 | – | 0.3 days | 0 | |
| Sun 18 Oct, 12:57 UTC10d ago | M0.0▼falling | 0 | – | – | 2.2 days | 1 |
| Sun 18 Oct, 06:53 UTC10d ago | M0.0▲rising | 2 | – | 0.3 days | 1 | |
| Sat 17 Oct, 14:12 UTC11d ago | M0.0▲rising | 2 | – | 0.7 days | 1 | |
| Wed 14 Oct, 17:47 UTC14d ago | M0.0■steady | 1 | – | 2.9 days | 1 |
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 settings and rules apply on RPTEST?
The name of RPTEST gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.
Player counts
How many players are recorded on RPTEST right now?
RPTEST is not responding at this moment and is offline, last seen 4 days 21 hours ago. The seven-day average is 0 players, with a peak of 1.
How does RPTEST rank against other Rust servers?
The last seven days of player hours place RPTEST at #12,442, in the top 56% of all ranked servers.
Server facts
How reliably does RPTEST stay online?
RPTEST is down at the moment; the last recorded contact was 4 days 21 hours ago. Of the 168 hours in the last 7 full days, it was up for 21, or 12% of the time. 2 October 2026 is when Rust Server Trends first recorded it.
Which region does RPTEST run from?
Nothing about a region comes from RPTEST. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 192.154.104.162:28016.
Which Rust version is RPTEST running?
Rust network protocol 2635 and build 168909 on Windows is what RPTEST runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on RPTEST?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does RPTEST run its wipes?
No next wipe can be predicted for RPTEST, which wipes at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 4 days 21 hours.
Tags
What do the server tags on RPTEST mean?
The game's server browser reads the tags RPTEST publishes: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^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 RPTEST appear?
The Rust Server Trends lists that take in RPTEST are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Connecting
What steps get you onto RPTEST?
To join, enter client.connect 192.154.104.162:28016 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.