Station XX-15349 · no signal
Triple Threat 1v1v1v1
Offline 73.14.233.219:28015 checked 7d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,349
- top 69%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 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, measured since 18 Oct. 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
- 0.8 daysbetween real wipes
- wipe-day peak
- 2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 19 Oct, 00:48 UTC10d ago | M0.3▲rising | 2 | – | running | 0 | |
| Sun 18 Oct, 04:26 UTC11d ago | M0.0▲rising | 2 | – | 0.8 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 pageMap and rules
Which map is running on Triple Threat 1v1v1v1?
Generated by the game, the map on Triple Threat 1v1v1v1 is procedural, size 2,000 with seed 1337. Size and seed produce the same map, so RustMaps can show it from this page. Its map carries the name Custom Map.
Which settings and rules apply on Triple Threat 1v1v1v1?
You will find no gather rate in the name of Triple Threat 1v1v1v1. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on Triple Threat 1v1v1v1 right now?
Triple Threat 1v1v1v1 is not responding at this moment and is offline, last seen 7 days 18 hours ago. The seven-day average for this server is 0 players.
How does Triple Threat 1v1v1v1 rank against other Rust servers?
The last seven days of player hours place Triple Threat 1v1v1v1 at #15,349, in the top 69% of all ranked servers.
Server facts
How reliably does Triple Threat 1v1v1v1 stay online?
As recorded now, Triple Threat 1v1v1v1 is not reachable, the last contact having been 7 days 18 hours ago. It was up 2% of the time across the last 7 full days: 4 of 168 hours. 17 October 2026 is when Rust Server Trends first recorded it.
Which region does Triple Threat 1v1v1v1 run from?
A region is not published by Triple Threat 1v1v1v1. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 73.14.233.219:28015.
Which Rust version is Triple Threat 1v1v1v1 running?
On Windows, Triple Threat 1v1v1v1 runs Rust network protocol 2634 and build 167781. 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 Triple Threat 1v1v1v1?
On average, the busiest point of its recent wipes drew 2 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does Triple Threat 1v1v1v1 wipe, and on which days?
On record so far are too few of Triple Threat 1v1v1v1's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 10 days 21 hours.
Tags
What do the server tags on Triple Threat 1v1v1v1 mean?
Tags published by Triple Threat 1v1v1v1 and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp4 (Max players): Slots: 4; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Triple Threat 1v1v1v1 appear?
The Rust Server Trends lists that take in Triple Threat 1v1v1v1 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; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto Triple Threat 1v1v1v1?
To join, enter client.connect 73.14.233.219:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.