Offline 81.64.5.96:28015 checked 15d ago
Serveur Local Oxide Test
Connect
srv = rust.server("81.64.5.96:28017")
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 63% 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 | Mon 12 Oct, 16:21 UTC15d 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
- 81.64.5.96:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 16:21 UTC
- hostname
- –
- first seen
- 11 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 · 156 on average | 117/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 117/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 47/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 24/1000 |
Quick answers
From the figures on this page.
Player counts
What position does Serveur Local Oxide Test take in the server rankings?
Player hours over seven days put Serveur Local Oxide Test at #13,866, in the top 63% of the ranked set.
How full does Serveur Local Oxide Test run?
Offline now for Serveur Local Oxide Test, with the last sample 15 days 11 hours ago.
About the server
What is the Rust version on Serveur Local Oxide Test?
Version Rust network protocol 2634 and build 167584 on Windows is reported by Serveur Local Oxide Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Serveur Local Oxide Test, and is it up?
Offline now for Serveur Local Oxide Test, last seen 15 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 11 October 2026.
Where does Serveur Local Oxide Test sit?
There is no region published for Serveur Local Oxide Test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 81.64.5.96:28015.
Settings and map
What rules and settings are recorded for Serveur Local Oxide Test?
You will not find a gather rate in the string Serveur Local Oxide Test. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Serveur Local Oxide Test loaded?
The game generates its map: procedural, on Serveur Local Oxide Test.
Wipe schedule
When does Serveur Local Oxide Test wipe, and on what schedule?
The record for Serveur Local Oxide Test holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 15 days 15 hours ago, and that is the one in play.
On Serveur Local Oxide Test, what happens on wipe day?
The average peak over recent wipes is 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Serveur Local Oxide Test?
On Rust Data, Serveur Local Oxide Test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Serveur Local Oxide Test hold?
The game's server browser reads these tags from Serveur Local Oxide Test: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167584 (Build): The server runs build 167584; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join Serveur Local Oxide Test?
Enter client.connect 81.64.5.96:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.