Station XX-15426 · no signal
Warthog Test - local only
Offline 68.97.1.27:28135 checked 6d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,426
- top 69%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 2.3 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 17 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 15 Oct, 03:02 UTC13d ago | M0.0▲rising | 1 | – | running | 0 | |
| Mon 12 Oct, 18:51 UTC15d ago | M0.0■steady | 1 | held half | 2.3 days | 1 |
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 pageRules and settings
Which map is running on Warthog Test - local only?
Warthog Test - local only uses a procedural map, which the game generates.
Which settings and rules apply on Warthog Test - local only?
No gather rate appears in the name of Warthog Test - local only. At the game's default, groups can have up to 8 players. In survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC off, Valve's anti-cheat.
Player counts
How many players are recorded on Warthog Test - local only right now?
No players are recorded on Warthog Test - local only at this moment; it is offline, and the last sighting was 6 days 3 hours ago. Averaged across the last seven days, the population was 0 players.
How does Warthog Test - local only rank against other Rust servers?
On player hours for the past week, Warthog Test - local only sits at #15,426, which puts it inside the top 69% of every ranked server.
Server facts
How reliably does Warthog Test - local only stay online?
No contact with Warthog Test - local only right now, and the last recorded contact was 6 days 3 hours ago. It was up 11% of the time across the last 7 full days: 19 of 168 hours. On 11 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Warthog Test - local only run from?
A region is not published by Warthog Test - local only. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 68.97.1.27:28135 is the address it uses.
Which Rust version is Warthog Test - local only running?
Warthog Test - local only is running Rust network protocol 2634 and build 166652 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Warthog Test - local only?
On average, the busiest point of its recent wipes drew 1 players. 17 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 100% of its recent wipes.
On what timetable does Warthog Test - local only run its wipes?
The rhythm of Warthog Test - local only cannot yet be told: too few of its wipes are on record. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 16 days 20 hours.
Tags
What do the server tags on Warthog Test - local only mean?
Tags published by Warthog Test - local only and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp2 (Max players): The server has 2 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): Game build: 166652; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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 Warthog Test - local only appear?
The Rust Server Trends lists that take in Warthog Test - local only are: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto Warthog Test - local only?
You can connect by pressing F1 in Rust and typing client.connect 68.97.1.27:28135 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.