Offline 185.65.134.239:28015 checked 18d ago
Pico Local Test
Connect
srv = rust.server("185.65.134.239: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 61% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 09:03 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
- 185.65.134.239: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 · 164 on average | 168/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 136/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 34/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 137/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 49/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Pico Local Test rank?
Player hours over seven days put Pico Local Test at #13,553, in the top 61% of the ranked set.
How many players does Pico Local Test hold at once?
The current row shows Pico Local Test offline; the last response was 18 days 4 hours ago.
Server data
What Rust version does Pico Local Test run?
The build is Rust network protocol 2634 and build 167231 on Windows, run by Pico Local Test. Steam updates your game for you, but the protocol must match to join.
Is Pico Local Test up, and what does its uptime show?
The latest sample has Pico Local Test offline, with a last sighting 18 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 9 October 2026.
Where does Pico Local Test sit?
For Pico Local Test, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 185.65.134.239:28015 is its address.
Map and rules
What rules and settings are recorded for Pico Local Test?
The name Pico Local Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. The VAC field reads off.
Which map has Pico Local Test loaded?
A procedural map runs on Pico Local Test, generated by the game.
Wipes and dates
When does Pico Local Test wipe, and on what schedule?
The record for Pico Local 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. The world it runs now was generated 18 days 11 hours ago.
What is wipe day on Pico Local Test like?
Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which Rust Data filters and lists contain Pico Local Test?
The Rust Data lists that Pico Local Test 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.
Which meanings do the tags on Pico Local Test hold?
These tags are published by Pico Local Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): The server lists 2 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167231 (Build): Build number: 167231; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Pico Local Test?
Enter client.connect 185.65.134.239:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.