Offline 103.70.0.60:10000 checked 22d ago
Recore-VIP V2
Connect
srv = rust.server("103.70.0.60:10003")
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, measured since 17 Sep. 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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h. # 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
4096 · seed 1
- map
- Custom Map
- size
- 4096
- seed
- 1
Server
srv.info()- address
- 103.70.0.60:10000
- region
- –
- max players
- 40
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 4 Sep 2026, 15:53 UTC
- hostname
- –
- first seen
- 13 Sep 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 98/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 26/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 75 on average | 219/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 68 on average | 134/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 67 on average | 8/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 59 on average | 368/1000 |
Quick answers
From the figures on this page.
Population data
How does Recore-VIP V2 compare in the rankings?
Player hours over seven days put Recore-VIP V2 at #15,945, in the top 71% of the ranked set.
How many players does Recore-VIP V2 hold at once?
The current row shows Recore-VIP V2 offline; the last response was 22 days 16 hours ago.
Server facts
What Rust version does Recore-VIP V2 run?
The build is Rust network protocol 2633 and build 164530 on Linux, run by Recore-VIP V2. Steam updates your game for you, but the protocol must match to join.
How reliable is Recore-VIP V2, and is it up?
The latest sample has Recore-VIP V2 offline, with a last sighting 22 days 16 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 13 September 2026.
Where does Recore-VIP V2 sit?
There is no region published for Recore-VIP V2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 103.70.0.60:10000.
Rules, settings, map
What rules and settings are recorded for Recore-VIP V2?
You will not find a gather rate in the string Recore-VIP V2. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat status: VAC on.
Which map has Recore-VIP V2 selected?
The game generates the map on Recore-VIP V2: procedural, size 4,096, seed 1. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipe schedule
When does Recore-VIP V2 wipe, and on what schedule?
The next wipe for Recore-VIP V2 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. A new world was started 54 days 5 hours ago, and that is the one in play. A monthly wipe schedule is published in its tags.
Lists and tags
Which lists on Rust Data hold Recore-VIP V2, and which filters?
These Rust Data lists include Recore-VIP V2: Modded Rust servers. It appears under these filters on the server list: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Which meanings do the tags on Recore-VIP V2 hold?
The game's server browser reads these tags from Recore-VIP V2: gmrust (Game mode): Survival play, standard Rust; mp40 (Max players): 40 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs164530 (Build): Build number: 164530; 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): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into Recore-VIP V2?
Enter client.connect 103.70.0.60:10000 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.