pico-v2 test
Offline 169.150.196.33:28015 checked 18d ago
Measurements
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 66% of all ranked servers. Ranked on player hours over the last seven days.
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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 10 Oct, 14:54 UTC18d ago | 1 | – | 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.
Quick answers
Player counts
How does pico-v2 test rank against other Rust servers?
By player hours over the last seven days, pico-v2 test places at #14,691, within the top 66% of ranked servers.
How busy is pico-v2 test?
pico-v2 test is offline at this count; we last saw it 18 days 7 hours ago.
Tags
What do the server tags on pico-v2 test mean?
What the game's server browser reads from pico-v2 test is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): Your game needs the same version, protocol 2634, to join; cs167398 (Build): Game build: 167398; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): This server appears under Modded because plugins or settings alter the game. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.
Which Rust Population lists and filters include pico-v2 test?
These Rust Population lists include pico-v2 test: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more and it will show up.
Wipe schedule
What does wipe day look like on pico-v2 test?
Averaged over recent wipes, 1 players were counted at the busiest point. 1 hours after the latest wipe the crowd peaked.
What is the wipe schedule on pico-v2 test?
Its rhythm cannot be told yet: too few of pico-v2 test's wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 18 days 12 hours ago the current world was made.
Settings
Which map does pico-v2 test run?
A procedural map, generated by the game, is in use on pico-v2 test.
What are the rules and settings on pico-v2 test?
No gather rate appears in the name of pico-v2 test. The group limit is 8 players, which is the default. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players is allowed. Modded is its browser category: plugins or settings change the game. Oxide plugins are in use here. The anti-cheat VAC from Valve is disabled.
About the server
Which version of Rust does pico-v2 test run?
Rust network protocol 2634 and build 167398 on Windows is what pico-v2 test uses. Steam updates your game automatically, but you need the same protocol to join.
Is pico-v2 test online, and how reliable is it?
We last saw pico-v2 test 18 days 7 hours ago, and it is offline now. Over the last 7 full days, 0 of 168 hours were online, or 0%. It was first seen by Rust Population on 9 October 2026.
Where is pico-v2 test located?
Nothing published by pico-v2 test states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 169.150.196.33:28015.
How to join
How do I join pico-v2 test?
Either enter client.connect 169.150.196.33:28015 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.