Online 104.129.133.199:28059 checked 8m ago
La 167 PVE
Connect
srv = rust.server("104.129.133.199:28056")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 17 Sep. 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
Top 50% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 27 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 25 Oct, 10:15 UTC2d ago | 1 | NaN | running | 0 |
| 1 | Wed 23 Sep, 03:32 UTC34d ago | 1 | halved by day 1 | 32.3 days | 0 |
# 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
3500 · seed 1362873838
- map
- Procedural Map
- size
- 3500
- seed
- 1362873838
Server
srv.info()- address
- 104.129.133.199:28059
- region
- –
- max players
- 120
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 10:15 UTC
- hostname
- –
- first seen
- 13 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 163 on average | 69/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 83/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 25/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 75/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 17/1000 |
Quick answers
From the figures on this page.
Population data
How does La 167 PVE compare in the rankings?
Rank #11,047 on seven-day player hours for La 167 PVE, within the top 50% of all ranked servers.
How many players does La 167 PVE hold at once?
Current row: 0 players on La 167 PVE, against 120 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 14:00 UTC is the busiest, at 1 players.
Server facts
What does performance look like on La 167 PVE?
Server fps over the last 48 hours averages 7; the floor is 5. Buildings, deployables and all else in the world took the count as high as 72,350 entities. The memory field tops out at 2,591 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on La 167 PVE?
Rust network protocol 2635 and build 168909 on Linux is what La 167 PVE runs. Steam updates your game for you, but the protocol must match to join.
Is La 167 PVE up, and what does its uptime show?
The current sample puts La 167 PVE online. Count back 2 days 10 hours from its reported uptime to get the last restart. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.
Where does La 167 PVE sit?
There is no region published for La 167 PVE. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 104.129.133.199:28059 is its address.
Rules, settings, map
Which settings and rules does La 167 PVE run?
You will not find a gather rate in the string La 167 PVE. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on La 167 PVE?
Size 3,500, seed 1362873838: the procedural map on La 167 PVE, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does La 167 PVE wipe?
Too few wipes are on record for La 167 PVE to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 2 days 12 hours ago.
On La 167 PVE, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 27 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 1.
Lists and tags
Which lists on Rust Data hold La 167 PVE, and which filters?
The Rust Data lists that La 167 PVE fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Which meanings do the tags on La 167 PVE hold?
These tags are published by La 167 PVE and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp120 (Max players): 120 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to La 167 PVE?
In Rust, F1 opens the console: type client.connect 104.129.133.199:28059. Launch Rust on this page does the same by opening the game through Steam and connecting.
