Online 139.180.52.71:28015 checked 9m ago
The BAD idea
Connect
srv = rust.server("139.180.52.71: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, measured since 17 Sep. 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 69% 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
4500 · seed 6738
- map
- Procedural Map
- size
- 4500
- seed
- 6738
Server
srv.info()- address
- 139.180.52.71:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Sep 2026, 10:38 UTC
- hostname
- –
- first seen
- 15 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 246 on average | 93/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 236 on average | 193/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 101 on average | 34/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 58 on average | 118/200 |
| 4 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 52 on average | 57/100 |
| 5 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 52 on average | 29/300 |
Quick answers
From the figures on this page.
Player counts
How does The BAD idea compare in the rankings?
Over the last seven days The BAD idea sits at #15,423 on player hours, in the top 69% of ranked servers.
What population does The BAD idea carry?
The sample now reads 0 players for The BAD idea, out of 100 slots. Over the last seven days it averaged 0 players.
Server facts
How well does The BAD idea perform?
Server fps over the last 48 hours averages 90; the floor is 71. Buildings, deployables and all else in the world took the count as high as 110,139 entities. The memory field tops out at 5,444 MB. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is The BAD idea on?
Rust network protocol 2633 and build 165217 on Windows is what The BAD idea runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is The BAD idea, and is it up?
Online is the state at the latest refresh for The BAD idea. A restart about 8 days 14 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Rust Data logged it first on 15 September 2026.
Where does The BAD idea sit?
There is no region published for The BAD idea. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 139.180.52.71:28015.
Settings and map
What rules and settings are recorded for The BAD idea?
No gather rate appears in the name: The BAD idea. The group limit sits at the default of 8 players. Recorded as pve, player combat is not allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has The BAD idea selected?
The BAD idea runs a procedural map of size 4,500 with seed 6738, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does The BAD idea wipe, and how often?
Too few wipes are on record for The BAD idea 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. This world was created 43 days 2 hours ago.
Lists and tags
Which lists on Rust Data hold The BAD idea, and which filters?
These Rust Data lists include The BAD idea: 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.
How should you read the server tags on The BAD idea?
These tags are published by The BAD idea and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): Build number: 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): Players do not fight each other here; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Join steps
What is the way into The BAD idea?
Enter client.connect 139.180.52.71:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.