Working its way up from the back of the class: #15,967 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
28/ 100
F
Lost ground: down 6,988 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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 6h.
The force wipe · high confidence
wipe-day peak1players, last three wipes
Coming wipes
7d 6hThu 5 Nov, 19:00 UTCFW
35d 6hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 21 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:11 UTCFW27d ago
1
–
running
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
No region is published for Vi's Modded PvE (7.5x). The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 71.90.125.24:28015 is the address to use.
Is Vi's Modded PvE (7.5x) up, and how steady is its uptime?
At this moment, Vi's Modded PvE (7.5x) is offline; the last time it was seen was 24 days 18 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 1 October 2026.
Which Rust version is Vi's Modded PvE (7.5x) running?
The server Vi's Modded PvE (7.5x) is on Rust network protocol 2634 and build 166494 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does Vi's Modded PvE (7.5x) wipe its map?
Vi's Modded PvE (7.5x) wipes with the force wipe and at no other time. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 27 days 18 hours have passed since this world was made.
What happens on Vi's Modded PvE (7.5x) when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 21 hours after it began.
Player count
What position does Vi's Modded PvE (7.5x) hold in the rankings?
In the top 71% of all ranked servers, Vi's Modded PvE (7.5x) sits at #15,967 for player hours over the last seven days.
How many players does Vi's Modded PvE (7.5x) usually have?
The last sighting of Vi's Modded PvE (7.5x) was 24 days 18 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Vi's Modded PvE (7.5x)?
The game's browser takes its cue from the tags Vi's Modded PvE (7.5x) has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Carbon provides the plugin framework here. 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.
Which lists and filters on Rust Server Score show Vi's Modded PvE (7.5x)?
These Rust Server Score lists count Vi's Modded PvE (7.5x) among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
What settings and rules apply on Vi's Modded PvE (7.5x)?
Going by its name, Vi's Modded PvE (7.5x) runs 7.5x gather. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Vi's Modded PvE (7.5x) uses?
Vi's Modded PvE (7.5x) runs a procedural map, which the game generates.
Connecting
How do you get onto Vi's Modded PvE (7.5x)?
To connect, start Rust, press F1, and type client.connect 71.90.125.24:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonCarbon provides the plugin framework here.
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.