Station XX-16275 · no signal
Pulse isolated staging compatibility test
Offline 84.203.49.238:28775 checked 28d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,275
- top 69%
- Last wipe
- 28d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 slots
- Motion · 24 h
- M –not enough readings
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which map is running on Pulse isolated staging compatibility test?
A procedural map runs on Pulse isolated staging compatibility test, generated by the game.
Which settings and rules apply on Pulse isolated staging compatibility test?
No gather rate appears in the name of Pulse isolated staging compatibility test. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched off.
Live population
How many players are recorded on Pulse isolated staging compatibility test right now?
No players are recorded on Pulse isolated staging compatibility test at this moment; it is offline, and the last sighting was 28 days 3 hours ago.
How does Pulse isolated staging compatibility test rank against other Rust servers?
The last seven days of player hours place Pulse isolated staging compatibility test at #16,275, in the top 69% of all ranked servers.
Operator and location
How reliably does Pulse isolated staging compatibility test stay online?
As recorded now, Pulse isolated staging compatibility test is not reachable, the last contact having been 28 days 3 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 1 October 2026.
Which region does Pulse isolated staging compatibility test run from?
A region is not published by Pulse isolated staging compatibility test. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 84.203.49.238:28775.
Which Rust version is Pulse isolated staging compatibility test running?
Pulse isolated staging compatibility test is running Rust network protocol 2634 and build 166493 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
On what timetable does Pulse isolated staging compatibility test run its wipes?
On record so far are too few of Pulse isolated staging compatibility test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 28 days 3 hours.
Server tags
What do the server tags on Pulse isolated staging compatibility test mean?
These are the tags Pulse isolated staging compatibility test publishes for the browser to read: gmrust (Game mode): You'll find standard Rust survival here; mp2 (Max players): Slots: 2; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166493 (Build): It runs game build 166493; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Pulse isolated staging compatibility test appear?
The Rust Server Trends lists that take in Pulse isolated staging compatibility test are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
What steps get you onto Pulse isolated staging compatibility test?
To join, enter client.connect 84.203.49.238:28775 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.