LiveLive coverage · Rust server
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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 26 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Embedded chart
Top 48% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe
This server has not put up a new map since the desk started watching it.
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.
Estimating Chori & Wine PVE | La Venganza de Nipur's next wipe relies on the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. The world you are playing on was built 24 days 13 hours. A monthly wipe schedule is published in its tags.
These are the Rust Live Stats lists Chori & Wine PVE | La Venganza de Nipur fits: Modded Rust servers live now and Rust PvE servers, live now. You will find it on the server list under 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.
These are the tags Chori & Wine PVE | La Venganza de Nipur makes public: gmvanilla (Game mode): The mode is vanilla survival; mp25 (Max players): 25 slots are available; ts8 (Group limit): 8 per team at most, the game's default setting; v2635 (Protocol): The server runs protocol 2635, so match that version to join; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): Region code: none set; ^m (Monthly): It wipes with Facepunch's force wipe, once each month; ^v (Vanilla): No changed rates, kits or rules — this is the game as Facepunch ships it; ^p (PvE): No player fights another — the danger comes from the world; ^o (Oxide): It runs the plugin framework Oxide (uMod); ^z (Modded): Plugins or settings changes put this under Modded. Players now, queue length and world creation time are carried in the tags too, and appear at the top of this page.
0 of Chori & Wine PVE | La Venganza de Nipur's 25 slots are filled right now. Peak over the past week: 2. Average: 0 players. The busiest hour in the past 48 was 15:00 UTC, averaging 1 players.
Player hours over seven days put Chori & Wine PVE | La Venganza de Nipur at #10,587, in the top 48% of all ranked servers.
The name Chori & Wine PVE | La Venganza de Nipur carries no gather rate. No custom limit is set, so groups hold the default 8 players. pve applies here, no fighting other players. Modded is its browser category, where plugins or settings change the game. Oxide plugins are in use. By its own label it is vanilla: no changed rates, kits or rules — this is the game as Facepunch ships it. VAC is enabled: Valve's anti-cheat.
Size 4,250, seed 1393735046: that is the procedural map the game generates for Chori & Wine PVE | La Venganza de Nipur. Same size, same seed, same map: RustMaps has it, reachable from this page.
Nothing on Chori & Wine PVE | La Venganza de Nipur states a region. The location shown on Rust Live Stats is the one a server gives, not a lookup of the machine's position. You can reach it at 190.174.116.91:28015.
Server fps averaged 56 over the last 48 hours, with a low of 43. Entity count reached 109,457: buildings, deployables and the rest of the world. Up to 5,194 MB of memory was used. Lag, as players feel it, comes from low fps and a rising entity count.
Rust network protocol 2635 and build 168909 on Windows is what Chori & Wine PVE | La Venganza de Nipur runs. Steam updates it for you, but your game needs the same protocol to join.
Chori & Wine PVE | La Venganza de Nipur is up and running at this moment. The uptime it reports puts the last restart at about 6 days 9 hours ago. It was online for 47 of 48 hours in the last 2 full days, or 98% of the time. Rust Live Stats has tracked it since 26 October 2026.
Enter client.connect 190.174.116.91:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you. You can find its website at https://discord.com/invite/7U585Ew8TJ.