Working its way up from the back of the class: #12,055 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
22/ 100
F
Lost ground: down 6,804 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (D); 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.
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.
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 6 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 54% of all ranked servers. 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 14h.
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
Where in the world is Chori & Wine PVE | La Venganza de Nipur?
Chori & Wine PVE | La Venganza de Nipur leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 190.174.128.52:28015 is the address to use.
How reliable is Chori & Wine PVE | La Venganza de Nipur, and is it up?
You cannot join now: Chori & Wine PVE | La Venganza de Nipur is offline, last seen 18 days 7 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 6 October 2026.
Which Rust version is Chori & Wine PVE | La Venganza de Nipur running?
The server Chori & Wine PVE | La Venganza de Nipur is on Rust network protocol 2634 and build 166652 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does Chori & Wine PVE | La Venganza de Nipur reset?
the force wipe gives the basis for estimating Chori & Wine PVE | La Venganza de Nipur's next wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 24 days 8 hours have passed since this world was made. Its tags record that it wipes monthly.
Population
Where does Chori & Wine PVE | La Venganza de Nipur sit among Rust servers?
In the top 54% of all ranked servers, Chori & Wine PVE | La Venganza de Nipur sits at #12,055 for player hours over the last seven days.
Is Chori & Wine PVE | La Venganza de Nipur a busy server?
The last sighting of Chori & Wine PVE | La Venganza de Nipur was 18 days 7 hours ago, and it is offline right now.
Tags
What is meant by the tags on Chori & Wine PVE | La Venganza de Nipur?
The game's browser takes its cue from the tags Chori & Wine PVE | La Venganza de Nipur has set: gmvanilla (Game mode): You play vanilla survival here; mp25 (Max players): Its slot count is 25; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Chori & Wine PVE | La Venganza de Nipur?
These Rust Server Score lists count Chori & Wine PVE | La Venganza de Nipur among them: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Vanilla and Modded; Game mode: PvE; Server tag: Monthly ^m, Vanilla ^v, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is Chori & Wine PVE | La Venganza de Nipur set up, and what rules does it keep?
The name of Chori & Wine PVE | La Venganza de Nipur gives no gather rate. The default of 8 players applies as the group cap. pve is the mode here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Chori & Wine PVE | La Venganza de Nipur?
The game generates the procedural map on Chori & Wine PVE | La Venganza de Nipur at size 4,250 with seed 1393735046. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How do you get onto Chori & Wine PVE | La Venganza de Nipur?
To connect, start Rust, press F1, and type client.connect 190.174.128.52:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://discord.com/invite/7U585Ew8TJ.
Server tags
what each one means
Published asmp25,ptrak,$r?,v2634,^m,^v,^p,gmvanilla,cs166652,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp25
Max playersIts slot count is 25.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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 term to build on. Strongest in standing (D); momentum is the one to work on (F).