A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
54/ 100
D
Working its way up from the back of the class: #10,107 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
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
55/ 100
C−
Moving up: up 1,060 places this week.
A fair term, with more to come.
Strongest in wipe hold (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
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 46% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
16 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W··W
·WWWW·W
WWW····
····WWW
··WW···
··W····
··
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 gap0.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Wed 21 OctThu 15 OctWed 14 Oct
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
Wed 21 Oct, 12:41 UTC6d ago
1
–
running
0
Thu 15 Oct, 12:50 UTC12d ago
1
–
6 days
0
Wed 14 Oct, 18:26 UTC13d ago
1
–
0.8 days
0
Sun 11 Oct, 03:29 UTC16d ago
1
✓ held half
3.6 days
1
Sat 10 Oct, 08:08 UTC17d ago
1
–
0.8 days
0
Fri 9 Oct, 22:26 UTC17d ago
1
–
0.4 days
1
Wed 30 Sep, 11:49 UTC27d ago
2
–
9.4 days
1
Tue 29 Sep, 09:38 UTC28d ago
2
–
1.1 days
0
Mon 28 Sep, 14:40 UTC29d ago
2
–
0.8 days
0
Sun 27 Sep, 10:26 UTC30d ago
1
–
1.2 days
1
Fri 25 Sep, 10:52 UTC32d ago
1
–
2 days
2
Thu 24 Sep, 12:03 UTC33d ago
2
–
1 days
0
Wed 23 Sep, 09:14 UTC34d ago
2
–
1.1 days
0
Tue 22 Sep, 06:49 UTC35d ago
1
–
1.1 days
1
Sun 20 Sep, 06:59 UTC37d ago
1
–
2 days
0
Thu 17 Sep, 00:41 UTC40d ago
0
–
3.3 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
In what location does Vitality Local LiveTest sit?
No region is published for Vitality Local LiveTest. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 91.245.44.75:28018.
How dependable is Vitality Local LiveTest, and is it online at the moment?
At this moment, Vitality Local LiveTest is offline; the last time it was seen was 44 minutes ago. It was up 39% of the time over the last 7 full days, 66 of 168 hours. It was first seen by Rust Server Score on 16 September 2026.
On what Rust version does Vitality Local LiveTest sit?
You will find Vitality Local LiveTest on Rust network protocol 2635 and build 168909, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Vitality Local LiveTest wipe its map?
There is no next wipe to predict on Vitality Local LiveTest, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 12 days 9 hours have passed since this world was made.
What should you expect from wipe day on Vitality Local LiveTest?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 100% of its recent wipes.
Player numbers
Where does Vitality Local LiveTest sit among Rust servers?
In the top 46% of all ranked servers, Vitality Local LiveTest sits at #10,107 for player hours over the last seven days.
Is Vitality Local LiveTest a busy server?
The last sighting of Vitality Local LiveTest was 44 minutes ago, and it is offline right now. It peaked at 1 and averaged 0 players over the last seven days.
Lists and filters
What do Vitality Local LiveTest's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): 10 slots are available; ts32 (Group limit): A team can hold 32 players at most; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Vitality Local LiveTest 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.
Which Rust Server Score filters and lists feature Vitality Local LiveTest?
Rust Server Score lists that include Vitality Local LiveTest: 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; Last wipe: In the last 2 weeks.
Server rules
How is Vitality Local LiveTest set up, and what rules does it keep?
Nothing in the name of Vitality Local LiveTest states a gather rate. The limit for a group is 32 players. survival is the mode here, gather, build and raid, as in 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map Vitality Local LiveTest uses?
A procedural map, generated by the game, is what Vitality Local LiveTest runs.
Connecting
How do you get onto Vitality Local LiveTest?
To connect, start Rust, press F1, and type client.connect 91.245.44.75:28018. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts32,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max players10 slots are available.
ts32
Group limitA team can hold 32 players at most.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: 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 fair term, with more to come. Strongest in wipe hold (A+); population is the one to work on (F).