On the class lists: F (27), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak –
Rank#15,432top 69%
Last wipe12d agoweekly schedule
Next wipe1d 12hFri 30 Oct, 01:47 UTC
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,432 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 259 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (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 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 69% of all ranked servers, and #524 of the trio servers (top 84%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W·W·
···W···
·····W·
···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, 01:47 UTC, in 1d 12h.
Its weekly schedule tag · low confidence
usual gap5.2 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 3
Coming wipes
1d 12hFri 30 Oct, 01:47 UTC
8d 5hThu 5 Nov, 19:00 UTCFW
8d 12hFri 6 Nov, 01:47 UTC
15d 12hFri 13 Nov, 01:47 UTC
22d 12hFri 20 Nov, 01:47 UTC
29d 12hFri 27 Nov, 01:47 UTC
36d 5hThu 3 Dec, 19:00 UTCFW
36d 12hFri 4 Dec, 01:47 UTC
The first 48 hours of its last wipes
Fri 16 OctThu 8 OctSat 3 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 01:47 UTC12d ago
0
–
running
0
Thu 8 Oct, 19:05 UTC19d ago
0
–
7.3 days
0
Sat 3 Oct, 20:12 UTC24d ago
1
halved by day 3
5 days
0
Thu 24 Sep, 19:04 UTC33d ago
0
–
9 days
0
Sat 19 Sep, 14:58 UTC38d ago
0
–
5.2 days
0
Thu 17 Sep, 19:26 UTC40d ago
0
–
1.8 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
Where in the world is [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot |?
The name of [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | points to North America, though no region tag is set. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 69.131.179.199:28015.
Is [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | up, and how steady is its uptime?
The server is down: [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | is offline now, with the last sighting 6 days 21 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 13 September 2026.
What Rust version is [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | on?
Rust network protocol 2634 and build 167781 on Windows is what [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | wipe its map?
Its tag sets the prediction, as the record holds too few of [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot |'s wipes to confirm its schedule. It is due to wipe next on Friday 30 October at 01:47 UTC. 12 days 11 hours have passed since this world was made. The tags carry a weekly wipe schedule.
What should you expect from wipe day on [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot |?
The average peak on its recent wipes was 0 players. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 3.
Player numbers
What position does [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | hold in the rankings?
In the top 69% of all ranked servers, [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | sits at #15,432 for player hours over the last seven days. It comes #524 among servers in the trio group.
How many players does [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | usually have?
The last sighting of [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | was 6 days 21 hours ago, and it is offline right now. Over the past seven days, the average player count was 0.
Lists and filters
How should you read the tags on [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot |?
The game's browser takes its cue from the tags [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | has set: gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): The server holds 100 slots; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^w (Weekly): It wipes weekly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot |: 3x Rust servers, graded, Modded Rust servers, graded, Rust servers with a trio group limit and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 3x.
Rules and settings
Which rules does [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | enforce, and what are its settings?
[US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | sets gather at 3x, as its name suggests. You can have up to 3 players in a group (trio). survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | uses?
A procedural map of size 3,500 and seed 1659005079, generated by the game, is what [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot | runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How should you connect to [US] Beg4Mercy 3X | Solo/Duo/Trio | Weekly | Custom Loot |?
Enter client.connect 69.131.179.199: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/rcHNtNFwk.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^w,gmrust,cs167781,ts3,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersThe server holds 100 slots.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under 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 momentum (D); population is the one to work on (F).