On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,339top 69%
Last wipe17d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,339 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
50/ 100
D
Keeps a fair share of its players through a wipe: 50% of wipes kept half their crowd.
Momentumrank now against a week ago
44/ 100
F
Slipped a little: down 1,747 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in wipe hold (D); 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 24 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
····W··
······W
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap4.9 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 2
The first 48 hours of its last wipes
Sun 11 OctSun 11 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 11:43 UTC17d ago
1
–
running
0
Sun 11 Oct, 01:16 UTC18d ago
1
–
0.4 days
0
Fri 2 Oct, 10:14 UTC26d ago
1
✓ held half
8.6 days
0
Sun 27 Sep, 12:42 UTC31d ago
3
halved by day 2
4.9 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
Which region is [US]OmniRust | 5x | Biweekly | kits based in?
You won't find a region tag on [US]OmniRust | 5x | Biweekly | kits, but its name indicates North America. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 149.120.127.66:28015.
Is [US]OmniRust | 5x | Biweekly | kits up, and how steady is its uptime?
You cannot join now: [US]OmniRust | 5x | Biweekly | kits is offline, last seen 2 days 7 hours ago. It was up 10% of the time over the last 7 full days, 17 of 168 hours. The first sighting by Rust Server Score was on 24 September 2026.
Which Rust version is [US]OmniRust | 5x | Biweekly | kits running?
Rust network protocol 2634 and build 167398 on Linux is what [US]OmniRust | 5x | Biweekly | kits runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [US]OmniRust | 5x | Biweekly | kits wipe, and how often?
[US]OmniRust | 5x | Biweekly | kits wipes at times that vary, so no next wipe can be predicted. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 17 days 19 hours.
What should you expect from wipe day on [US]OmniRust | 5x | Biweekly | kits?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 1 hours into the latest wipe. Half the peak held until the next wipe in 50% of its recent wipes. In the other wipes it slipped under half by day 2.
Player numbers
What position does [US]OmniRust | 5x | Biweekly | kits hold in the rankings?
Over the last seven days, [US]OmniRust | 5x | Biweekly | kits has #15,339 for player hours, in the top 69% of all ranked servers.
What does the population on [US]OmniRust | 5x | Biweekly | kits look like?
It has been 2 days 7 hours since [US]OmniRust | 5x | Biweekly | kits was last seen, and it is offline right now. For the last seven days, the average number of players was 0.
Tags and filters
How should you read the tags on [US]OmniRust | 5x | Biweekly | kits?
The game's browser takes its cue from the tags [US]OmniRust | 5x | Biweekly | kits has set: gmvanilla (Game mode): Survival, vanilla style; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): This runs on build 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature [US]OmniRust | 5x | Biweekly | kits?
These Rust Server Score lists count [US]OmniRust | 5x | Biweekly | kits among them: 5x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 5x.
Server rules
How is [US]OmniRust | 5x | Biweekly | kits set up, and what rules does it keep?
The name of [US]OmniRust | 5x | Biweekly | kits points to a 5x gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
[US]OmniRust | 5x | Biweekly | kits runs which map?
[US]OmniRust | 5x | Biweekly | kits runs a game-generated procedural map at size 4,500, seed 138020313. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to [US]OmniRust | 5x | Biweekly | kits?
Enter client.connect 149.120.127.66:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,gmvanilla,cs167398,ts8,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp100
Max playersThe server holds 100 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A term to build on. Strongest in wipe hold (D); population is the one to work on (F).