Foxx Dev
Online NA 107.175.159.174:28025 checked 10m ago
Server instruments
last reading Thu 15:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 66 · below 20 is lag, below 10 is badEntities
48 h range 138,149–142,641 · memory 4,119 MBUptime
22 h 55 min since its last restart, at the last readingPlayers
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 25 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers, top 81% in NA. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 1h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 1hFW
- WPT 2Sun 8 Nov, 07:50 UTC9d 14h
- WPT 3Sun 22 Nov, 07:50 UTC23d 14h
- WPT 4Thu 3 Dec, 19:00 UTC35d 1hFW
- WPT 5Sun 6 Dec, 07:50 UTC37d 14h
The first 48 hours of its last wipes
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 |
|---|---|---|---|---|
| Sun 11 Oct, 07:50 UTC18d ago | 1 | – | running | 1 |
| Sat 3 Oct, 03:37 UTC26d ago | 1 | halved by day 1 | 8.2 days | 0 |
| Mon 28 Sep, 21:39 UTC30d ago | 1 | halved by day 1 | 4.2 days | 0 |
| Fri 25 Sep, 21:11 UTC33d ago | 0 | – | 3 days | 0 |
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
the same kind of game, then region, group limit, rate and wipes- 175/2000
- 64/200
- 20/200
- 15/35
- 9/100
- 6/50
Quick answers
from the figures on this pageReset cycle
What happens on Foxx Dev when wipe day comes?
At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 1 it fell below half.
How often does Foxx Dev wipe, and when?
Its tag guides the prediction: too few of Foxx Dev's wipes are on record to confirm its schedule. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. 18 days 8 hours ago the current world was made. A wipe schedule of every two weeks is published in its tags.
Tags
Which tags does Foxx Dev carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp40 (Max players): The server holds 40 slots; ts12 (Group limit): Teams are capped at 12; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): Check: mode. PvE, so the world supplies the danger, not other players; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): Its browser listing: North America from Foxx Dev. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Who operates Foxx Dev?
Check: operator. Foxx Dev publishes a foxxservers.com hostname, and 3 other servers we track do too. Same operator, most likely.
Where does Foxx Dev appear in Rust Metrics lists and filters?
These Rust Metrics lists carry Foxx Dev: Modded Rust servers, checked live, Rust PvE servers and North America: server readout. These filters bring it up on the server list: Region: North America; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Population
What position does Foxx Dev hold among Rust servers?
Top 69% of all ranked servers: Foxx Dev takes #15,327 on seven-day player hours and #1,502 in North America.
What is the population on Foxx Dev?
0 of 40 slots are filled on Foxx Dev right now. Seven-day reading: 0 players on average.
Server
What location is Foxx Dev hosted in?
Reading: location. The NA tag puts Foxx Dev in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 107.175.159.174:28025.
What Rust version is Foxx Dev on?
Reading: Foxx Dev, Rust network protocol 2635 and build 168909, Linux. Check: protocol. To join, your game must match; Steam handles the update.
What is the performance reading for Foxx Dev?
Over the last 48 hours the average was 95 server fps; the floor was 66. Peak entity count: 142,641. Buildings, deployables and all else included. Memory peak: 5,335 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is Foxx Dev, and is it online now?
Check: connection. Foxx Dev is online at this moment. By its reported uptime, the last restart was roughly 22 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 25 September 2026.
Rules and settings
What rules does Foxx Dev enforce, and what are its settings?
Reading the name gives no gather rate for Foxx Dev. The cap on groups is 12 players. The mode is pve. Note the following: other players are not fought. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
Which map is live on Foxx Dev?
Check: map. Procedural, size 5,000, seed 241644880, generated by the game on Foxx Dev. View it on RustMaps from this page: matching size and seed give an identical map. Read the map name: Fox Island!.
Join
How do you connect to Foxx Dev?
Press F1 in Rust and enter client.connect 107.175.159.174:28025. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.