Rust Data

rustdata.spaceservers4.148.0.37:28017.ipynb

Run all rust-data · live

‹ All servers

Online 4.148.0.37:28015 checked 12m ago

ZeroRust | 20 Max | Raid Windows

moddedcarbon

Connect

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

Right now

srv.summary()
players now 0/20 # 0% full
7-day average 0 # peak –
rank #15,411 # top 69%
last wipe 17d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123402:0011:0020:0006:0015:0000:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040002:0011:0020:0006:0015:0000: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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.

wipe-day peak0players, last three wipes

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 0, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 10 Oct, 06:05 UTC17d ago 0 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

3500 · seed 2010147616
No map picture published
map
Procedural Map
size
3500
seed
2010147616
Open on RustMaps

Server

srv.info()
address
4.148.0.37:28015
region
–
max players
20
group limit
8, the default
wipe schedule
–
last wipe
10 Oct 2026, 06:05 UTC
hostname
–
first seen
13 Sep 2026

About this server · in its own words

print(srv.description)
20-player casual Rust. Normal raiding: 4 PM-midnight Pacific. Protected hours: midnight-4 PM Pacific, with 2x/1.5x/1.25x raid cost in wipe weeks 1/2/3. Use /raidstatus.

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 161 on average26/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average125/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average35/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average33/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average9/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average10/1000

Quick answers

From the figures on this page.

Player counts

What position does ZeroRust | 20 Max | Raid Windows take in the server rankings?

Over the last seven days ZeroRust | 20 Max | Raid Windows sits at #15,411 on player hours, in the top 69% of ranked servers.

What population does ZeroRust | 20 Max | Raid Windows carry?

ZeroRust | 20 Max | Raid Windows reports 0 players at this refresh, with 20 slots configured. Over the last seven days it averaged 0 players.

Server facts

What does performance look like on ZeroRust | 20 Max | Raid Windows?

The 48-hour average is 172 server fps, with a low of 119. Buildings, deployables and all else in the world took the count as high as 68,721 entities. Memory peaked at 5,203 MB. Low fps plus an entity count on the way up is the lag players report.

What Rust version does ZeroRust | 20 Max | Raid Windows run?

Rust network protocol 2634 and build 167398 on Linux is what ZeroRust | 20 Max | Raid Windows runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is ZeroRust | 20 Max | Raid Windows, and is it online now?

ZeroRust | 20 Max | Raid Windows reports itself online at the current refresh. The uptime it reports puts the last restart about 17 days 18 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 13 September 2026.

Where does ZeroRust | 20 Max | Raid Windows sit?

For ZeroRust | 20 Max | Raid Windows, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 4.148.0.37:28015 is its address.

Rules, settings, map

Which settings and rules does ZeroRust | 20 Max | Raid Windows run?

No gather rate appears in the name: ZeroRust | 20 Max | Raid Windows. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Carbon. Anti-cheat status: VAC on.

Which map has ZeroRust | 20 Max | Raid Windows loaded?

Size 3,500, seed 2010147616: the procedural map on ZeroRust | 20 Max | Raid Windows, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does ZeroRust | 20 Max | Raid Windows wipe, and how often?

The record for ZeroRust | 20 Max | Raid Windows holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 17 days 19 hours ago.

What is wipe day on ZeroRust | 20 Max | Raid Windows like?

The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which lists on Rust Data hold ZeroRust | 20 Max | Raid Windows, and which filters?

On Rust Data, ZeroRust | 20 Max | Raid Windows appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Which meanings do the tags on ZeroRust | 20 Max | Raid Windows hold?

These tags are published by ZeroRust | 20 Max | Raid Windows and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): 20 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Build number: 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way into ZeroRust | 20 Max | Raid Windows?

In Rust, F1 opens the console: type client.connect 4.148.0.37:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp20,ptrak,$r?,v2634,gmrust,cs167398,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp20
Max players 20 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Build number: 167398.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon The plugin framework in use is Carbon.

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 44,124 players 11,668 servers online