#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10
Online 57.128.5.43:20003 checked 10m ago
Server instruments
last reading Thu 16:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 30 · below 20 is lag, below 10 is badEntities
48 h range 116,443–134,303 · memory 3,528 MBUptime
8 h 57 min since its last restart, at the last readingPlayers
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 55% 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.
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 | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 21:47 UTC5d ago | 1 | – | running | 0 |
| Mon 12 Oct, 09:21 UTC17d ago | 1 | halved by day 1 | 11.5 days | 0 |
Peak: the most players in the first 48 hours. 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 wipes- 788/850
- 1,200/1200
- 152/200
- 799/845
- 844/960
- 150/1000
Quick answers
from the figures on this pageWipe schedule
What happens on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 when wipe day comes?
The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 2 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 1 it fell below half when it didn't.
What wipe timing does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 follow?
To tell the rhythm of #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 5 days 20 hours ago.
Tag meanings
Which tags does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 carry, and what do they mean?
Tags published by #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs167398 (Build): The server runs game build 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Rust Metrics lists featuring #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10: 2x Rust servers, checked live and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.
Population
Where does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 sit in the rankings?
Ranking for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10: #12,306 on seven-day player hours, top 55% of all ranked servers.
What player count does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 carry?
Current headcount on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10: 0 players, 100 slots available. Seven-day check: 0 players on average. Peak reading: 1.
Operator and location
Where does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 sit?
Reading: location. #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 57.128.5.43:20003.
What Rust version is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 on?
Version check: Rust network protocol 2635 and build 167398 on Windows, run by #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Check: fps. Average 30 server fps over the last 48 hours, low of 30. Within range. Check: entities. The peak was 134,303, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 4,026 MB. Expect lag when fps falls and entities climb.
Is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 up, and how often does it stay up?
Reading: online. #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 answers right now. Check: restart. The uptime it reports puts the last restart about 8 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 13 September 2026.
Settings and map
What settings and rules apply on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Gather rate check: 2x. That comes from the name #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
What map is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 on?
Check: map. Procedural, size 4,500, seed 450159596, generated by the game on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
What do you do to join #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Press F1 in Rust and enter client.connect 57.128.5.43:20003. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://team-outplay.wixsite.com/outplay-tm is where its website sits.