Offline EA 153.246.233.123:38015 checked 25d ago
Isolated save recovery check
Connect
srv = rust.server("153.246.233.123:38017")
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, top 92% in EA. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 12h. # The 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
- 153.246.233.123:38015
- region
- EA
- max players
- –
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 25 Sep 2026, 12:09 UTC
- hostname
- –
- first seen
- 2 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 | Rustoria.co - SEA Long | EA · groups of 12+ · monthly · 109 on average | 62/200 |
| 1 | Rustafied.com - SEA Long | EA · groups of 16+ · monthly · 27 on average | 28/100 |
| 2 | [SEA] Facepunch Premium 1 | EA · groups of 8+ · monthly · 17 on average | 5/250 |
| 3 | [SEA] Facepunch 1 | EA · groups of 8+ · monthly · 13 on average | 8/300 |
| 4 | nomarust LL | JP | Vanilla | Monthly | EA · groups of 8+ · monthly · 2 on average | 1/200 |
| 5 | RustGalaxy Nexus Japan | EA · groups of 100+ · monthly · 2 on average | 4/50 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Isolated save recovery check rank?
Player hours over the last seven days: #15,917 for Isolated save recovery check, #487 in Asia, within the top 69% of the ranked set.
How full does Isolated save recovery check run?
The current row shows Isolated save recovery check offline; the last response was 25 days 22 hours ago.
About the server
What Rust version does Isolated save recovery check run?
The build is Rust network protocol 2634 and build 166586 on Linux, run by Isolated save recovery check. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Isolated save recovery check, and is it up?
The latest sample has Isolated save recovery check offline, with a last sighting 25 days 22 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 2 October 2026.
Where does Isolated save recovery check sit?
In Asia, Isolated save recovery check lists itself, using the EA tag. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 153.246.233.123:38015.
Rules, settings, map
Which settings and rules does Isolated save recovery check run?
You will not find a gather rate in the string Isolated save recovery check. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Community is its browser category. Oxide plugins run on it. The description says vanilla, which here means untouched settings: rates, kits and rules as shipped. VAC is running: Valve's anti-cheat is on.
Which map has Isolated save recovery check selected?
The game generates its map: procedural, on Isolated save recovery check.
Wipe data
On what schedule does Isolated save recovery check wipe?
The next wipe for Isolated save recovery check is an estimate, drawn from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world it runs now was generated 32 days 18 hours ago. Its tags carry a monthly wipe schedule.
Tags, lists
Which Rust Data filters and lists contain Isolated save recovery check?
The Rust Data lists that Isolated save recovery check fits are: Rust community servers, unfiltered and Vanilla Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Monthly ^m, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on Isolated save recovery check?
Read by the game's server browser, the tags Isolated save recovery check publishes are: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Plugin framework: Oxide (uMod); EA (East Asia): The server browser files it under East Asia. 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 Isolated save recovery check?
The manual route: launch Rust, F1, then client.connect 153.246.233.123:38015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.