Rust Data

rustdata.spaceservers80.0.186.84:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 80.0.186.84:28015 checked 10h ago

<oddball

moddedoxidepve

Connect

srv = rust.server("80.0.186.84:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 1 # peak 1
rank #6,756 # top 30%
last wipe 3d ago # no schedule published
next wipe – # too few wipes seen yet
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75121:0011:0013:0014:0016:0017:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020021:0011:0013:0014:0016:0017:00

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, measured since 17 Oct. 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
RankRank in region
15k10k15k20k10 Oct14 Oct18 Oct21 Oct25 Oct29 Oct

Top 30% 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 25 Oct, 15:27 UTC3d ago 1 NaN running 1

# 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

4500 · seed 465223350
Map of <oddball
map
Procedural Map
size
4500
seed
465223350
Open on RustMaps

Server

srv.info()
address
80.0.186.84:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
25 Oct 2026, 15:27 UTC
hostname
–
first seen
10 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 250 on average248/2000
1[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 241 on average94/2000
2Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 104 on average130/200
3【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 60 on average38/200
4[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 53 on average44/300
5TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 51 on average7/100

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does <oddball rank?

Over the last seven days <oddball sits at #6,756 on player hours, in the top 30% of ranked servers.

What population does <oddball carry?

<oddball returns no live count at this refresh, having last been seen 10 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 13:00 UTC, averaging 1 players.

About the server

How well does <oddball perform?

Server fps over the last 48 hours averages 103; the floor is 93. The entity count peaked at 119,490, covering buildings, deployables and the rest of the world. Memory peaked at 3,161 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is <oddball on?

The build is Rust network protocol 2635 and build 168909 on Windows, run by <oddball. The protocol has to match before you can join, and Steam does the updating.

How reliable is <oddball, and is it up?

<oddball is offline at this refresh; the last response came 10 hours ago. A restart about 4 hours ago is what its reported uptime implies. 23 of 168 hours up over the last 7 full days, or 14%. Its earliest recorded date in Rust Data is 10 October 2026.

Which location does <oddball run from?

No region is published by <oddball. Rust Data does not look up where the machine stands; it shows where a server says it is. 80.0.186.84:28015 is its address.

Rules, settings, map

Which settings and rules does <oddball run?

The name <oddball carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode pve, with this note: player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.

What is the map on <oddball?

Size 4,500, seed 465223350: the procedural map on <oddball, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipe schedule

When does <oddball wipe, and how often?

Too few wipes are on record for <oddball to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 12 hours ago.

On <oddball, what happens on wipe day?

The average peak over recent wipes is 1 players. Peak population on the latest wipe came 0 hours in.

Lists and tags

Which lists on Rust Data hold <oddball, and which filters?

The Rust Data lists that <oddball fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

How should you read the server tags on <oddball?

The game's server browser reads these tags from <oddball: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

What is the way to join <oddball?

In Rust, F1 opens the console: type client.connect 80.0.186.84:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2635,^p,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is set.

Gameplay

^p
PvE PvE: the world is the threat, not other players.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Plugins or settings alter the game, so it sits under Modded.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 33,246 players 11,665 servers online