Offline 84.203.49.238:28775 checked 27d ago
Pulse isolated staging compatibility test
Connect
srv = rust.server("84.203.49.238:28777")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 84.203.49.238:28775
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:14 UTC
- hostname
- –
- first seen
- 1 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 151/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 96/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 88 on average | 234/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Population
What position does Pulse isolated staging compatibility test take in the server rankings?
Over the last seven days Pulse isolated staging compatibility test sits at #16,275 on player hours, in the top 69% of ranked servers.
What population does Pulse isolated staging compatibility test carry?
Pulse isolated staging compatibility test returns no live count at this refresh, having last been seen 27 days 23 hours ago.
Server data
What is the Rust version on Pulse isolated staging compatibility test?
Version Rust network protocol 2634 and build 166493 on Windows is reported by Pulse isolated staging compatibility test. Steam updates your game for you, but the protocol must match to join.
How reliable is Pulse isolated staging compatibility test, and is it up?
Pulse isolated staging compatibility test is offline at this refresh; the last response came 27 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 1 October 2026.
Where does Pulse isolated staging compatibility test sit?
For Pulse isolated staging compatibility test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 84.203.49.238:28775 is its address.
Settings and map
Which rules apply on Pulse isolated staging compatibility test, and what settings?
You will not find a gather rate in the string Pulse isolated staging compatibility test. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. The VAC field reads off.
Which map has Pulse isolated staging compatibility test loaded?
The game generates its map: procedural, on Pulse isolated staging compatibility test.
Wipe schedule
On what schedule does Pulse isolated staging compatibility test wipe?
A rhythm cannot be read from the wipes of Pulse isolated staging compatibility test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 28 days ago, and that is the one in play.
Tags and filters
Which lists on Rust Data hold Pulse isolated staging compatibility test, and which filters?
These Rust Data lists include Pulse isolated staging compatibility test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on Pulse isolated staging compatibility test?
These tags are published by Pulse isolated staging compatibility test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166493 (Build): The server runs build 166493; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Pulse isolated staging compatibility test?
Enter client.connect 84.203.49.238:28775 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.