On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 1
Rank#9,294top 42%
Last wipe27d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
58/ 100
C−
Working its way up from the back of the class: #9,294 on player hours.
Uptimehours on the list, last 48
85/ 100
A−
Good attendance: on the list 41 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 176 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 42% 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
Just for Vag1n@s leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 79.116.184.49:28015 is the address to use.
Is Just for Vag1n@s up, and how steady is its uptime?
The server is up: Just for Vag1n@s is online now. The uptime it reports puts the last restart at about 18 hours ago. For the last 3 full days, it was up 64 of 72 hours, or 89% of the time. It was first seen by Rust Server Score on 26 October 2026.
Does Just for Vag1n@s perform well?
It averaged 176 server fps over the last 48 hours, with a low of 150. At its peak, it held 139,510 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,544 MB. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does Just for Vag1n@s sit?
You will find Just for Vag1n@s on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Just for Vag1n@s wipe its map?
The record holds too few of Just for Vag1n@s's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 27 days 9 hours.
Player count
What position does Just for Vag1n@s hold in the rankings?
In the top 42% of all ranked servers, Just for Vag1n@s sits at #9,294 for player hours over the last seven days.
How many players does Just for Vag1n@s usually have?
With 10 slots available, Just for Vag1n@s currently has 0 players. It peaked at 1 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 21:00 UTC, with 1 players.
Tags
How should you read the tags on Just for Vag1n@s?
The game's browser takes its cue from the tags Just for Vag1n@s has set: gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Just for Vag1n@s?
Rust Server Score lists that include Just for Vag1n@s: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does Just for Vag1n@s enforce, and what are its settings?
Nothing in the name of Just for Vag1n@s states a gather rate. 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. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map Just for Vag1n@s uses?
The game generates the procedural map on Just for Vag1n@s at size 5,000 with seed 987654321. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How do you get onto Just for Vag1n@s?
To connect, start Rust, press F1, and type client.connect 79.116.184.49:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).