Working its way up from the back of the class: #15,191 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
18/ 100
F
Lost ground: down 9,824 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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
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 64% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
··WW·WW
WW·WWWW
W······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap0.5 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Mon 28 SepSun 27 SepSun 27 Sep
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
Mon 28 Sep, 06:18 UTC30d ago
1
–
running
1
Sun 27 Sep, 18:38 UTC31d ago
1
–
0.5 days
1
Sun 27 Sep, 10:18 UTC31d ago
1
–
0.3 days
1
Sat 26 Sep, 08:58 UTC32d ago
1
–
1.1 days
1
Fri 25 Sep, 12:42 UTC33d ago
1
–
0.8 days
1
Fri 25 Sep, 06:04 UTC33d ago
1
–
0.3 days
0
Thu 24 Sep, 16:48 UTC34d ago
1
–
0.6 days
0
Tue 22 Sep, 17:20 UTC36d ago
1
–
2 days
1
Tue 22 Sep, 06:34 UTC36d ago
1
–
0.4 days
1
Mon 21 Sep, 17:54 UTC37d ago
1
–
0.5 days
1
Mon 21 Sep, 06:26 UTC37d ago
1
–
0.5 days
1
Sun 20 Sep, 14:28 UTC38d ago
1
–
0.7 days
1
Sat 19 Sep, 10:40 UTC39d ago
1
–
1.2 days
1
Sat 19 Sep, 03:40 UTC39d ago
1
–
0.3 days
1
Thu 17 Sep, 16:00 UTC41d ago
1
–
1.5 days
1
Thu 17 Sep, 08:40 UTC41d ago
1
–
0.3 days
1
Wed 16 Sep, 16:52 UTC42d ago
1
–
0.7 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
You'll find no region listed by Vanilla Server. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 147.192.82.57:28015 is the address to use.
How reliable is Vanilla Server, and is it up?
At this moment, Vanilla Server is offline; the last time it was seen was 29 days 18 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 16 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Vanilla Server sit?
The server Vanilla Server is on Rust network protocol 2633 and build 165217 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does Vanilla Server reset?
No next wipe can be predicted for Vanilla Server, which wipes at irregular times. 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 30 days 18 hours.
What happens on Vanilla Server when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does Vanilla Server place in the wider field of Rust servers?
Over the last seven days, Vanilla Server has #15,191 for player hours, in the top 64% of all ranked servers.
What does the population on Vanilla Server look like?
Vanilla Server is offline at the moment; the last time it was seen was 29 days 18 hours ago.
Lists and filters
What do Vanilla Server's tags stand for?
gmvanilla (Game mode): Survival, vanilla style; mp1 (Max players): Its slot count is 1; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set are the tags Vanilla Server publishes, and the game's server browser reads them. 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 Vanilla Server appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Vanilla Server: 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.
Rules and settings
Which rules does Vanilla Server enforce, and what are its settings?
You will find no gather rate in the name of Vanilla Server. The default of 8 players applies as the group cap. 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.
Getting in
How do you get onto Vanilla Server?
Enter client.connect 147.192.82.57: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 asmp1,ptrak,$r?,v2633,gmvanilla,cs165217,ts8
Game
gmvanilla
Game modeSurvival, vanilla style.
mp1
Max playersIts slot count is 1.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildBuild number: 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
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 standing (F); momentum is the one to work on (F).