Offline 169.150.196.33:28015 checked 18d ago
pico-v2 test
Connect
srv = rust.server("169.150.196.33:28016")
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. 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 bestTop 66% 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 10 Oct, 14:54 UTC18d ago | 1 | NaN | running | 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 169.150.196.33:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 14:54 UTC
- hostname
- –
- first seen
- 9 Oct 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 · 155 on average | 27/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 133/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 32/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 11/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0/1000 |
Quick answers
From the figures on this page.
Population
What position does pico-v2 test take in the server rankings?
Over the last seven days pico-v2 test sits at #14,691 on player hours, in the top 66% of ranked servers.
How many players does pico-v2 test hold at once?
The current row shows pico-v2 test offline; the last response was 18 days 6 hours ago.
About the server
Which Rust version is pico-v2 test on?
Version Rust network protocol 2634 and build 167398 on Windows is reported by pico-v2 test. The protocol has to match before you can join, and Steam does the updating.
Is pico-v2 test up, and what does its uptime show?
pico-v2 test is offline at this refresh; the last response came 18 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 9 October 2026.
Which location does pico-v2 test run from?
No region is published by pico-v2 test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 169.150.196.33:28015.
Map and rules
Which settings and rules does pico-v2 test run?
No gather rate appears in the name: pico-v2 test. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. The VAC field reads off.
Which map has pico-v2 test loaded?
The game generates its map: procedural, on pico-v2 test.
Wipes and dates
When does pico-v2 test wipe, and on what schedule?
The record for pico-v2 test holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 18 days 11 hours ago.
On pico-v2 test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 1 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does pico-v2 test appear among Rust Data lists and filters?
On Rust Data, pico-v2 test appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on pico-v2 test hold?
The game's server browser reads these tags from pico-v2 test: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167398 (Build): The server runs build 167398; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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
How can I connect to pico-v2 test?
In Rust, F1 opens the console: type client.connect 169.150.196.33:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.