Station XX-15861 · no signal
RustAimLab (private)
Offline 150.220.36.191:28415 checked 18d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,861
- top 72%
- Last wipe
- 19d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 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 72% 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
- 0.3 daysbetween real 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, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sat 10 Oct, 01:22 UTC19d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 9 Oct, 17:18 UTC19d ago | M0.0▲rising | 1 | – | 0.3 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 pageMap and rules
Which settings and rules apply on RustAimLab (private)?
No gather rate appears in the name of RustAimLab (private). At the game's default, groups can have up to 8 players. It plays 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. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on RustAimLab (private) right now?
RustAimLab (private) is not responding at this moment and is offline, last seen 18 days 11 hours ago.
How does RustAimLab (private) rank against other Rust servers?
On player hours for the past week, RustAimLab (private) sits at #15,861, which puts it inside the top 72% of every ranked server.
Operator and location
How reliably does RustAimLab (private) stay online?
No contact with RustAimLab (private) right now, and the last recorded contact was 18 days 11 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 8 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is RustAimLab (private) hosted?
No region is published by RustAimLab (private). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 150.220.36.191:28415.
What build of Rust does RustAimLab (private) use?
RustAimLab (private) is running Rust network protocol 2634 and build 166494 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on RustAimLab (private)?
The recent wipes averaged a busiest count of 1 players. 1 hours after the latest wipe, the crowd peaked.
How often does RustAimLab (private) wipe, and on which days?
The rhythm of RustAimLab (private) 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. 19 days 13 hours is how long the current world has been running.
Tags
What do the server tags on RustAimLab (private) mean?
Tags published by RustAimLab (private) and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): 4 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166494 (Build): It runs game build 166494; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 RustAimLab (private) appear?
These Rust Server Trends lists include RustAimLab (private): Modded Rust servers, tracked live and Rust aim training servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Join the server
What steps get you onto RustAimLab (private)?
Enter client.connect 150.220.36.191:28415 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects 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.