On the class lists: D (52), with population over 48 hours and no performance mark.
Players now1/ 552% full
7-day average0peak 2
Rank#5,568top 25%
Last wipe26d agoweekly schedule
Next wipe1d 1hFri 30 Oct, 12:31 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 55 on average. Plenty of space to grow.
Standingrank on player hours
75/ 100
B
Holds a respectable place: #5,568 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 134 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
88/ 100
A−
Climbing fast: up 4,181 places this week.
A fair term, with more to come.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 25% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W·W·WW·
····W··
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Friday 30 October, 12:31 UTC, in 1d 1h.
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
1d 1hFri 30 Oct, 12:31 UTC
7d 8hThu 5 Nov, 19:00 UTCFW
8d 1hFri 6 Nov, 12:31 UTC
15d 1hFri 13 Nov, 12:31 UTC
22d 1hFri 20 Nov, 12:31 UTC
29d 1hFri 27 Nov, 12:31 UTC
35d 8hThu 3 Dec, 19:00 UTCFW
36d 1hFri 4 Dec, 12:31 UTC
The first 48 hours of its last wipes
Fri 2 OctFri 25 SepSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 6, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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 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
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by [IND] Badnaam | Weekly. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 148.113.8.230:28015.
How dependable is [IND] Badnaam | Weekly, and is it online at the moment?
The server is up: [IND] Badnaam | Weekly is online now. According to its reported uptime, the last restart was about 8 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
Does [IND] Badnaam | Weekly perform well?
It averaged 134 server fps over the last 48 hours, with a low of 113. At its peak, it held 83,452 entities, including buildings, deployables and all else in the world. At its highest, it used 2,468 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is [IND] Badnaam | Weekly on?
You will find [IND] Badnaam | Weekly on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does [IND] Badnaam | Weekly wipe, and how often?
Too few wipes on [IND] Badnaam | Weekly are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Friday 30 October at 12:31 UTC. 26 days 22 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
What happens on [IND] Badnaam | Weekly when wipe day arrives?
Recent wipes have peaked at 12 players on average. 2 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 1 in the wipes where it did not hold.
Population
What position does [IND] Badnaam | Weekly hold in the rankings?
Over the last seven days, [IND] Badnaam | Weekly has #5,568 for player hours, in the top 25% of all ranked servers.
Is [IND] Badnaam | Weekly a busy server?
With 55 slots available, [IND] Badnaam | Weekly currently has 1 players. The seven-day average is 0 players, with a peak of 2. The highest average in the last 48 hours came at 10:00 UTC, with 1 players.
Tags
What do [IND] Badnaam | Weekly's tags stand for?
The game's browser takes its cue from the tags [IND] Badnaam | Weekly has set: gmrust (Game mode): Survival in the standard Rust style; mp55 (Max players): 55 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^w (Weekly): It wipes weekly; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): Oxide (uMod) provides the plugin framework here. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Who is behind [IND] Badnaam | Weekly?
No other server we track uses the jodsmp.in hostname that [IND] Badnaam | Weekly publishes.
Which lists and filters on Rust Server Score show [IND] Badnaam | Weekly?
These Rust Server Score lists count [IND] Badnaam | Weekly among them: Best community servers, graded and Vanilla Rust servers, graded. It shows under the following 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.
Server rules
What settings and rules apply on [IND] Badnaam | Weekly?
The name of [IND] Badnaam | Weekly gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. Oxide plugins are running on it. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [IND] Badnaam | Weekly uses?
The game generates the procedural map on [IND] Badnaam | Weekly at size 3,800 with seed 485541106. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join [IND] Badnaam | Weekly?
Enter client.connect 148.113.8.230:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/nqEzxqjkYp.
Server tags
what each one means
Published asmp55,ptrak,$r?,v2635,^w,^v,gmrust,cs168909,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp55
Max players55 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).