Station XX-13672 · no signal
3am17 staging test
Offline 83.17.151.145:28015 checked 20d ago
- Players now
- 1/ 20
- 5% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,672
- top 62%
- Last wipe
- 20d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 20 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 62% 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
- 4 daysbetween real wipes
- wipe-day peak
- 1players, 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 1, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 8 Oct, 10:21 UTC20d ago | M0.0■steady | 1 | – | running | 1 | |
| Sun 4 Oct, 09:42 UTC24d ago | M0.0■steady | 1 | halved by day 1 | 4 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 map is running on 3am17 staging test?
A procedural map runs on 3am17 staging test, generated by the game.
Which settings and rules apply on 3am17 staging test?
The name of 3am17 staging test gives no gather rate. At the game's default, groups can have up to 8 players. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on 3am17 staging test?
A reading taken now finds 3am17 staging test offline; the most recent activity was 20 days 18 hours ago.
How does 3am17 staging test rank against other Rust servers?
The last seven days of player hours place 3am17 staging test at #13,672, in the top 62% of all ranked servers.
Server facts
How reliably does 3am17 staging test stay online?
No contact with 3am17 staging test right now, and the last recorded contact was 20 days 18 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 3 October 2026 is when Rust Server Trends first recorded it.
Where in the world is 3am17 staging test hosted?
A region is not published by 3am17 staging test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 83.17.151.145:28015 is the address it uses.
Which Rust version is 3am17 staging test running?
Rust network protocol 2634 and build 166655 on Windows is what 3am17 staging test runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on 3am17 staging test?
1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe. Until the next wipe the crowd remained above half that peak in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.
On what timetable does 3am17 staging test run its wipes?
The rhythm of 3am17 staging test cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 20 days 19 hours.
Tags
What do the server tags on 3am17 staging test mean?
Tags published by 3am17 staging test and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): The server has 20 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166655 (Build): It runs game build 166655; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does 3am17 staging test appear?
The Rust Server Trends lists that take in 3am17 staging test are: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
How do you connect to 3am17 staging test?
To join, enter client.connect 83.17.151.145: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.