On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 10000% full
7-day average0peak –
Rank#15,341top 69%
Last wipe58d agono schedule published
Next wipe–no wipe 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 1,000 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,341 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
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 216 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
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 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. 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
You'll find no region listed by TJA4-TEST. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 64.31.32.5:28015.
How dependable is TJA4-TEST, and is it online at the moment?
Right now, TJA4-TEST is online. About 8 days 22 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. On 13 September 2026, Rust Server Score saw it for the first time.
Is TJA4-TEST smooth to play on?
The average over the last 48 hours was 223 server fps, and it never went below 194. At its peak, it held 15,158 entities, including buildings, deployables and all else in the world. At its highest, it used 5,524 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is TJA4-TEST running?
You will find TJA4-TEST on Rust network protocol 2632 and build 161125, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
When does TJA4-TEST wipe, and how often?
The record holds too few of TJA4-TEST's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 58 days 15 hours have passed since this world was made.
Player count
Where does TJA4-TEST sit among Rust servers?
Over the last seven days, TJA4-TEST has #15,341 for player hours, in the top 69% of all ranked servers.
What does the population on TJA4-TEST look like?
With 1,000 slots available, TJA4-TEST currently has 0 players. Over the past seven days, the average player count was 0.
Lists and filters
What do TJA4-TEST's tags stand for?
You'll see TJA4-TEST tagged with gmrust (Game mode): Survival in the standard Rust style; mp1000 (Max players): 1,000 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2632 (Protocol): Join only if your game runs protocol 2632; cs161125 (Build): This runs on build 161125; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is 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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does TJA4-TEST appear in the Rust Server Score lists and filters?
These Rust Server Score lists count TJA4-TEST 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.
Rules and settings
What settings and rules apply on TJA4-TEST?
You will find no gather rate in the name of TJA4-TEST. The default of 8 players applies as the group cap. 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. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
TJA4-TEST runs which map?
TJA4-TEST runs a game-generated procedural map at size 2,000, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to TJA4-TEST?
Enter client.connect 64.31.32.5:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp1000,ptrak,$r?,v2632,gmrust,cs161125,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1000
Max players1,000 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2632
ProtocolJoin only if your game runs protocol 2632.
cs161125
BuildThis runs on build 161125.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is 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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).