Online 57.128.5.43:20003 checked 12m ago
#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10
Connect
srv = rust.server("57.128.5.43:20002")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 56% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not 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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 23 Oct, 21:47 UTC4d ago | 1 | NaN | running | 0 |
| 1 | Mon 12 Oct, 09:21 UTC15d 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.
display(srv.map, srv.info())Map
4500 · seed 450159596
- map
- Procedural Map
- size
- 4500
- seed
- 450159596
Server
srv.info()- address
- 57.128.5.43:20003
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 21:47 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 734 on average | 640/600 |
| 1 | Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes | EU · groups of 16+ · 2x · monthly · 548 on average | 415/375 |
| 2 | Atlas - US 2X Monthly | Vanilla+ | No BP Wipes | NA · groups of 16+ · 2x · monthly · 354 on average | 125/150 |
| 3 | EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr | EU · groups of 50+ · 2x · monthly · 326 on average | 138/150 |
| 4 | Magic Rust #18 — Vanilla 2x | Pyccкий | EU · groups of 150+ · 2x · weekly · 323 on average | 46/100 |
| 5 | MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 | EU · groups of 300+ · 2x · weekly · 299 on average | 211/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 rank?
Player hours over seven days put #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 at #12,385, in the top 56% of the ranked set.
How many players does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 hold at once?
#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 16:00 UTC, mean 1 players.
About the server
What does performance look like on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
The 48-hour average is 30 server fps, with a low of 29. Entity numbers reached 124,645, and that includes buildings, deployables and the rest. A high of 3,670 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Rust network protocol 2635 and build 167398 on Windows is what #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10, and is it online now?
Online is the state at the latest refresh for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. A restart about 1 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Rust Data logged it first on 13 September 2026.
Which location does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 run from?
There is no region published for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 57.128.5.43:20003 is its address.
Settings and map
Which settings and rules does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 run?
2x gather is what the name states, and the name is #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 loaded?
Size 4,500, seed 450159596: the procedural map on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe schedule
When does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 wipe, and how often?
Too few wipes are on record for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 4 days 11 hours ago.
On #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10, what happens on wipe day?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 2 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. The drop under half arrived by day 1 in the other cases.
Tags and filters
Which Rust Data filters and lists contain #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
The Rust Data lists that #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 fits are: Modded Rust servers and 2x Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week; Gather rate: 2x.
How should you read the server tags on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
Read by the game's server browser, the tags #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 publishes are: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
What is the way to join #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?
In Rust, F1 opens the console: type client.connect 57.128.5.43:20003. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://team-outplay.wixsite.com/outplay-tm.