Offline 62.101.160.208:28015 checked 20d ago
Pico Local Test
Connect
srv = rust.server("62.101.160.208: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 best
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 62.101.160.208:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 09:12 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 · 151 on average | 51/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 123 on average | 82/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 23/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 64/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 56/200 |
Quick answers
From the figures on this page.
Population data
What position does Pico Local Test take in the server rankings?
Rank #13,607 on seven-day player hours for Pico Local Test, within the top 61% of all ranked servers.
How many players does Pico Local Test hold at once?
The current row shows Pico Local Test offline; the last response was 20 days 12 hours ago.
Server data
What is the Rust version on Pico Local Test?
Rust network protocol 2634 and build 167231 on Windows is what Pico Local Test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Pico Local Test, and is it up?
Offline now for Pico Local Test, last seen 20 days 12 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.
Where does Pico Local Test sit?
There is no region published for Pico Local Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 62.101.160.208:28015 is its address.
Settings and map
Which settings and rules does Pico Local Test run?
The name Pico Local Test carries no gather rate. No custom cap; the default of 8 players per group stands. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC off.
What is the map on Pico Local Test?
Pico Local Test runs a procedural map, which the game generates.
Wipe schedule
When does Pico Local Test wipe, and how often?
The record for Pico Local Test holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 20 days 21 hours ago.
Tags, lists
Where does Pico Local Test appear among Rust Data lists and filters?
These Rust Data lists include Pico Local Test: 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 Local Test hold?
Read by the game's server browser, the tags Pico Local Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167231 (Build): Build number: 167231; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^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.
Connecting
How can I connect to Pico Local Test?
The manual route: launch Rust, F1, then client.connect 62.101.160.208:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.