Working its way up from the back of the class: #15,556 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
51/ 100
D
Moving up: up 256 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
No daily history yet.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 68% of all ranked servers, top 82% in NA. 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h.
The 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
In North America, according to its own listing, sits Vinager, with the NA tag. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 73.54.237.216:28016.
Is Vinager up, and how steady is its uptime?
You cannot join now: Vinager is offline, last seen 26 days 21 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 2 October 2026.
On what Rust version does Vinager sit?
You will find Vinager on Rust network protocol 2634 and build 166494, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Vinager reset?
The next wipe on Vinager is a projection from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 27 days 14 hours. The tags show a monthly wipe schedule.
Player count
Where does Vinager place in the wider field of Rust servers?
In North America, Vinager is #1,535, and overall it is #15,556 on player hours over the last seven days, in the top 68% of all ranked servers.
How many players does Vinager usually have?
The last sighting of Vinager was 26 days 21 hours ago, and it is offline right now.
Tags and filters
What do Vinager's tags stand for?
You'll see Vinager tagged with 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; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; NA (North America): The server browser lists it under North America in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does Vinager appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Vinager: Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
Which rules does Vinager enforce, and what are its settings?
The name of Vinager gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. 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 Vinager?
Vinager runs a game-generated procedural map at size 2,599, seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to Vinager?
To connect, start Rust, press F1, and type client.connect 73.54.237.216:28016. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,^m,^v,NA,gmrust,cs166494,ts8,^o^z
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.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
NA
North AmericaThe server browser lists it under North America.
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 momentum (D); standing is the one to work on (F).