On the class lists: D (50), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 2
Rank#5,879top 26%
Last wipe4d agoweekly schedule
Next wipe2d 23hSun 1 Nov, 11:11 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
74/ 100
B−
Holds a respectable place: #5,879 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
100/ 100
A+
Runs smoothly: 63 server fps on average.
Wipeskeeping the crowd after a wipe
20/ 100
F
Needs to keep more players after wipe day: 20% of wipes kept half their crowd.
Momentumrank now against a week ago
58/ 100
C−
Moving up: up 905 places this week.
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.
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 26% of all ranked servers, and #163 of the solo servers (top 73%). Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
······W
····W·W
······W
······W
······W
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Sunday 1 November, 11:11 UTC, in 2d 23h.
Every Sunday at 11:11 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm86%of its recent wipes
wipe-day peak2players, last three wipes
crowd held20%else halves by day 1.5
Coming wipes
2d 23hSun 1 Nov, 11:11 UTC
7d 7hThu 5 Nov, 19:00 UTCFW
9d 23hSun 8 Nov, 11:11 UTC
16d 23hSun 15 Nov, 11:11 UTC
23d 23hSun 22 Nov, 11:11 UTC
30d 23hSun 29 Nov, 11:11 UTC
35d 7hThu 3 Dec, 19:00 UTCFW
37d 23hSun 6 Dec, 11:11 UTC
The first 48 hours of its last wipes
Sun 25 OctSun 18 OctSun 11 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 11:11 UTC4d ago
2
–
running
0
Sun 18 Oct, 10:11 UTC11d ago
3
halved by day 1
7 days
0
Sun 11 Oct, 10:11 UTC18d ago
1
halved by day 4
7 days
0
Sun 4 Oct, 10:11 UTC25d ago
5
halved by day 1
7 days
1
Fri 2 Oct, 10:21 UTC27d ago
2
✓ held half
2 days
0
Sun 27 Sep, 10:11 UTC32d ago
4
halved by day 2
5 days
0
Sun 20 Sep, 10:11 UTC39d ago
7
halved by day 1
7 days
1
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
Where in the world is Nightly | Solo | Beginner | Vanilla?
You'll find no region listed by Nightly | Solo | Beginner | Vanilla. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 85.215.227.142:28016.
How reliable is Nightly | Solo | Beginner | Vanilla, and is it up?
Right now, Nightly | Solo | Beginner | Vanilla is online. The uptime it reports puts the last restart at about 22 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does Nightly | Solo | Beginner | Vanilla perform well?
It never fell below 27 server fps in the last 48 hours, averaging 63. Buildings, deployables and everything else in the world added up to as many as 77,149 entities. At its highest, it used 2,246 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is Nightly | Solo | Beginner | Vanilla running?
You will find Nightly | Solo | Beginner | Vanilla on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Nightly | Solo | Beginner | Vanilla wipe its map?
The wipe rhythm on Nightly | Solo | Beginner | Vanilla is every Sunday at 11:11 UTC. Expect the next wipe on Sunday 1 November at 11:11 UTC. It has been running its current world for 4 days. The tags carry a weekly wipe schedule.
What should you expect from wipe day on Nightly | Solo | Beginner | Vanilla?
Across its recent wipes, the busiest moments averaged 2 players. 0 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 20% of its recent wipes. The crowd dropped below half by day 1.5 in the wipes where it did not hold.
Population
Where does Nightly | Solo | Beginner | Vanilla sit among Rust servers?
In the top 26% of all ranked servers, Nightly | Solo | Beginner | Vanilla sits at #5,879 for player hours over the last seven days. In the solo group, it ranks #163.
How many players does Nightly | Solo | Beginner | Vanilla usually have?
With 100 slots available, Nightly | Solo | Beginner | Vanilla currently has 0 players. The seven-day average is 0 players, with a peak of 2. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 2 players.
Tags
What do Nightly | Solo | Beginner | Vanilla's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts1 (Group limit): No team may go above 1; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^d (Combat training): You are given the loot; the point is aim and PvP practice; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Nightly | Solo | Beginner | Vanilla publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Nightly | Solo | Beginner | Vanilla appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Nightly | Solo | Beginner | Vanilla: Rust servers for beginners, graded, Modded Rust servers, graded, Rust combat training servers, graded and Solo Rust servers, graded. It shows under the following filters on the server list: Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Combat training ^d, Modded ^z and Oxide ^o; Group limit: Solo; Wipe schedule: Weekly; Last wipe: In the last week.
Server rules
What settings and rules apply on Nightly | Solo | Beginner | Vanilla?
Nothing in the name of Nightly | Solo | Beginner | Vanilla states a gather rate. Solo play only, with no teams permitted. You get combat training here, loot is handed out for aim and PvP practice. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Nightly | Solo | Beginner | Vanilla?
A procedural map of size 3,500 and seed 1785397734, generated by the game, is what Nightly | Solo | Beginner | Vanilla runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to Nightly | Solo | Beginner | Vanilla?
Enter client.connect 85.215.227.142:28016 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 asmp100,ptrak,$r?,v2635,^w,^v,^d,gmrust,cs168909,ts1,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts1
Group limitNo team may go above 1.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Gameplay
^d
Combat trainingYou are given the loot; the point is aim and PvP practice.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).