Working its way up from the back of the class: #15,490 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
49/ 100
D
Slipped a little: down 336 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); 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.
AveragePeakWipe
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.
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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h.
The 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
In what location does Void's Vibe Coding - Script Testing sit?
No region is published for Void's Vibe Coding - Script Testing. Rust Server Score takes the server's word for its location and does not trace the hardware. 162.244.125.185:28015 is the address to use.
How dependable is Void's Vibe Coding - Script Testing, and is it online at the moment?
The server is down: Void's Vibe Coding - Script Testing is offline now, with the last sighting 41 days 9 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is Void's Vibe Coding - Script Testing on?
The server Void's Vibe Coding - Script Testing is on Rust network protocol 2633 and build 164530 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Void's Vibe Coding - Script Testing wipe its map?
The estimate for Void's Vibe Coding - Script Testing's next wipe comes from the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 54 days 20 hours have passed since this world was made. Its tags record that it wipes monthly.
Player numbers
What position does Void's Vibe Coding - Script Testing hold in the rankings?
In the top 69% of all ranked servers, Void's Vibe Coding - Script Testing sits at #15,490 for player hours over the last seven days.
What does the population on Void's Vibe Coding - Script Testing look like?
It has been 41 days 9 hours since Void's Vibe Coding - Script Testing was last seen, and it is offline right now.
Tags and filters
How should you read the tags on Void's Vibe Coding - Script Testing?
The game's browser takes its cue from the tags Void's Vibe Coding - Script Testing has set: gmvanilla (Game mode): This is vanilla survival; mp350 (Max players): 350 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^p (PvE): The danger comes from the world, not from other players; ^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. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Void's Vibe Coding - Script Testing appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Void's Vibe Coding - Script Testing: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: Monthly ^m, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
What settings and rules apply on Void's Vibe Coding - Script Testing?
The name of Void's Vibe Coding - Script Testing gives no gather rate. The default of 8 players applies as the group cap. It runs pve, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Void's Vibe Coding - Script Testing uses?
Void's Vibe Coding - Script Testing runs a game-generated procedural map at size 4,500, seed 1646099129. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
What is the way to join Void's Vibe Coding - Script Testing?
Enter client.connect 162.244.125.185: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 asmp350,ptrak,$r?,v2633,^m,^p,gmvanilla,cs164530,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp350
Max players350 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
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 momentum (D); standing is the one to work on (F).