[IND] Badnaam | Weekly
Online 148.113.8.230:28015 checked 6m ago
Vital stats
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 24% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Friday 30 October, 12:31 UTC, in 22h. Its weekly schedule tag · low confidence
Coming wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 6, 2 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 12:31 UTC27d ago | 6 | – | running | 0 |
| Fri 25 Sep, 12:27 UTC34d ago | 30 | halved by day 1 | 7 days | 1 |
| Sat 19 Sep, 00:47 UTC40d ago | 0 | – | 6.5 days | 0 |
| Fri 18 Sep, 12:31 UTC41d ago | 2 | – | 0.5 days | 0 |
| Wed 16 Sep, 20:40 UTC42d ago | 1 | – | 1.7 days | 0 |
| Mon 14 Sep, 05:44 UTC45d ago | 2 | halved by day 1 | 2.6 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Tags
Who runs [IND] Badnaam | Weekly?
No other server we track uses the jodsmp.in hostname that [IND] Badnaam | Weekly publishes.
Which Rust Pop Watch lists and filters include [IND] Badnaam | Weekly?
These Rust Pop Watch lists include [IND] Badnaam | Weekly: Community servers, by the numbers and Vanilla Rust servers, live. It appears under these filters on the server list: Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Weekly ^w, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
What do the server tags on [IND] Badnaam | Weekly mean?
The game's server browser picks up these tags from [IND] Badnaam | Weekly: gmrust (Game mode): This one runs standard Rust survival, as it comes; mp55 (Max players): Slots: 55; ts8 (Group limit): This uses the default limit of 8 players per team; v2635 (Protocol): To join, your game must be on the same protocol version: 2635; cs168909 (Build): It's on game build 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^v (Vanilla): Facepunch's game, unchanged: no modified rates, kits or rules; ^o (Oxide): Oxide (uMod), a plugin framework, is what it runs. Current players, queue and world age are in the tags too, displayed at the top of this page.
Population
How does [IND] Badnaam | Weekly rank against other Rust servers?
The last seven days of player hours place [IND] Badnaam | Weekly at #5,393, in the top 24% of all ranked servers.
How many players are on [IND] Badnaam | Weekly right now?
0 players are on [IND] Badnaam | Weekly at the moment, out of 55 slots. Peak for the week was 2, against an average of 0 players. The busiest stretch of the last 48 hours came at 10:00 UTC, averaging 1 players.
Server facts
Is [IND] Badnaam | Weekly online, and how reliable is it?
As of now, [IND] Badnaam | Weekly is online. The uptime figure suggests it restarted roughly 11 hours ago. Out of 168 hours in the last 7 full days, it was online for 167, a 99% uptime. Rust Pop Watch's first record of it is 13 September 2026.
Does [IND] Badnaam | Weekly run smoothly?
Average server fps for the last 48 hours was 133, and it never went below 108. Entities reached a maximum of 83,598: buildings, deployables and everything else. The highest memory usage was 2,481 MB. Players feel lag when fps drops and the entity count climbs.
Where is [IND] Badnaam | Weekly located?
No region is published by [IND] Badnaam | Weekly. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. You'll find it at 148.113.8.230:28015.
Which Rust version is [IND] Badnaam | Weekly on?
On Linux, [IND] Badnaam | Weekly runs Rust network protocol 2635 and build 168909. Joining requires your game to match the protocol, which Steam updates for you.
The wipe schedule
What happens on [IND] Badnaam | Weekly when wipe day comes around?
Across its recent wipes, the busiest point averaged 12 players. 2 hours after the latest wipe, the crowd hit its peak. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. The crowd fell under half by day 1 whenever it did not hold.
What is the wipe schedule on [IND] Badnaam | Weekly?
Too few wipes are recorded on [IND] Badnaam | Weekly to confirm its schedule, so its tag drives the prediction. The next wipe is pencilled in for Friday 30 October at 12:31 UTC. Its current world has been live for 27 days 1 hours. Weekly is the wipe rhythm its tags set out.
The rules
Which map does [IND] Badnaam | Weekly run?
Generated by the game with seed 485541106, the map on [IND] Badnaam | Weekly is procedural and 3,800 in size. RustMaps has it from this page, since identical size and seed give an identical map.
What are the rules and settings on [IND] Badnaam | Weekly?
The name of [IND] Badnaam | Weekly says nothing about gather rate. Groups go up to 8 players, which is the default. the usual game of gathering, building and raiding: that is the survival mode. Raids and PvP are both on the table. The server browser lists it under Community. Oxide plugins are running on it. The server's own word for it is vanilla: facepunch's game, unchanged: no modified rates, kits or rules. Anti-cheat is on: VAC, Valve's system.
How to join
How do I join [IND] Badnaam | Weekly?
Enter client.connect 148.113.8.230:28015 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/nqEzxqjkYp.