On the class lists: F (41), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 3
Rank#5,980top 27%
Last wipe13d agobiweekly schedule
Next wipe8hThu 29 Oct, 05:11 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
73/ 100
B−
Holds a respectable place: #5,980 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 69 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
38/ 100
F
Slipped a little: down 1,421 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 27% 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
from its schedule tag
Next wipe Thursday 29 October, 05:11 UTC, in 8h.
Its biweekly schedule tag · low confidence
usual gap14 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 7
Coming wipes
8hThu 29 Oct, 05:11 UTC
7d 22hThu 5 Nov, 19:00 UTCFW
14d 8hThu 12 Nov, 05:11 UTC
28d 8hThu 26 Nov, 05:11 UTC
35d 22hThu 3 Dec, 19:00 UTCFW
42d 8hThu 10 Dec, 05:11 UTC
The first 48 hours of its last wipes
Thu 15 OctFri 2 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 32 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 05:11 UTC13d ago
2
–
running
0
Fri 2 Oct, 18:30 UTC26d ago
3
halved by day 1
12.4 days
0
Thu 17 Sep, 04:40 UTC41d ago
2
halved by day 13
15.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
In what location does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES sit?
PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 89.207.66.19:28016.
Is PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES up, and how steady is its uptime?
Right now, PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES is online. About 13 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
How well does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES run?
It averaged 69 server fps over the last 48 hours, with a low of 60. Up to 99,526 entities were in the world, covering buildings, deployables and the rest. Up to 4,072 MB of memory was used. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES sit?
You will find PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES wipe, and how often?
Too few wipes on PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Thursday 29 October at 05:11 UTC. The world it runs now was created 13 days 15 hours. A fortnightly wipe schedule appears in its tags.
What should you expect from wipe day on PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES?
Recent wipes have peaked at 2 players on average. 32 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 7.
Population
Where does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES sit among Rust servers?
Over the last seven days, PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES has #5,980 for player hours, in the top 27% of all ranked servers.
Is PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES a busy server?
With 100 slots available, PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES currently has 0 players. The seven-day average is 0 players, with a peak of 3. The busiest time in the last 48 hours was 14:00 UTC, with an average of 0 players.
Tags and filters
How should you read the tags on PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES?
The game's browser takes its cue from the tags PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): The server holds 100 slots; 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): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^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.
Where does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES appear in the Rust Server Score lists and filters?
These Rust Server Score lists count PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES among them: Modded Rust servers, graded. It shows under the following filters on the server list: 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.
Map and rules
Which rules does PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES enforce, and what are its settings?
You will find no gather rate in the name of PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES. The group limit stays at the game's default of 8 players. It runs survival, 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 PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES uses?
PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES runs a game-generated procedural map at size 4,250, seed 1832977638. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How should you connect to PvP | TEAMRUST | SOLO-Max2 | SKIN | KITS | EVENTS | RAID BASES?
Enter client.connect 89.207.66.19:28016 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://team.gamestores.app/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersThe server holds 100 slots.
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 codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
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 performance (A+); population is the one to work on (F).