Offline 195.82.176.131:28015 checked 25d ago
TEST Server OXIDE
Connect
srv = rust.server("195.82.176.131: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 · 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 2 Oct, 10:07 UTC26d ago | 1 | NaN | running | 1 |
| 1 | Mon 21 Sep, 15:52 UTC37d ago | 1 | held half | 10.8 days | 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
- 195.82.176.131:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 10:07 UTC
- hostname
- –
- first seen
- 21 Sep 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 · 150 on average | 106/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 163/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 50/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Population
How does TEST Server OXIDE compare in the rankings?
Rank #13,916 on seven-day player hours for TEST Server OXIDE, within the top 61% of all ranked servers.
How many players does TEST Server OXIDE hold at once?
TEST Server OXIDE returns no live count at this refresh, having last been seen 25 days 12 hours ago.
Server data
What Rust version does TEST Server OXIDE run?
Version Rust network protocol 2634 and build 166586 on Windows is reported by TEST Server OXIDE. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST Server OXIDE, and is it up?
The latest sample has TEST Server OXIDE offline, with a last sighting 25 days 12 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 21 September 2026.
In which location is TEST Server OXIDE hosted?
There is no region published for TEST Server OXIDE. Rust Data does not look up where the machine stands; it shows where a server says it is. 195.82.176.131:28015 is its address.
Rules, settings, map
What rules and settings are recorded for TEST Server OXIDE?
You will not find a gather rate in the string TEST Server OXIDE. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on TEST Server OXIDE?
The game generates its map: procedural, on TEST Server OXIDE.
Wipe schedule
When does TEST Server OXIDE wipe, and how often?
Too few wipes are on record for TEST Server OXIDE to reveal its 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 26 days 22 hours ago.
What is wipe day on TEST Server OXIDE like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Where does TEST Server OXIDE appear among Rust Data lists and filters?
These Rust Data lists include TEST Server OXIDE: 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 TEST Server OXIDE hold?
The game's server browser reads these tags from TEST Server OXIDE: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166586 (Build): The server runs build 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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 into TEST Server OXIDE?
In Rust, F1 opens the console: type client.connect 195.82.176.131:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.