Offline 85.131.245.63:28015 checked 28d ago
[JP]TRS:RUST[PvE]
Connect
srv = rust.server("85.131.245.63:29015")
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 best
Top 70% 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
4000 · seed 1
- map
- Procedural Map
- size
- 4000
- seed
- 1
Server
srv.info()- address
- 85.131.245.63:28015
- region
- –
- max players
- 48
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Sep 2026, 03:38 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 | QS『芬达』100000倍/10.28/枪战/蓝图全解/萌新/建造 | EA · groups of 20+ · weekly · 24 on average | 31/100 |
| 1 | 【蛋壳】10倍|10.23档|爆枪|礼包|新手推荐 | EA · groups of 8+ · weekly · 20 on average | 22/200 |
| 2 | [JP]初心者PVPサーバー|RaidTime・ Events | EA · groups of 10+ · biweekly · 16 on average | 7/100 |
| 3 | [守护]100倍PVE/迷雾僵尸/突袭基地/等级武直/萌新 | EA · no group limit · 11 on average | 21/100 |
| 4 | [JP] DON-tacos PvE | EA · groups of 8+ · monthly · 11 on average | 5/100 |
| 5 | #10-[搞就完了]10倍/10.29新档/无权/萌新首选 | EA · no group limit · 11 on average | 19/100 |
Quick answers
From the figures on this page.
Player counts
How does [JP]TRS:RUST[PvE] compare in the rankings?
Over the last seven days [JP]TRS:RUST[PvE] sits at #16,728 on player hours, in the top 70% of ranked servers.
What population does [JP]TRS:RUST[PvE] carry?
The current row shows [JP]TRS:RUST[PvE] offline; the last response was 28 days 10 hours ago.
Server facts
Which Rust version is [JP]TRS:RUST[PvE] on?
Rust network protocol 2633 and build 162929 on Linux is what [JP]TRS:RUST[PvE] runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is [JP]TRS:RUST[PvE], and is it online now?
[JP]TRS:RUST[PvE] is offline at this refresh; the last response came 28 days 10 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does [JP]TRS:RUST[PvE] run from?
The name of [JP]TRS:RUST[PvE] points to Asia, even though no region tag is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 85.131.245.63:28015 is its address.
Rules, settings, map
What rules and settings are recorded for [JP]TRS:RUST[PvE]?
The name [JP]TRS:RUST[PvE] carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has [JP]TRS:RUST[PvE] loaded?
[JP]TRS:RUST[PvE] runs a procedural map of size 4,000 with seed 1, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipes and dates
When does [JP]TRS:RUST[PvE] wipe, and on what schedule?
A rhythm cannot be read from the wipes of [JP]TRS:RUST[PvE] on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 55 days 3 hours ago.
Tags and filters
Which lists on Rust Data hold [JP]TRS:RUST[PvE], and which filters?
The Rust Data lists that [JP]TRS:RUST[PvE] fits are: Modded Rust servers. Under these filters on the server list, it is listed: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on [JP]TRS:RUST[PvE]?
The game's server browser reads these tags from [JP]TRS:RUST[PvE]: gmrust (Game mode): Survival play, standard Rust; mp48 (Max players): Slot count: 48; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs162929 (Build): Recorded game build: 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. 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
How can I connect to [JP]TRS:RUST[PvE]?
In Rust, F1 opens the console: type client.connect 85.131.245.63:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.