Station XX-15473 · no signal
Justin+mctester's Rust
Offline 158.120.182.9:28015 checked 35d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,473
- top 67%
- Last wipe
- 35d 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 67% 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.
- wipe-day peak
- 0players, last three wipes
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 |
|---|---|---|---|---|---|---|
| Tue 22 Sep, 19:50 UTC35d ago | M0.0■steady | 0 | – | running | 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 Justin+mctester's Rust?
The map on Justin+mctester's Rust is procedural, produced by the game.
Which settings and rules apply on Justin+mctester's Rust?
No gather rate appears in the name of Justin+mctester's Rust. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on Justin+mctester's Rust?
A reading taken now finds Justin+mctester's Rust offline; the most recent activity was 35 days 11 hours ago.
How does Justin+mctester's Rust rank against other Rust servers?
Over the last seven days, Justin+mctester's Rust recorded enough player hours to reach #15,473 worldwide, placing it in the top 67% of all ranked servers.
Server details
How reliably does Justin+mctester's Rust stay online?
As recorded now, Justin+mctester's Rust is not reachable, the last contact having been 35 days 11 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 22 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is Justin+mctester's Rust hosted?
A region is not published by Justin+mctester's Rust. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 158.120.182.9:28015.
What build of Rust does Justin+mctester's Rust use?
On Windows, Justin+mctester's Rust runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
What does wipe day look like on Justin+mctester's Rust?
The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does Justin+mctester's Rust wipe, and on which days?
The rhythm of Justin+mctester's Rust cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. 35 days 19 hours is how long the current world has been running.
Server tags
What do the server tags on Justin+mctester's Rust mean?
The game's server browser reads the tags Justin+mctester's Rust publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): Game build: 165217; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server. 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 Justin+mctester's Rust appear?
The Rust Server Trends lists that take in Justin+mctester's Rust are: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Connecting
What steps get you onto Justin+mctester's Rust?
To join, enter client.connect 158.120.182.9: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.