Offline 81.64.5.139:28015 checked 5d ago
Serveur Local Oxide Test
Connect
srv = rust.server("81.64.5.139: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 best
Top 66% 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
- 81.64.5.139:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 16:21 UTC
- hostname
- –
- first seen
- 23 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 | 55/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.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 · 117 on average | 82/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 25/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 5/1000 |
Quick answers
From the figures on this page.
Population
What position does Serveur Local Oxide Test take in the server rankings?
Player hours over seven days put Serveur Local Oxide Test at #14,616, in the top 66% of the ranked set.
What population does Serveur Local Oxide Test carry?
Offline now for Serveur Local Oxide Test, with the last sample 5 days 14 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
About the server
What Rust version does Serveur Local Oxide Test run?
Rust network protocol 2635 and build 167584 on Windows is what Serveur Local Oxide Test runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Serveur Local Oxide Test, and is it up?
Offline now for Serveur Local Oxide Test, last seen 5 days 14 hours ago. Uptime of 0% across the last 5 full days: 0 hours of 120. The first row Rust Data holds for it is dated 23 October 2026.
In which location is Serveur Local Oxide Test hosted?
No region is published by Serveur Local Oxide Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 81.64.5.139:28015 is its address.
Map and rules
Which settings and rules does Serveur Local Oxide Test run?
No gather rate appears in the name: Serveur Local Oxide Test. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has Serveur Local Oxide Test selected?
A procedural map runs on Serveur Local Oxide Test, generated by the game.
Wipe schedule
When does Serveur Local Oxide Test wipe, and how often?
Too few wipes are on record for Serveur Local Oxide Test to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 16 days 14 hours ago.
Tags, lists
Which lists on Rust Data hold Serveur Local Oxide Test, and which filters?
The Rust Data lists that Serveur Local Oxide 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.
How should you read the server tags on Serveur Local Oxide Test?
Read by the game's server browser, the tags Serveur Local Oxide Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; 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. 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
What is the way into Serveur Local Oxide Test?
Enter client.connect 81.64.5.139:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.