Station XX-12318 · recording
#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10
Online 57.128.5.43:20003 checked 14m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak 1
- Rank
- #12,318
- top 56%
- Last wipe
- 3d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- −1into Mon 17:00 UTC
- Peak · 48 h
- 1most players in any hour
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 56% 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
- 11.5 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, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 23 Oct, 21:47 UTC3d ago | M0.0▲rising | 1 | – | running | 0 | |
| Mon 12 Oct, 09:21 UTC15d ago | M0.0▲rising | 1 | halved by day 1 | 11.5 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 pageServer rules
Which map is running on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Generated by the game, the map on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 is procedural, size 4,500 with seed 450159596. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
2x gather is what #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 runs, judging by its name. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Live population
What is the current population on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
0 of the 100 slots on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 are filled right now. The seven-day average is 0 players, with a peak of 1. Averaged over the last 48 hours, the busiest hour was 16:00 UTC at 1 players.
How does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 rank against other Rust servers?
The last seven days of player hours place #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 at #12,318, in the top 56% of all ranked servers.
Server facts
How reliably does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 stay online?
#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 is up at the moment. Going by the uptime figure it reports, it restarted about 4 hours ago. 168 of 168 hours in the last 7 full days were up time, 100% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
How well does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 perform under load?
Its average server fps over the last 48 hours was 30, and it never dropped below 29. Buildings, deployables and all the rest of the world's entities brought it to a high of 119,392. Memory use peaked at 3,527 MB. What you feel as lag is the combination of low fps and a rising entity count.
Where in the world is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 hosted?
No region is published by #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. 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 57.128.5.43:20003.
What build of Rust does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 use?
#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 is running Rust network protocol 2635 and build 167398 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
On average, the busiest point of its recent wipes drew 1 players. 2 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
How often does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 wipe, and on which days?
Too few wipes of #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 3 days 21 hours.
Lists and tags
What do the server tags on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 mean?
Tags published by #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp100 (Max players): The server has 100 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs167398 (Build): It runs game build 167398; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 | Full WIPED 23/10 appear?
These Rust Server Trends lists include #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10: 2x Rust servers, listed live and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.
How to join
How do you connect to #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Enter client.connect 57.128.5.43:20003 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you. You can find its website at https://team-outplay.wixsite.com/outplay-tm.
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.