Offline 187.15.104.106:28021 checked 40d ago

Test Server RaidSim

moddedoxide

Connect

srv = rust.server("187.15.104.106:28023")
print(srv.connect_command)

Launch Rust and join

Right now

srv.summary()

players now 0/3 # 0% full

7-day average 0 # peak –

rank #15,406 # no region published

last wipe 41d ago # no schedule published

next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")

No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")

This server has not answered a direct query in the last 48 hours.

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 best

srv.rank.plot(invert=True)  # 1 is best

RankRank in region

Wipe schedule

srv.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

srv.wipes.head(20)

	wiped	peak	crowd	lasted	players_before
	datetime64[UTC]	int64	object	timedelta	int64
Empty DataFrame · no wipe seen yet.

# 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

Custom map, no picture published

map: discord.gg/raidsim
size: –
seed: –

Server

srv.info()

<class 'rust.Server'>
Index: 8 entries, address to first_seen

address: 187.15.104.106:28021
region: –
max players: 3
group limit: 100 max
wipe schedule: –
last wipe: 18 Sep 2026, 15:02 UTC
hostname: –
first seen: 18 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)

	server	like_this	players
0	ShockRust \| Blue \| NoLimit	no group limit · 149 on average	180/500
1	МИНИ-КАРТА 2Х \| STORM \| FPS+ 28.10	EU · groups of 8+ · weekly · 128 on average	121/100
2	RETRO RUST #1 Х1000\|NOLIMIT\|LOOT++\|KIT WIPE 27.10	EU · groups of 16+ · weekly · 118 on average	177/225
3	404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|EU MAIN 25.10	EU · groups of 16+ · monthly · 94 on average	87/700
4	RustSpain.com \| EU Main	EU · groups of 12+ · weekly · 86 on average	237/200
5	404 RUST 2Х\|ДЛЯ НОВИЧКОВ\|СИБИРСКИЙ 27.10	EU · groups of 16+ · monthly · 86 on average	233/700

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does Test Server RaidSim rank?

Over the last seven days Test Server RaidSim sits at #15,406 on player hours, in the top – of ranked servers.

How full does Test Server RaidSim run?

Test Server RaidSim returns no live count at this refresh, having last been seen 40 days 21 hours ago.

Server facts

What is the Rust version on Test Server RaidSim?

Rust network protocol 2633 and build 162929 on Windows is what Test Server RaidSim runs. Steam updates your game for you, but the protocol must match to join.

Is Test Server RaidSim up, and what does its uptime show?

Offline now for Test Server RaidSim, last seen 40 days 21 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 18 September 2026.

Which location does Test Server RaidSim run from?

For Test Server RaidSim, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 187.15.104.106:28021 is its address.

Settings and map

Which settings and rules does Test Server RaidSim run?

No gather rate appears in the name: Test Server RaidSim. 100 players is the maximum per group. Recorded as survival, 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. Oxide plugins run on it. Anti-cheat status: VAC on.

Wipes and dates

When does Test Server RaidSim wipe, and on what schedule?

Too few wipes are on record for Test Server RaidSim to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 41 days ago.

Tags and filters

Which lists on Rust Data hold Test Server RaidSim, and which filters?

The Rust Data lists that Test Server RaidSim fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on Test Server RaidSim?

The game's server browser reads these tags from Test Server RaidSim: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): The server lists 3 slots; ts100 (Group limit): Team size tops out at 100; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs162929 (Build): Recorded game build: 162929; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way into Test Server RaidSim?

The manual route: launch Rust, F1, then client.connect 187.15.104.106:28021. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

Published as mp3,ptrak,$r?,v2633,gmrust,cs162929,ts100,^o^z

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.