Pulse Testing
Online OC · au1 168.100.162.88:28015 checked 9m ago
Server instruments
last reading Wed 11:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 30 · below 20 is lag, below 10 is badEntities
48 h range 31,155–31,297 · memory 1,544 MBUptime
10 h 51 min since its last restart, at the last readingPlayers
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
daily · 1 is bestTop 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| 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 UTC3d ago | – | – | – | 0 |
Similar servers
the same kind of game, then region, group limit, rate and wipes- 140/300
- 152/300
- 51/100
- 0/3300
- 2/300
- 1/50
Quick answers
from the figures on this pageWipe timing
When does Pulse Testing wipe?
No wipe schedule is kept by Pulse Testing, which makes a new world every few hours; those resets do not count as wipes.
Tag meanings
How should you read the tags on Pulse Testing?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): Slots: 40; ts16 (Group limit): Team cap: 16; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $rau1 (Region code): Region code reading: au1; ^w (Weekly): Wipe cycle: weekly; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; OC (Oceania): Oceania is the browser category it sits in from Pulse Testing. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Who operates Pulse Testing?
Most likely the same operator runs both: Pulse Testing publishes a pulserust.net hostname, and 1 other server we track does the same.
Where does Pulse Testing appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Pulse Testing: Rust servers in Oceania and Modded Rust servers, checked live. Check: filters. On the server list it appears under these: 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.
Population
What position does Pulse Testing hold among Rust servers?
Top 34% of all ranked servers: Pulse Testing takes #7,510 on seven-day player hours and #151 in Oceania.
What is the population on Pulse Testing?
Current headcount on Pulse Testing: 0 players, 40 slots available. Seven-day check: 1 players on average. Peak reading: 3. Average at the busiest hour was 1 players, at 09:00 UTC over the last 48 hours.
Server details
Where does Pulse Testing sit?
The OC tag puts Pulse Testing in Oceania, and its region code is au1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 168.100.162.88:28015.
What Rust version is Pulse Testing on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Pulse Testing. Matching protocol is required to join. Let Steam update your game.
What is the performance reading for Pulse Testing?
Check: fps. Average 30 server fps over the last 48 hours, low of 30. Within range. Reading: 31,297 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 1,639 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is Pulse Testing, and is it online now?
Pulse Testing reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 10 hours ago. Uptime for the last 3 full days: 22 of 72 hours, or 31%. Check: first contact. Rust Metrics logged it on 26 October 2026.
Settings and map
How is Pulse Testing configured, and what rules are in force?
No gather rate appears in the name: Pulse Testing. Group size, maximum: 16 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. VAC is on. That is Valve's anti-cheat.
What map is Pulse Testing on?
Check: map. Procedural, size 3,000, seed 1, generated by the game on Pulse Testing. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How can you get onto Pulse Testing?
Check: join. Open Rust, press F1, then enter client.connect 168.100.162.88:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://pulserust.net/ is where its website sits.