Rust Server IndexCard catalogue of Rust servers

Holdings11,876 servers94,650 players154 fresh wipes

Call no.2X12318 On the shelf · online

#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10

Online 57.128.5.43:20003 checked 14m ago

Subjects 1. 2x 2. modded3. oxide
Players now
0/ 100
0% full
7-day average
0
peak 1
Rank
#12,318
top 56%
Last wipeWiped23 OCT2026 · 3d 21h ago
3d ago · no schedule published
Next wipe
–
too few wipes seen yet
Call slipPaste it into the F1 console
Record sheet A · appended

Players

AveragePeak
00.250.50.75120:0005:0014:0023:0008:0017:00

Hourly average and peak, UTC.

Record sheet B · appended

Server performance

01020304020:0005:0014:0023:0008:0017:00

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.

Record sheet C · appended

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct13 Oct20 Oct27 Oct

Top 56% of all ranked servers. Ranked on player hours over the last seven days.

Record sheet D · loan terms

Wipe schedule

too few wipes seen yet

Not 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

Fri 23 OctMon 12 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

Record sheet E · date due

Wipes

newest first
WipedPeakCrowdLastedPlayers before
23 OCT 2026Fri 23 Oct, 21:47 UTC3d ago
1 – running 0
12 OCT 2026Mon 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.

Shelf list · shelved beside it

Similar servers

The same kind of game, then region, group limit, rate and wipes.

EU2X
Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 697 on average
904/ 1000
EU2X
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 520 on average
747/ 800
NA2X
Atlas - US 2X Monthly | Vanilla+ | No BP WipesNA · groups of 16+ · 2x · monthly · 340 on average
201/ 200
EU2X
Magic Rust #18 — Vanilla 2x | PyccкийEU · groups of 150+ · 2x · weekly · 322 on average
41/ 100
EU2X
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 312 on average
426/ 475
EU2X
Vitality - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 292 on average
163/ 250
Reference desk

Quick answers

From the figures on this page.

Map and rules

Where can you read the rules and settings that apply on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

Filed under gather rates: 2x, as the name of #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 states. The default group limit of 8 players applies. Filed under survival, gather, build and raid: the standard game. Fighting and raiding other players is permitted. The server browser lists it under Modded; plugins or settings alter the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.

Which map is in use on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 runs a procedural map of size 4,500 with seed 450159596, generated by the game. The map can be seen on RustMaps from this page, because the same size and seed give the same map.

Tags

Where does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 appear among the Rust Server Index lists and filters?

The Rust Server Index lists that include #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 are Rust servers filed under 2x gather rate and Modded Rust servers, filed by play style. Filed 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 tags listed for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

The server's own tags are listed here, and the game's server browser reads them: #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 gives gmrust (Game mode): Rust survival, as standard; mp100 (Max players): The queue ceiling sits at 100; ts8 (Group limit): Teams cap at 8, the default setting; v2635 (Protocol): The protocol is 2635; older or newer clients cannot join; cs167398 (Build): Build on file: 167398; ptrak (Networking): Networking runs on RakNet, the game's default layer; $r? (Region code): A region code is absent; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Modded: the game is changed by plugins or settings. Current players, queue length and when the world was made appear in the tags, set out at the top of this page.

Wipes and resets

How does a wipe day run on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

At their busiest, its recent wipes drew 1 players on average. 2 hours into the latest wipe, the crowd reached its peak. Its recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the other cases, numbers dropped below half by day 1.

Which wipe timetable does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 follow?

#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10's rhythm cannot be told yet: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 3 days 21 hours is when its current world was made.

Players and ranking

Where does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 sit in the rankings?

The seven-day player-hours ranking places #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 at #12,318, among the top 56% of ranked servers.

What does the player count on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 look like?

The live count for #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 stands at 0 players, out of 100 slots. Averaged across seven days: 0 players, peaking at 1. Over the last 48 hours, 16:00 UTC drew the highest average: 1 players.

Server facts

What version does #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 use?

Rust network protocol 2635 and build 167398 on Windows is what you will find on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10. Steam keeps your game updated, but the protocol must match for you to join.

What is the uptime and current status of #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

Right now #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 is up and running. Its reported uptime gives the last restart as roughly 4 hours ago. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. On 13 September 2026 it was first seen by Rust Server Index.

Is the performance on #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 good?

Averaged over the last 48 hours, server fps was 30, with a low of 29. The entity count reached 119,392, covering buildings, deployables and all else in the world. Memory use reached as much as 3,527 MB. Lag, to players, is low fps and an entity count that climbs.

What is the location of #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

#1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10 gives no region at all. No lookup of the machine's position is made by Rust Server Index; it shows where the server says it is. You will reach it at 57.128.5.43:20003.

Joining the server

What steps lead onto #1 OuTPlay | X2 | Raidable Bases | Bi-Weekly | Full WIPED 23/10?

Enter client.connect 57.128.5.43:20003 in the console, opened with F1. Or join on this page with Launch Rust, which opens Rust through Steam and connects you. You will find its website at https://team-outplay.wixsite.com/outplay-tm.

Subject headings explained

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2635,gmrust,cs167398,ts8,^o^z

Game

gmrust
Game mode Rust survival, as standard.
mp100
Max players The queue ceiling sits at 100.
ts8
Group limit Teams cap at 8, the default setting.
v2635
Protocol The protocol is 2635; older or newer clients cannot join.
cs167398
Build Build on file: 167398.
ptrak
Networking Networking runs on RakNet, the game's default layer.
$r?
Region code A region code is absent.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded Modded: the game is changed by plugins or settings.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.