RUST METRICSFlight deck · live data
Data live Servers11,637 Players32,508 Populated2,805 Fresh wipes 3 h70 Scan5 min
‹ All servers148.113.8.230:28015
Online Full Queue Fresh wipe Wipe due No query

[IND] Badnaam | Weekly

Online 148.113.8.230:28015 checked 8m ago

weekly wipes vanillaoxide
COM 1 · connect

Server instruments

last reading Thu 03:00 UTC
0 14 28 41 55 PAX 0 /55

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 145 SERVER FPS

Server fps

48 h low 113 · below 20 is lag, below 10 is bad
0 25 50 75 100 ENT 83,274 ×1000

Entities

48 h range 78,730–83,452 · memory 1,986 MB
1239 ET SINCE RESTART 02:22

Uptime

2 h 22 min since its last restart, at the last reading
7-day average0peak 2
Rank#5,751top 26%
Last wipe26d agoweekly schedule
Next wipe1d 7hFri 30 Oct, 12:31 UTC
Memory1,986MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75105:0014:0023:0008:0017:0003:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020005:0014:0023:0008:0017:0003: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 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12.5k5k7.5k10k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 26% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 12:31 UTC, in 1d 7h. Its weekly schedule tag · low confidence

usual gap2.6 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak12players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. WPT 1Fri 30 Oct, 12:31 UTC1d 7h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 14hFW
  3. WPT 3Fri 6 Nov, 12:31 UTC8d 7h
  4. WPT 4Fri 13 Nov, 12:31 UTC15d 7h
  5. WPT 5Fri 20 Nov, 12:31 UTC22d 7h
  6. WPT 6Fri 27 Nov, 12:31 UTC29d 7h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 14hFW
  8. WPT 8Fri 4 Dec, 12:31 UTC36d 7h

The first 48 hours of its last wipes

Fri 2 OctFri 25 SepSat 19 Sep
010203040+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 6, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 12:31 UTC26d ago 6 – running 0
Fri 25 Sep, 12:27 UTC33d 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 UTC40d ago 2 – 0.5 days 0
Wed 16 Sep, 20:40 UTC42d ago 1 – 1.7 days 0
Mon 14 Sep, 05:44 UTC44d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on [IND] Badnaam | Weekly?

The busiest point of its recent wipes drew 12 players on average. 2 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. By day 1 it fell below half when it didn't.

When does [IND] Badnaam | Weekly wipe?

Its tag guides the prediction: too few of [IND] Badnaam | Weekly's wipes are on record to confirm its schedule. Friday 30 October at 12:31 UTC is when its next wipe is due. 26 days 16 hours ago the current world was made. The tags state a wipe schedule of one wipe a week.

Tag meanings

How should you read the tags on [IND] Badnaam | Weekly?

These are the tags [IND] Badnaam | Weekly publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp55 (Max players): The server holds 55 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^w (Weekly): Wipe cycle: weekly; ^v (Vanilla): Unmodified from Facepunch's release: no altered rates, no kits, no extra rules; ^o (Oxide): Plugin framework in use: Oxide (uMod). Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Who is in charge of [IND] Badnaam | Weekly?

No other server we track uses the jodsmp.in hostname that [IND] Badnaam | Weekly publishes.

Where does [IND] Badnaam | Weekly appear in Rust Metrics lists and filters?

Rust Metrics lists featuring [IND] Badnaam | Weekly: Rust community servers: live readings and Vanilla Rust servers, live. These filters bring it up 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.

Population

Where does [IND] Badnaam | Weekly sit in the rankings?

Ranking for [IND] Badnaam | Weekly: #5,751 on seven-day player hours, top 26% of all ranked servers.

What is the population on [IND] Badnaam | Weekly?

Current headcount on [IND] Badnaam | Weekly: 0 players, 55 slots available. Check: players over seven days. Average 0, peak 2. Check: 48-hour peak. 10:00 UTC, 1 players on average.

Server details

Where does [IND] Badnaam | Weekly sit?

Reading: location. [IND] Badnaam | Weekly gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 148.113.8.230:28015.

What Rust version is [IND] Badnaam | Weekly on?

Reading: [IND] Badnaam | Weekly, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

Is performance on [IND] Badnaam | Weekly within range?

Reading: 133 server fps on average across the last 48 hours. It never dropped below 113. Reading: 83,452 entities at the highest. That covers buildings, deployables and everything else. Reading: 2,468 MB of memory at the highest. Expect lag when fps falls and entities climb.

How reliable is [IND] Badnaam | Weekly, and is it online now?

Check: connection. [IND] Badnaam | Weekly is online at this moment. Check: restart. The uptime it reports puts the last restart about 2 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

How is [IND] Badnaam | Weekly configured, and what rules are in force?

Reading the name gives no gather rate for [IND] Badnaam | Weekly. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Oxide plugins are running. It describes itself as vanilla. The meaning given: unmodified from Facepunch's release: no altered rates, no kits, no extra rules. Anti-cheat reading: VAC on, Valve's system.

Which map is live on [IND] Badnaam | Weekly?

Check: map. Procedural, size 3,800, seed 485541106, generated by the game on [IND] Badnaam | Weekly. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join [IND] Badnaam | Weekly?

Check: join. Open Rust, press F1, then enter client.connect 148.113.8.230:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. https://discord.com/invite/nqEzxqjkYp is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp55,ptrak,$r?,v2635,^w,^v,gmrust,cs168909,ts8,^o

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp55
Max players The server holds 55 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Difficulty

^v
Vanilla Unmodified from Facepunch's release: no altered rates, no kits, no extra rules.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).

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.