On the class lists: F (36), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#14,968top 67%
Last wipe10d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
33/ 100
F
Working its way up from the back of the class: #14,968 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
16/ 100
F
Needs to work on its frame rate: 10 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 157 places this week.
A term to build on.
Strongest in uptime (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.
AveragePeakWipe
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 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 67% of all ranked servers. 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 gap17.3 daysbetween real wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 19 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 19 Oct, 13:23 UTC10d ago
0
–
running
0
Fri 2 Oct, 07:17 UTC27d ago
1
halved by day 1
17.3 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
Just Play [vin] leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 195.206.233.220:28015 is the address to use.
How reliable is Just Play [vin], and is it up?
The server is up: Just Play [vin] is online now. About 6 days 11 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does Just Play [vin] perform well?
It averaged 10 server fps over the last 48 hours, with a low of 5. At its peak, it held 69,626 entities, including buildings, deployables and all else in the world. Up to 3,001 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does Just Play [vin] sit?
The server Just Play [vin] is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does Just Play [vin] wipe, and how often?
There are too few wipes on record for Just Play [vin] to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 10 days 6 hours.
What happens on Just Play [vin] when wipe day arrives?
The average peak on its recent wipes was 0 players. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Player count
What position does Just Play [vin] hold in the rankings?
Over the last seven days, Just Play [vin] has #14,968 for player hours, in the top 67% of all ranked servers.
How many players does Just Play [vin] usually have?
Just Play [vin] is showing 0 players right now, with 50 slots in total. It peaked at 1 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 13:00 UTC, with 0 players.
Tags and filters
What is meant by the tags on Just Play [vin]?
The game's browser takes its cue from the tags Just Play [vin] has set: gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; 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): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this 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 Just Play [vin] appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Just Play [vin]: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
How is Just Play [vin] set up, and what rules does it keep?
Nothing in the name of Just Play [vin] states a gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
Which map is in play on Just Play [vin]?
A procedural map of size 3,500 and seed 166863296, generated by the game, is what Just Play [vin] runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to Just Play [vin]?
Enter client.connect 195.206.233.220: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 asmp50,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
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
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
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. Strongest in uptime (A+); population is the one to work on (F).