Rust Data

rustdata.spaceservers5.42.223.38:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 5.42.223.38:28015 checked 31d ago

Test server

biweekly wipes vanillamoddedoxide

Connect

srv = rust.server("5.42.223.38:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/128 # 0% full
7-day average 0 # peak –
rank #16,955 # top 71%
last wipe 40d ago # biweekly schedule
next wipe 1d 21h # Fri 30 Oct, 21:50 UTC
display(Image(srv.banner))

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, 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 best
RankRank in region
15k10k15k20k20 Sep23 Sep26 Sep28 Sep1 Oct4 Oct

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

Wipe schedule · from its schedule tag

srv.wipe_schedule()

Next wipe Friday 30 October, 21:50 UTC, in 1d 21h. # Its biweekly schedule tag · low confidence

wipe-day peak1players, last three wipes

Coming wipes

inatkind
01d 21hFri 30 Oct, 21:50 UTCwipe
17d 19hThu 5 Nov, 19:00 UTCFW force wipe
215d 21hFri 13 Nov, 21:50 UTCwipe
329d 21hFri 27 Nov, 21:50 UTCwipe
435d 19hThu 3 Dec, 19:00 UTCFW force wipe
543d 21hFri 11 Dec, 21:50 UTCwipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 18 Sep, 21:50 UTC40d ago 1 NaN running 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

3250 · seed 1049736
No map picture published
map
Procedural Map
size
3250
seed
1049736
Open on RustMaps

Server

srv.info()
address
5.42.223.38:28015
region
–
max players
128
group limit
8, the default
wipe schedule
biweekly
last wipe
18 Sep 2026, 21:50 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)
serverlike_thisplayers
0Friendly Seattle: No KOS | Chill | Noob FriendlyNA · groups of 8+ · biweekly · 40 on average48/100
1[JP]初心者PVPサーバー|RaidTime・ EventsEA · groups of 10+ · biweekly · 17 on average2/100
2СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10EU · groups of 50+ · biweekly · 9 on average3/200
3RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average6/200
4Rust Empires II - Roleplay/RP friendly, Cities, PVE, No KOS outgroups of 8+ · biweekly · 5 on average9/50
5[JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29EA · no group limit · biweekly · 4 on average0/20

Quick answers

From the figures on this page.

Population data

How does Test server compare in the rankings?

Rank #16,955 on seven-day player hours for Test server, within the top 71% of all ranked servers.

What population does Test server carry?

The current row shows Test server offline; the last response was 31 days ago.

Server data

What Rust version does Test server run?

The build is Rust network protocol 2633 and build 164530 on Windows, run by Test server. The protocol has to match before you can join, and Steam does the updating.

How reliable is Test server, and is it online now?

The latest sample has Test server offline, with a last sighting 31 days ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.

In which location is Test server hosted?

There is no region published for Test server. Rust Data does not look up where the machine stands; it shows where a server says it is. 5.42.223.38:28015 is its address.

Rules, settings, map

Which settings and rules does Test server run?

No gather rate appears in the name: Test server. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Vanilla, by its own description: untouched settings: rates, kits and rules as shipped. Anti-cheat status: VAC on.

Which map has Test server loaded?

Size 3,250, seed 1049736: the procedural map on Test server, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe schedule

When does Test server wipe, and on what schedule?

The tag sets the prediction: Test server has too few wipes on record to confirm its schedule. Friday 30 October at 21:50 UTC is when the next wipe is due. The world it runs now was generated 40 days 2 hours ago. Its tags carry a wipe schedule of every two weeks.

On Test server, what happens on wipe day?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 16 hours after it began.

Tags, lists

Where does Test server appear among Rust Data lists and filters?

These Rust Data lists include Test server: Modded Rust servers. It appears under these filters on the server list: Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.

Which meanings do the tags on Test server hold?

The game's server browser reads these tags from Test server: gmrust (Game mode): Rust survival in its standard form; mp128 (Max players): Slot count: 128; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): Recorded game build: 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^b (Biweekly): Wipes run on a two-week cycle; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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?

Enter client.connect 5.42.223.38:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp128,ptrak,$r?,v2633,^b,^v,gmrust,cs164530,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp128
Max players Slot count: 128.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs164530
Build Recorded game build: 164530.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^b
Biweekly Wipes run on a two-week cycle.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits under Modded.

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.

Rust Data 51,299 players 11,732 servers online