On the class lists: F (34), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,339top 69% · #1509 in NA
Last wipe90d agoweekly schedule
Next wipe15hThu 29 Oct, 23:39 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 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
54/ 100
D
Attendance needs work: on the list only 26 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 119 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 214 places this week. Nothing a good wipe can't fix.
A term to build on.
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
No five-minute samples in the last two hours.
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 69% of all ranked servers, top 81% in NA, and #626 of the quad servers (top 76%). Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Thursday 29 October, 23:39 UTC, in 15h.
Weekly: 7 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 sit?
You'll see THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 listed in North America, tagged NA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 216.245.177.16:28025 is the address to use.
How reliable is THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30, and is it up?
You cannot join now: THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 is offline, last seen 22 hours ago. About 23 hours ago, it restarted, based on the uptime it reports. It was up 92% of the time over the last 7 full days, 154 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
Does THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 perform well?
The average over the last 48 hours was 119 server fps, and it never went below 103. Buildings, deployables and everything else in the world added up to as many as 11,731 entities. Up to 930 MB of memory was used. When fps is low and entities climb, that is lag to players.
Which Rust version is THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 running?
Rust network protocol 2631 and build 158240 on Windows is what THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 reset?
The next wipe on THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 is a projection from weekly: 7 days after its last wipe. Expect the next wipe on Thursday 29 October at 23:39 UTC. 90 days 8 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
Population
Where does THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 sit among Rust servers?
In North America, THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 is #1,509, and overall it is #15,339 on player hours over the last seven days, in the top 69% of all ranked servers. It comes #626 among servers in the quad group.
What does the population on THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 look like?
The last sighting of THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 was 22 hours ago, and it is offline right now. A seven-day average of 0 players applies here.
Tags and filters
What do THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30's tags stand for?
The game's browser takes its cue from the tags THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): Its slot count is 50; ts4 (Group limit): No team may go above 4; v2631 (Protocol): To get in, your game needs to be on the same version: the protocol is 2631; cs158240 (Build): Build number: 158240; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; NA (North America): In the server browser it appears under North America. 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 THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30?
Rust Server Score lists that include THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30: 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: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Weekly.
Map and rules
Which rules does THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 enforce, and what are its settings?
You will find no gather rate in the name of THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30. You can have up to 4 players in a group (quad). You get survival here, gather, build and raid, as in 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 THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 uses?
THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30 runs a game-generated procedural map at size 1,300, 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: Custom Map.
Connecting
How should you connect to THIRSTY BEAVER One Grid | 1 Grid | JUST WIPED 7/30?
Enter client.connect 216.245.177.16:28025 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/erAPtnDRzu.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2631,^w,NA,gmrust,cs158240,ts4,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersIts slot count is 50.
ts4
Group limitNo team may go above 4.
v2631
ProtocolTo get in, your game needs to be on the same version: the protocol is 2631.
cs158240
BuildBuild number: 158240.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
NA
North AmericaIn the server browser it appears under North America.
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 performance (A+); population is the one to work on (F).