Rust Data

rustdata.spaceservers168.100.162.88:28013.ipynb

Run all rust-data · live

‹ All servers

Offline OC · au1 168.100.162.88:28015 checked 1d ago

Pulse Testing

weekly wipes moddedoxide

Connect

srv = rust.server("168.100.162.88:28013")
print(srv.connect_command)

Right now

srv.summary()
players now 1/40 # 2% full
7-day average 1 # peak 3
rank #7,489 # top 34% · #150 in OC
no wipes 'resets' # 9 new worlds this week: a reset every few hours, not a wipe schedule
next wipe – # resets, no wipes

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5223:0001:0004:0006:0009:0011:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304023:0001:0004:0006:0009:0011: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 27 Oct. 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
12.5k5k7.5k10k27 Oct28 Oct29 Oct

Top 34% of all ranked servers, top 70% in OC. Ranked on player hours over the last seven days.

World resets · a new world every few hours; none of these counts as a wipe

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 08:47 UTC2d ago NaN NaN NaN 0
1 Tue 27 Oct, 08:27 UTC2d ago NaN NaN NaN 0
2 Tue 27 Oct, 08:19 UTC2d ago NaN NaN NaN 1
3 Tue 27 Oct, 08:12 UTC2d ago NaN NaN NaN 1
4 Tue 27 Oct, 07:59 UTC2d ago NaN NaN NaN 0
5 Tue 27 Oct, 07:39 UTC2d ago NaN NaN NaN 1
6 Tue 27 Oct, 07:25 UTC2d ago NaN NaN NaN 1
7 Tue 27 Oct, 07:03 UTC2d ago NaN NaN NaN 1
8 Tue 27 Oct, 01:06 UTC2d ago NaN NaN NaN 0
display(srv.map, srv.info())

Map

3000 · seed 1
Map of Pulse Testing
map
Procedural Map
size
3000
seed
1
Open on RustMaps

Server

srv.info()
address
168.100.162.88:28015
region
OC · au1
max players
40
group limit
16 max
wipe schedule
weekly
last wipe
resets constantly
hostname
au.pulserust.net
first seen
26 Oct 2026

Operator · pulserust.net

rust.servers(operator="pulserust.net").sort_values("players")

2 servers publish a pulserust.net hostname.

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

rust.similar(srv).head(6)
serverlike_thisplayers
0РУССКИЙ ДЛЯ НОВИЧКОВ | WIPE 29.10EU · groups of 8+ · weekly · 108 on average165/300
1РОССИЙСКИЙ ДЛЯ НОВИЧКОВ | WIPE 29.10EU · groups of 8+ · weekly · 111 on average162/300
2RaidLabgroups of 8+ · 32 on average200/50
3EU Hub 01EU · groups of 1000+ · 24 on average3/3300
4404 RUST /ДЛЯ НОВИЧКОВ /МОСКОВСКИЙ 19.10EU · groups of 8+ · monthly · 3 on average3/300
5A Shockbyte Rust Servergroups of 8+ · 2 on average0/40

Quick answers

From the figures on this page.

Player counts

What position does Pulse Testing take in the server rankings?

On seven-day player hours Pulse Testing is #7,489 overall and #150 in Oceania, inside the top 34% of all ranked servers.

What population does Pulse Testing carry?

Offline now for Pulse Testing, with the last sample 27 hours ago. Over the last seven days it averaged 1 players and peaked at 3. Peak hour in the last 48 hours: 09:00 UTC, mean 1 players.

Server data

How smoothly does Pulse Testing run?

Server fps over the last 48 hours averages 30; the floor is 30. Buildings, deployables and all else in the world took the count as high as 31,297 entities. A high of 1,639 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does Pulse Testing run?

Rust network protocol 2635 and build 168909 on Linux is what Pulse Testing runs. Steam updates your game for you, but the protocol must match to join.

Is Pulse Testing up, and what does its uptime show?

The latest sample has Pulse Testing offline, with a last sighting 27 hours ago. A restart about 10 hours ago is what its reported uptime implies. Uptime of 46% across the last 2 full days: 22 hours of 48. Its earliest recorded date in Rust Data is 26 October 2026.

In which location is Pulse Testing hosted?

With its OC tag, Pulse Testing lists itself in Oceania; its region code is au1. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 168.100.162.88:28015 is its address.

Rules, settings, map

Which rules apply on Pulse Testing, and what settings?

The name Pulse Testing carries no gather rate. Group size tops out at 16 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.

Which map has Pulse Testing selected?

The game generates the map on Pulse Testing: procedural, size 3,000, seed 1. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Pulse Testing wipe, and how often?

Pulse Testing starts a fresh world on a few-hour cycle, keeps no wipe schedule, and those resets are not wipes.

Tags, lists

Which lists on Rust Data hold Pulse Testing, and which filters?

The Rust Data lists that Pulse Testing fits are: Oceania Rust servers and Modded Rust servers. Under these filters on the server list, it is listed: Region: Oceania; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 3 days.

Which operator runs Pulse Testing?

The same operator most likely runs Pulse Testing and 1 other server we track, as all publish a pulserust.net hostname.

Which meanings do the tags on Pulse Testing hold?

These tags are published by Pulse Testing and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp40 (Max players): The server lists 40 slots; ts16 (Group limit): The team cap is 16; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $rau1 (Region code): au1 is the region code recorded; ^w (Weekly): The interval is one week; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; OC (Oceania): In the server browser it sits under Oceania. 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.

Join steps

What is the way to join Pulse Testing?

Enter client.connect 168.100.162.88:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://pulserust.net/ is the website recorded for it.

Server tags · what each one means

srv.tags.decode()

Published as mp40,ptrak,$rau1,v2635,^w,OC,gmrust,cs168909,ts16,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp40
Max players The server lists 40 slots.
ts16
Group limit The team cap is 16.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$rau1
Region code au1 is the region code recorded.

Wipe schedule

^w
Weekly The interval is one week.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Region

OC
Oceania In the server browser it sits under Oceania.

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 83,167 players 11,844 servers online