On the class lists: F (35), with population over 48 hours and no performance mark.
Players now0/ 400% full
7-day average0peak –
Rank#15,335top 69%
Last wipe22d 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 40 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,335 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
100/ 100
A+
Runs smoothly: 198 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
49/ 100
D
Slipped a little: down 373 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
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 28 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······
WW·····
·······
·······
····
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.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 3
The first 48 hours of its last wipes
Tue 6 OctMon 5 OctMon 28 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Tue 6 Oct, 21:38 UTC22d ago
1
–
running
0
Mon 5 Oct, 22:46 UTC23d ago
1
–
1 days
0
Mon 28 Sep, 01:10 UTC31d ago
2
halved by day 3
7.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 1000x | Cross Rust | Weekly based in?
You'll find no region listed by 1000x | Cross Rust | Weekly. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 135.148.15.102:23565 is the address to use.
Is 1000x | Cross Rust | Weekly up, and how steady is its uptime?
The server is up: 1000x | Cross Rust | Weekly is online now. According to its reported uptime, the last restart was about 2 days 5 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. The first sighting by Rust Server Score was on 28 September 2026.
Does 1000x | Cross Rust | Weekly perform well?
The average over the last 48 hours was 198 server fps, and it never went below 120. Up to 47,272 entities were in the world, covering buildings, deployables and the rest. Up to 3,820 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does 1000x | Cross Rust | Weekly sit?
Rust network protocol 2635 and build 168909 on Linux is what 1000x | Cross Rust | Weekly runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does 1000x | Cross Rust | Weekly wipe, and how often?
1000x | Cross Rust | Weekly wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 22 days 16 hours.
What happens on 1000x | Cross Rust | Weekly when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe. Half the peak held until 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 1000x | Cross Rust | Weekly hold in the rankings?
In the top 69% of all ranked servers, 1000x | Cross Rust | Weekly sits at #15,335 for player hours over the last seven days.
What does the population on 1000x | Cross Rust | Weekly look like?
With 40 slots available, 1000x | Cross Rust | Weekly currently has 0 players. Over the past seven days, the average player count was 0.
Lists and filters
How should you read the tags on 1000x | Cross Rust | Weekly?
gmrust (Game mode): Rust survival, played by the standard rules; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags 1000x | Cross Rust | Weekly publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does 1000x | Cross Rust | Weekly appear in the Rust Server Score lists and filters?
Rust Server Score lists that include 1000x | Cross Rust | Weekly: Rust servers above 10x gather rate and Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: More than 10x.
Server rules
Which rules does 1000x | Cross Rust | Weekly enforce, and what are its settings?
The name of 1000x | Cross Rust | Weekly points to a 1000x gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on 1000x | Cross Rust | Weekly?
A procedural map of size 3,000 and seed 1218474365, generated by the game, is what 1000x | Cross Rust | Weekly runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to 1000x | Cross Rust | Weekly?
To connect, start Rust, press F1, and type client.connect 135.148.15.102:23565. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp40,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp40
Max playersThe server holds 40 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 performance (A+); population is the one to work on (F).