Working its way up from the back of the class: #14,501 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
31/ 100
F
Lost ground: down 5,534 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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 66% of all ranked servers, top 91% in EA. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W·W
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap1.8 daysbetween real wipes
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Sun 4 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 4 Oct, 04:26 UTC24d ago
1
–
running
1
Fri 2 Oct, 09:37 UTC26d ago
2
–
1.8 days
0
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
In Asia, according to its own listing, sits [JP]VRCRust, with the EA tag. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 60.91.61.143:28015.
Is [JP]VRCRust up, and how steady is its uptime?
At this moment, [JP]VRCRust is offline; the last time it was seen was 11 days 18 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 20 September 2026.
Which Rust version is [JP]VRCRust running?
Rust network protocol 2634 and build 167781 on Linux is what [JP]VRCRust runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [JP]VRCRust wipe, and how often?
The record holds too few of [JP]VRCRust's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 26 days 14 hours.
What should you expect from wipe day on [JP]VRCRust?
Recent wipes have peaked at 2 players on average. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does [JP]VRCRust place in the wider field of Rust servers?
Over the last seven days, [JP]VRCRust has #14,501 for player hours, in the top 66% of all ranked servers and #508 in Asia.
Is [JP]VRCRust a busy server?
It has been 11 days 18 hours since [JP]VRCRust was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on [JP]VRCRust?
The game's browser takes its cue from the tags [JP]VRCRust has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^p (PvE): The danger comes from the world, not from other players; ^d (Combat training): Practise aim and PvP, loot provided; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; EA (East Asia): In the server browser it appears under East Asia. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does [JP]VRCRust appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [JP]VRCRust among them: Modded Rust servers, graded, Rust combat training servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Game mode: PvE; Server tag: PvE ^p, Combat training ^d, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is [JP]VRCRust set up, and what rules does it keep?
You will find no gather rate in the name of [JP]VRCRust. The group limit stays at the game's default of 8 players. combat training is the mode here, practice for aim and PvP, and loot is handed out. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [JP]VRCRust uses?
A procedural map of size 4,500 and seed 1337, generated by the game, is what [JP]VRCRust runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join [JP]VRCRust?
Enter client.connect 60.91.61.143:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://vrchat.com/home/user/usr_1e1d17a4-8c33-429b-8a84-8a3a0d10ed3c.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,^p,^d,EA,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
^d
Combat trainingPractise aim and PvP, loot provided.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
EA
East AsiaIn the server browser it appears under East Asia.
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.