Offline 63.135.75.101:38115 checked 6d ago
NEXORA verified restart
Connect
srv = rust.server("63.135.75.101:38117")
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 68% 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
- 63.135.75.101:38115
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 09:49 UTC
- hostname
- –
- first seen
- 23 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 | ABYSS | PvE | US | Vanilla | Noob Friendly | NA · groups of 8+ · monthly · 54 on average | 41/200 |
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EU · groups of 8+ · monthly · 31 on average | 28/200 |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 30 on average | 22/200 |
| 3 | [PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly | groups of 8+ · monthly · 22 on average | 16/150 |
| 4 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 7/200 |
| 5 | JP RustPvE kokuu Server No kill No raid beeginner | EA · groups of 8+ · monthly · 15 on average | 4/200 |
Quick answers
From the figures on this page.
Population data
What position does NEXORA verified restart take in the server rankings?
Player hours over seven days put NEXORA verified restart at #15,268, in the top 68% of the ranked set.
What population does NEXORA verified restart carry?
NEXORA verified restart returns no live count at this refresh, having last been seen 6 days 11 hours ago. Over the last seven days it averaged 0 players.
Server facts
What is the Rust version on NEXORA verified restart?
Version Rust network protocol 2634 and build 167781 on Windows is reported by NEXORA verified restart. Steam updates your game for you, but the protocol must match to join.
How reliable is NEXORA verified restart, and is it up?
NEXORA verified restart is offline at this refresh; the last response came 6 days 11 hours ago. Uptime of 0% across the last 5 full days: 0 hours of 120. Rust Data logged it first on 23 October 2026.
Where does NEXORA verified restart sit?
For NEXORA verified restart, no region is published. 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 63.135.75.101:38115.
Settings and map
Which rules apply on NEXORA verified restart, and what settings?
No gather rate appears in the name: NEXORA verified restart. The group limit sits at the default of 8 players. Game mode pve, with this note: player combat is not allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
Which map has NEXORA verified restart selected?
A procedural map runs on NEXORA verified restart, generated by the game.
Wipe data
When does NEXORA verified restart wipe, and on what schedule?
A rhythm cannot be read from the wipes of NEXORA verified restart on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 9 days 11 hours ago.
Tags, lists
Where does NEXORA verified restart appear among Rust Data lists and filters?
The Rust Data lists that NEXORA verified restart fits are: Rust community servers, unfiltered and Rust PvE servers. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on NEXORA verified restart hold?
Read by the game's server browser, the tags NEXORA verified restart publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): Slot count: 1; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Build number: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): Players do not fight each other here; the world supplies the danger. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to NEXORA verified restart?
In Rust, F1 opens the console: type client.connect 63.135.75.101:38115. Launch Rust on this page does the same by opening the game through Steam and connecting.