Station XX-15454 · recording
#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11
Online 54.36.18.143:26893 checked 1m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,454
- top 70%
- Last wipe
- 1d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 map is running on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11?
Generated by the game, the map on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 is procedural, size 4,500 with seed 450159596. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11?
Its name points to a gather rate of 2x on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11?
A reading taken now shows 0 players on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11, which has 100 slots. The population averaged 0 players over the past week.
How does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 rank against other Rust servers?
Over the last seven days, #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 recorded enough player hours to reach #15,454 worldwide, placing it in the top 70% of all ranked servers.
Server details
How reliably does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 stay online?
As recorded now, #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 is running. On 21 November 2026 it was recorded for the first time by Rust Server Trends.
Which region does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 run from?
Nothing about a region comes from #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 54.36.18.143:26893 is the address it uses.
Which Rust version is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 running?
Rust network protocol 2636 and build 127089 on Linux is what #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
On what timetable does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 run its wipes?
The rhythm of #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 cannot yet be told: too few of its wipes are on record. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 41 hours.
Server tags
What do the server tags on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 mean?
The game's server browser reads the tags #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 publishes: gmrust (Game mode): The game mode is standard Rust survival; mp100 (Max players): The server has 100 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2636 (Protocol): To connect, your game must be on the same protocol, 2636; cs127089-84fd9a97663 (Build): The build number is not made public; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^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 #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 appear?
The Rust Server Trends lists that take in #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11 are: 2x Rust servers, listed live and 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 3 days; Gather rate: 2x.
Connecting
How do you connect to #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | MAP WIPED 19/11?
Enter client.connect 54.36.18.143:26893 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. https://team-outplay.wixsite.com/outplay-tm is where its website lives.
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.