On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 750% full
7-day average0peak 1
Rank#14,261top 64% · #1449 in NA
Last wipe11d agobiweekly schedule
Next wipe2d 8hSat 31 Oct, 12:42 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 75 on average. Plenty of space to grow.
Standingrank on player hours
36/ 100
F
Working its way up from the back of the class: #14,261 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
35/ 100
F
Needs to work on its frame rate: 21 server fps on average.
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
17/ 100
F
Lost ground: down 9,330 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (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 64% of all ranked servers, top 78% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·····WW
···WWW·
·······
····
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 Saturday 31 October, 12:42 UTC, in 2d 8h.
Its biweekly schedule tag · low confidence
usual gap1.7 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak2players, last three wipes
crowd held50%else halves by day 5
Coming wipes
2d 8hSat 31 Oct, 12:42 UTC
7d 15hThu 5 Nov, 19:00 UTCFW
16d 8hSat 14 Nov, 12:42 UTC
30d 8hSat 28 Nov, 12:42 UTC
35d 15hThu 3 Dec, 19:00 UTCFW
44d 8hSat 12 Dec, 12:42 UTC
The first 48 hours of its last wipes
Sat 17 OctFri 16 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 12:42 UTC11d ago
2
–
running
1
Fri 16 Oct, 02:10 UTC13d ago
2
–
1.4 days
1
Thu 15 Oct, 07:07 UTC13d ago
1
–
0.8 days
0
Sun 11 Oct, 18:48 UTC17d ago
2
✓ held half
3.5 days
1
Sat 10 Oct, 04:36 UTC18d ago
1
–
1.6 days
1
Sat 3 Oct, 23:08 UTC25d ago
1
halved by day 5
6.2 days
1
Fri 2 Oct, 01:33 UTC27d ago
1
–
1.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
In what location does (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS sit?
You'll find (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS in North America, tagged NA, with region code us5. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 91.229.114.45:28107.
How reliable is (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS, and is it up?
The server is up: (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS is online now. About 18 hours ago, it restarted, based on the uptime it reports. It was up 99% of the time over the last 7 full days, 167 of 168 hours. It was first seen by Rust Server Score on 15 September 2026.
Is (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS smooth to play on?
It averaged 21 server fps over the last 48 hours, with a low of 8. Up to 74,191 entities were in the world, covering buildings, deployables and the rest. Up to 3,136 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS running?
Rust network protocol 2635 and build 168909 on Linux is what (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS wipe its map?
The prediction follows its tag, because too few of (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS's wipes are on record to confirm the schedule. Saturday 31 October at 12:42 UTC is the date set for its next wipe. The world it runs now was created 11 days 15 hours. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS?
Recent wipes have peaked at 2 players on average. Peak numbers came 2 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 50% of its recent wipes. The crowd dropped below half by day 5 in the wipes where it did not hold.
Population
Where does (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS place in the wider field of Rust servers?
Over the last seven days, (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS has #14,261 for player hours, in the top 64% of all ranked servers and #1,449 in North America.
How many players does (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS usually have?
With 75 slots available, (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS currently has 0 players. Averaging 0 players over seven days, it peaked at 1.
Tags and filters
What do (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS's tags stand for?
You'll see (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS tagged with gmrust (Game mode): Survival in the standard Rust style; mp75 (Max players): Its slot count is 75; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $rus5 (Region code): Region code: us5; ^b (Biweekly): The server wipes on a two-week cycle; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; NA (North America): You will find it under North America in the browser in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS?
Rust Server Score lists that include (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS: 3x Rust servers, graded, Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks; Gather rate: 3x.
Rules and settings
What settings and rules apply on (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS?
(US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS sets gather at 3x, as its name suggests. With no change from the game default, groups take up to 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
The game generates the procedural map on (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS at size 3,500 with seed 1337. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. The name of the map reads: Transylvania .
Getting in
How do you get onto (US) Guts & Glory | PvE & PvP | X3 | CHILL | EVENTS?
To connect, start Rust, press F1, and type client.connect 91.229.114.45:28107. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp75,ptrak,$rus5,v2635,^b,NA,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp75
Max playersIts slot count is 75.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rus5
Region codeRegion code: us5.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
Region
NA
North AmericaYou will find it under North America in the browser.
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 uptime (A+); population is the one to work on (F).