Pico Local Test
Offline 62.101.160.208:28015 checked 8d ago
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
daily · 1 is bestTop 61% 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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes
- 17/ 100
- 304/ 400
- 183/ 225
- 121/ 100
- 390/ 1000
- 31/ 700
Quick answers
Tags and listings
Where does Pico Local Test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Pico Local Test are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on Pico Local Test?
gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): The slot count is 2; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167231 (Build): This server runs build 167231; ptrak (Networking): Standard RakNet networking; $r? (Region code): It has no region code; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded — that is the tag list Pico Local Test puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What location is Pico Local Test in?
Pico Local Test does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 62.101.160.208:28015.
Is Pico Local Test up, and how often does it stay online?
Right now Pico Local Test is offline, having last been seen 8 days 16 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 9 October 2026 is when Rust Going Deep first saw it.
What Rust version is Pico Local Test on?
The version on Pico Local Test is Rust network protocol 2634 and build 167231, on Windows. The protocol must match to join; Steam will update your game.
Wipe details
How often does Pico Local Test wipe?
Pico Local Test's rhythm is unclear because not enough wipes are on record yet. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. 9 days 2 hours is how long ago this world came into being.
Settings and map
What settings and rules have been applied to Pico Local Test?
No gather rate appears in the name of Pico Local Test. Up to 8 players per group, which is the default. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is disabled.
What's the map on Pico Local Test?
The map on Pico Local Test is procedural, made by the game.
Player count
Is Pico Local Test busy?
Pico Local Test was last seen 8 days 16 hours ago and is offline as you read this.
What position does Pico Local Test hold in the server rankings?
For player hours in the last seven days, Pico Local Test ranks #13,607, within the top 61% of ranked servers.
How to join
What's the process to join Pico Local Test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 62.101.160.208:28015.