Working its way up from the back of the class: #16,728 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
25/ 100
F
Lost ground: down 8,204 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to F.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You won't find a region tag on [JP]TRS:RUST[PvE], but its name indicates Asia. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 85.131.245.63:28015.
How reliable is [JP]TRS:RUST[PvE], and is it up?
You cannot join now: [JP]TRS:RUST[PvE] is offline, last seen 27 days 12 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
Which Rust version is [JP]TRS:RUST[PvE] running?
You will find [JP]TRS:RUST[PvE] on Rust network protocol 2633 and build 162929, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does [JP]TRS:RUST[PvE] wipe its map?
[JP]TRS:RUST[PvE] has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 54 days 5 hours have passed since this world was made.
Population
Where does [JP]TRS:RUST[PvE] sit among Rust servers?
In the top 70% of all ranked servers, [JP]TRS:RUST[PvE] sits at #16,728 for player hours over the last seven days.
What does the population on [JP]TRS:RUST[PvE] look like?
The last sighting of [JP]TRS:RUST[PvE] was 27 days 12 hours ago, and it is offline right now.
Tags
How should you read the tags on [JP]TRS:RUST[PvE]?
You'll see [JP]TRS:RUST[PvE] tagged with gmrust (Game mode): Survival in the standard Rust style; mp48 (Max players): The server holds 48 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): Join only if your game runs protocol 2633; cs162929 (Build): This runs on build 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [JP]TRS:RUST[PvE] appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [JP]TRS:RUST[PvE] among them: Modded Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is [JP]TRS:RUST[PvE] set up, and what rules does it keep?
You will find no gather rate in the name of [JP]TRS:RUST[PvE]. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [JP]TRS:RUST[PvE]?
[JP]TRS:RUST[PvE] runs a game-generated procedural map at size 4,000, seed 1. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join [JP]TRS:RUST[PvE]?
Enter client.connect 85.131.245.63:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp48,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp48
Max playersThe server holds 48 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Even marks across the subjects, from F to F.