Working its way up from the back of the class: #15,222 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
40/ 100
F
Slipped a little: down 3,169 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); standing 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.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, top 88% in EU. 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 Saturday 31 October, 05:57 UTC, in 1d 22h.
Biweekly: 14 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
You'll see Test Localhost listed in Europe, tagged EU. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 188.27.130.160:28015 is the address to use.
Is Test Localhost up, and how steady is its uptime?
At this moment, Test Localhost is offline; the last time it was seen was 11 days 23 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. The first sighting by Rust Server Score was on 17 October 2026.
What Rust version is Test Localhost on?
You will find Test Localhost on Rust network protocol 2634 and build 167781, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does Test Localhost reset?
biweekly: 14 days after its last wipe gives the basis for estimating Test Localhost's next wipe. It is due to wipe next on Saturday 31 October at 05:57 UTC. The world it runs now was created 12 days 1 hours. Its tags give a wipe schedule of every two weeks.
Player numbers
What position does Test Localhost hold in the rankings?
Over the last seven days, Test Localhost has #15,222 for player hours, in the top 70% of all ranked servers and #2,592 in Europe.
Is Test Localhost a busy server?
Test Localhost is offline at the moment; the last time it was seen was 11 days 23 hours ago.
Tags
What do Test Localhost's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp5 (Max players): Its slot count is 5; ts5 (Group limit): Teams cap out at 5; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^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; EU (Europe): In the server browser it appears under Europe are the tags Test Localhost publishes, and the game's server browser reads them. 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 Test Localhost appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Test Localhost: European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; 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 Test Localhost enforce, and what are its settings?
The name of Test Localhost gives no gather rate. A group here can reach 5 players. survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
How to join
How should you connect to Test Localhost?
To connect, start Rust, press F1, and type client.connect 188.27.130.160:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2634,^b,EU,gmrust,cs167781,ts5,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp5
Max playersIts slot count is 5.
ts5
Group limitTeams cap out at 5.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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.
Region
EU
EuropeIn the server browser it appears under Europe.
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 momentum (F); standing is the one to work on (F).