Station XX-15491 · no signal
Aqaba City | Vanilla | Weekly
Offline 157.85.95.173:25226 checked 38d ago
- Players now
- 0/ 125
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,491
- top 69%
- Last wipe
- 41d ago
- weekly schedule
- Next wipe
- 1h
- Thu 29 Oct, 15:07 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 125 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 15:07 UTC, in 1h. Its weekly schedule tag · low confidence
- wipe-day peak
- 2players, last three wipes
Coming wipes
- 1hThu 29 Oct, 15:07 UTC
- 7d 5hThu 5 Nov, 19:00 UTCFW
- 14d 1hThu 12 Nov, 15:07 UTC
- 21d 1hThu 19 Nov, 15:07 UTC
- 28d 1hThu 26 Nov, 15:07 UTC
- 35d 5hThu 3 Dec, 19:00 UTCFW
- 42d 1hThu 10 Dec, 15:07 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 17 Sep, 15:07 UTC41d ago | M0.3▲rising | 2 | – | 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 Aqaba City | Vanilla | Weekly?
Aqaba City | Vanilla | Weekly runs a procedural map of size 4,500 with seed 1666129418, produced by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Aqaba City | Vanilla | Weekly?
You will find no gather rate in the name of Aqaba City | Vanilla | Weekly. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Community, as a community server. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC on, Valve's anti-cheat.
Population
What is the current population on Aqaba City | Vanilla | Weekly?
No players are recorded on Aqaba City | Vanilla | Weekly at this moment; it is offline, and the last sighting was 38 days 18 hours ago.
How does Aqaba City | Vanilla | Weekly rank against other Rust servers?
On player hours for the past week, Aqaba City | Vanilla | Weekly sits at #15,491, which puts it inside the top 69% of every ranked server.
Server facts
How reliably does Aqaba City | Vanilla | Weekly stay online?
As recorded now, Aqaba City | Vanilla | Weekly is not reachable, the last contact having been 38 days 18 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does Aqaba City | Vanilla | Weekly run from?
A region is not published by Aqaba City | Vanilla | Weekly. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 157.85.95.173:25226.
What build of Rust does Aqaba City | Vanilla | Weekly use?
On Linux, Aqaba City | Vanilla | Weekly runs Rust network protocol 2633 and build 164530. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on Aqaba City | Vanilla | Weekly?
The recent wipes averaged a busiest count of 2 players. The peak on the most recent wipe came 2 hours after the wipe.
On what timetable does Aqaba City | Vanilla | Weekly run its wipes?
The prediction is taken from its tag, since Aqaba City | Vanilla | Weekly has too few wipes on record to confirm the schedule. The date of its next wipe is Thursday 29 October at 15:07 UTC. It has run its current world for 41 days 22 hours. A weekly wipe schedule is published in its tags.
Tags
What do the server tags on Aqaba City | Vanilla | Weekly mean?
Tags published by Aqaba City | Vanilla | Weekly and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp125 (Max players): Slots: 125; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs164530 (Build): It runs game build 164530; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^w (Weekly): The server wipes every week; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Aqaba City | Vanilla | Weekly appear?
You will find Aqaba City | Vanilla | Weekly on the following Rust Server Trends lists: Rust community servers without the side modes and Vanilla Rust servers, recorded live. You will find it under these filters on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Weekly ^w and Vanilla ^v; Group limit: 5 or more; Wipe schedule: Weekly.
Connecting
How do you connect to Aqaba City | Vanilla | Weekly?
Enter client.connect 157.85.95.173:25226 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.