On the class lists: F (35), with population over 48 hours and no performance mark.
Players now0/ 80% full
7-day average0peak 2
Rank#9,476top 43%
Last wipe11d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 8 on average. Plenty of space to grow.
Standingrank on player hours
57/ 100
C−
Working its way up from the back of the class: #9,476 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: 223 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
24/ 100
F
Lost ground: down 5,017 places this week. A strong wipe could turn it round.
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 12 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 43% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W····W·
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap5.1 daysbetween real wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 4
The first 48 hours of its last wipes
Sat 17 OctMon 12 Oct
Players each hour, from the hour of the wipe. The latest peaked at 4, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 17 Oct, 02:57 UTC11d ago
4
–
running
0
Mon 12 Oct, 00:43 UTC16d ago
3
halved by day 4
5.1 days
1
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
You'll find no region listed by CODYS SOLO SERVER. Rust Server Score takes the server's word for its location and does not trace the hardware. 157.85.91.144:21139 is the address to use.
How reliable is CODYS SOLO SERVER, and is it up?
Right now, CODYS SOLO SERVER is online. The uptime it reports puts the last restart at about 5 days 14 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 11 October 2026, Rust Server Score saw it for the first time.
Does CODYS SOLO SERVER perform well?
The average over the last 48 hours was 223 server fps, and it never went below 196. Up to 30,544 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 4,012 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does CODYS SOLO SERVER sit?
The server CODYS SOLO SERVER is on Rust network protocol 2635 and build 167781 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does CODYS SOLO SERVER reset?
There are too few wipes on record for CODYS SOLO SERVER to show a rhythm. 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 11 days 18 hours.
What should you expect from wipe day on CODYS SOLO SERVER?
Across its recent wipes, the busiest moments averaged 4 players. 0 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 4 is when it sank below half in the wipes that did not hold.
Player numbers
Where does CODYS SOLO SERVER sit among Rust servers?
Over the last seven days, CODYS SOLO SERVER has #9,476 for player hours, in the top 43% of all ranked servers.
What does the population on CODYS SOLO SERVER look like?
With 8 slots available, CODYS SOLO SERVER currently has 0 players. The seven-day average is 0 players, with a peak of 2.
Tags and filters
How should you read the tags on CODYS SOLO SERVER?
You'll see CODYS SOLO SERVER tagged with gmrust (Game mode): Survival in the standard Rust style; mp8 (Max players): The server holds 8 slots; 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; cs167781 (Build): The game build is 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show CODYS SOLO SERVER?
These Rust Server Score lists count CODYS SOLO SERVER among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
What settings and rules apply on CODYS SOLO SERVER?
The name of CODYS SOLO SERVER gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Can you tell me which map CODYS SOLO SERVER uses?
A procedural map of size 2,500 and seed 744831120, generated by the game, is what CODYS SOLO SERVER runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto CODYS SOLO SERVER?
To connect, start Rust, press F1, and type client.connect 157.85.91.144:21139. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp8
Max playersThe server holds 8 slots.
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.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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).