DWG RG-S7488Server sheetchecked 1d ago
Pulse Testing
Offline OC · au1 168.100.162.88:28015 checked 1d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 34% of all ranked servers, top 70% in OC. Ranked on player hours over the last seven days.
World resets
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 27 Oct, 08:47 UTC2d ago | – | – | – | 0 |
| Tue 27 Oct, 08:27 UTC2d ago | – | – | – | 0 |
| Tue 27 Oct, 08:19 UTC2d ago | – | – | – | 1 |
| Tue 27 Oct, 08:12 UTC2d ago | – | – | – | 1 |
| Tue 27 Oct, 07:59 UTC2d ago | – | – | – | 0 |
| Tue 27 Oct, 07:39 UTC2d ago | – | – | – | 1 |
| Tue 27 Oct, 07:25 UTC2d ago | – | – | – | 1 |
| Tue 27 Oct, 07:03 UTC2d ago | – | – | – | 1 |
| Tue 27 Oct, 01:06 UTC2d ago | – | – | – | 0 |
Similar servers
Quick answers
Recorded details
What uptime is recorded for Pulse Testing, and is it up?
The current state of Pulse Testing is offline, with the last sighting 25 hours ago. About 10 hours ago is when it last restarted, measured from the uptime it reports. For the last 2 full days the record is 22 of 48 hours up, 46% of the time. On 26 October 2026 is when Rust Graphs first saw it.
Is Pulse Testing stable in the figures recorded?
Average server fps over the last 48 hours is 30; the lowest was 30. Counted at its highest: 31,297 entities, buildings, deployables and the rest of the world included. 1,639 MB is the memory peak. Players feel low fps and a climbing entity count as lag.
In which location is Pulse Testing hosted?
In Oceania, Pulse Testing appears with the OC tag; the region code given is au1. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 168.100.162.88:28015.
What Rust version is recorded for Pulse Testing?
Rust network protocol 2635 and build 168909 on Linux: that is what Pulse Testing runs. The same protocol is required for joining, and Steam updates your game to it.
Counts
What player count is recorded on Pulse Testing?
The latest refresh records Pulse Testing as offline, last seen 25 hours ago. The seven-day mean is 1 players; the peak over the same period is 3. The 48-hour peak falls at 09:00 UTC, averaging 1 players.
What rank has been recorded for Pulse Testing?
Across seven days, player hours give Pulse Testing #7,488 globally and #150 in Oceania, a top 34% position among ranked servers.
Wipe times
Which times and days are wipes plotted at on Pulse Testing?
No wipe schedule is kept for Pulse Testing. The world is replaced every few hours, and such resets are not wipes.
Map and rules
Which settings does Pulse Testing run, and what rules?
No gather rate is stated in the name of Pulse Testing. 16 players is the published group limit. It runs the survival game mode, the standard game: gather, build, raid. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Oxide plugins are run on it. VAC is on: that is Valve's anti-cheat.
What is the map for Pulse Testing?
Pulse Testing runs a procedural map of size 3,000 with seed 1, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Tags
On Rust Graphs, which lists and filters contain Pulse Testing?
The Rust Graphs lists that carry Pulse Testing are: Oceania servers, plotted and Modded Rust servers. On the server list, these filters bring it up: 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 meaning is attached to each tag on Pulse Testing?
The game's server browser reads these tags from Pulse Testing: gmrust (Game mode): Standard survival, as Rust plays; mp40 (Max players): 40 player slots; ts16 (Group limit): The team limit is 16; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $rau1 (Region code): Region code: au1; ^w (Weekly): Every week it wipes; ^o (Oxide): The plugin framework is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; OC (Oceania): The server browser lists it under Oceania. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Which operator runs Pulse Testing?
The same operator most likely runs Pulse Testing and 1 other server we track, since all publish a pulserust.net hostname.
Connect
How is Pulse Testing joined?
Enter client.connect 168.100.162.88:28015 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you. https://pulserust.net/ is its website.
Server tags
Published as mp40,ptrak,$rau1,v2635,^w,OC,gmrust,cs168909,ts16,^o^z
Game
gmrust
mp40
ts16
v2635
cs168909
ptrak
$rau1
Wipe schedule
^w
Mods and access
^o
^z
Region
OC
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.