Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
AveragePeak
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
No rank history yet.
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
The name of [VN] SOLO Vanilla 1x points to Asia, though no region tag is set. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 1.52.202.95:9015.
Is [VN] SOLO Vanilla 1x up, and how steady is its uptime?
The server is down: [VN] SOLO Vanilla 1x is offline now, with the last sighting 44 days 10 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does [VN] SOLO Vanilla 1x sit?
Rust network protocol 2633 and build 162929 on Linux is what [VN] SOLO Vanilla 1x runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does [VN] SOLO Vanilla 1x reset?
There are too few wipes on record for [VN] SOLO Vanilla 1x 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 53 days 8 hours.
Player count
What position does [VN] SOLO Vanilla 1x hold in the rankings?
In the top – of all ranked servers, [VN] SOLO Vanilla 1x sits at #15,150 for player hours over the last seven days.
What does the population on [VN] SOLO Vanilla 1x look like?
The last sighting of [VN] SOLO Vanilla 1x was 44 days 10 hours ago, and it is offline right now.
Lists and filters
What do [VN] SOLO Vanilla 1x's tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts1 (Group limit): Teams cap out at 1; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs162929 (Build): This runs on build 162929; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^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 [VN] SOLO Vanilla 1x publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show [VN] SOLO Vanilla 1x?
These Rust Server Score lists count [VN] SOLO Vanilla 1x among them: Modded Rust servers, graded and Solo Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Gather rate: 1x.
Map and rules
Which rules does [VN] SOLO Vanilla 1x enforce, and what are its settings?
The name of [VN] SOLO Vanilla 1x points to a 1x gather rate. This is a solo-only server, so teams cannot form. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [VN] SOLO Vanilla 1x uses?
A procedural map, generated by the game, is what [VN] SOLO Vanilla 1x runs.
Getting in
How do you get onto [VN] SOLO Vanilla 1x?
To connect, start Rust, press F1, and type client.connect 1.52.202.95:9015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs162929,ts1,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts1
Group limitTeams cap out at 1.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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.
Not enough figures yet to write a report. Check back after a few days on the list.