Rust Data

rustdata.spaceservers190.174.119.89:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 190.174.119.89:28015 checked 2d ago

Chori & Wine PVE | La Venganza de Nipur

monthly wipes vanillamoddedoxidepve

Connect

srv = rust.server("190.174.119.89:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 0/25 # 0% full
7-day average 0 # peak –
rank #15,323 # top 69%
last wipe 24d ago # monthly schedule
next wipe 7d 7h # Thu 5 Nov, 19:00 UTC FW

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct29 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h. # The force wipe

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
190.174.119.89:28015
region
–
max players
25
group limit
8, the default
wipe schedule
monthly
last wipe
4 Oct 2026, 20:46 UTC
hostname
–
first seen
26 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 54 on average7/300
1[US] RustEZ Scourge PvE | Zombies | No Raiding | No KillingNA · groups of 8+ · monthly · 50 on average16/200
2[US] RustEZ Survival PvE | No Decay | No Raiding | No KillingNA · groups of 8+ · monthly · 38 on average4/200
3[坚果PVE]宗门师徒/每日打榜/合成强化/打金赚钱EA · groups of 8+ · monthly · 35 on average35/100
4Zombie Land PVE Monthly | Raids | Skills | Custom MapsNA · groups of 14+ · monthly · 34 on average11/100
5Hex US PVE Monthly 1X BiWeekly 5X | RPG | Custom Weapons | JetNA · no group limit · 1x · monthly · 34 on average56/100

Quick answers

From the figures on this page.

Population data

How does Chori & Wine PVE | La Venganza de Nipur compare in the rankings?

Player hours over seven days put Chori & Wine PVE | La Venganza de Nipur at #15,323, in the top 69% of the ranked set.

How many players does Chori & Wine PVE | La Venganza de Nipur hold at once?

Offline now for Chori & Wine PVE | La Venganza de Nipur, with the last sample 2 days 13 hours ago. Over the last seven days it averaged 0 players.

Server facts

Which Rust version is Chori & Wine PVE | La Venganza de Nipur on?

The build is Rust network protocol 2635 and build 168909 on Windows, run by Chori & Wine PVE | La Venganza de Nipur. Joining needs the same protocol on your game; Steam handles the update.

Is Chori & Wine PVE | La Venganza de Nipur up, and what does its uptime show?

Chori & Wine PVE | La Venganza de Nipur is offline at this refresh; the last response came 2 days 13 hours ago. 0 of 48 hours up over the last 2 full days, or 0%. The first row Rust Data holds for it is dated 26 October 2026.

Where does Chori & Wine PVE | La Venganza de Nipur sit?

For Chori & Wine PVE | La Venganza de Nipur, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 190.174.119.89:28015 is its address.

Map and rules

Which settings and rules does Chori & Wine PVE | La Venganza de Nipur run?

No gather rate appears in the name: Chori & Wine PVE | La Venganza de Nipur. Eight players per group: that is the game's default, and it applies here. Game mode pve, with this note: player combat is not allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC, Valve's anti-cheat, is enabled.

Which map has Chori & Wine PVE | La Venganza de Nipur selected?

Chori & Wine PVE | La Venganza de Nipur runs a procedural map, which the game generates.

Wipe data

When does Chori & Wine PVE | La Venganza de Nipur wipe, and how often?

Expect an estimate: Chori & Wine PVE | La Venganza de Nipur's next wipe is projected from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. The world it runs now was generated 24 days 14 hours ago. Its tags carry a monthly wipe schedule.

Tags, lists

Which Rust Data filters and lists contain Chori & Wine PVE | La Venganza de Nipur?

These Rust Data lists include Chori & Wine PVE | La Venganza de Nipur: Modded Rust servers and Rust PvE servers. These filters bring it up 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.

Which meanings do the tags on Chori & Wine PVE | La Venganza de Nipur hold?

Read by the game's server browser, the tags Chori & Wine PVE | La Venganza de Nipur publishes are: gmvanilla (Game mode): Survival in vanilla form; mp25 (Max players): Slot count: 25; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

What is the way into Chori & Wine PVE | La Venganza de Nipur?

In Rust, F1 opens the console: type client.connect 190.174.119.89:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp25,ptrak,$r?,v2635,^m,^v,^p,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp25
Max players Slot count: 25.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Monthly: the wipe lands with Facepunch's force wipe.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Modded listing: the game is changed by plugins or settings.

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.

Rust Data 60,549 players 11,720 servers online