Station XX-15312 · no signal
Test Server JARVIS
Offline 193.5.238.30:28015 checked 16d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,312
- top 71%
- Last wipe
- 16d ago
- biweekly schedule
- Next wipe
- 7d 0h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 2 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 0h. The force wipe · high confidence
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 7d 0hThu 5 Nov, 19:00 UTCFW
- 11d 23hTue 10 Nov, 18:01 UTC
- 25d 23hTue 24 Nov, 18:01 UTC
- 35d 0hThu 3 Dec, 19:00 UTCFW
- 39d 23hTue 8 Dec, 18:01 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 13 Oct, 18:01 UTC16d ago | M0.0■steady | 0 | – | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which settings and rules apply on Test Server JARVIS?
No gather rate appears in the name of Test Server JARVIS. The group limit is 8 players, the game's default. In build & creative mode, no gathering, only sandbox building. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on Test Server JARVIS right now?
No players are recorded on Test Server JARVIS at this moment; it is offline, and the last sighting was 16 days ago.
How does Test Server JARVIS rank against other Rust servers?
On player hours for the past week, Test Server JARVIS sits at #15,312, which puts it inside the top 71% of every ranked server.
Server details
How reliably does Test Server JARVIS stay online?
Test Server JARVIS is down at the moment; the last recorded contact was 16 days ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 1 October 2026.
Where in the world is Test Server JARVIS hosted?
A region is not published by Test Server JARVIS. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 193.5.238.30:28015 is the address it uses.
Which Rust version is Test Server JARVIS running?
Rust network protocol 2634 and build 167781 on Windows is what Test Server JARVIS runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Test Server JARVIS?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Test Server JARVIS run its wipes?
The prediction follows its tag, because too few of Test Server JARVIS's wipes are on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 16 days. Its tags state that it wipes every two weeks.
Server tags
What do the server tags on Test Server JARVIS mean?
Tags published by Test Server JARVIS and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp2 (Max players): The server has 2 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^b (Biweekly): The wipe cycle is two weeks; ^k (Build server): A place to design and practise bases; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Test Server JARVIS appear?
The Rust Server Trends lists that take in Test Server JARVIS are: Modded Rust servers, tracked live and Rust build and creative servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Biweekly ^b, Build server ^k, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Connecting
How do you connect to Test Server JARVIS?
Enter client.connect 193.5.238.30:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.