briter1337
Offline 109.104.223.62:28115 checked 3d ago
Server instruments
no direct query in 48 hoursPlayers now
2% full 7-day avg7-day peakServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 23 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 57% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 72/250
- 106/200
- 327/350
- 20/100
- 419/450
- 304/325
Quick answers
from the figures on this pageWipe timing
How often does briter1337 wipe, and when?
To tell the rhythm of briter1337, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 86 days 23 hours ago the current world was made.
Lists and filters
Which tags does briter1337 carry, and what do they mean?
These are the tags briter1337 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp66 (Max players): Slots: 66; v2635 (Protocol): Match the game version: protocol 2635 is required; cs169224 (Build): The server runs game build 169224; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $reu1 (Region code): The code for this server's region is eu1. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does briter1337 appear in Rust Metrics lists and filters?
Rust Metrics lists featuring briter1337: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all.
Occupancy
Where does briter1337 sit in the rankings?
Player hours over seven days put briter1337 at #12,754, in the top 57% of all ranked servers.
What player count does briter1337 carry?
briter1337 is not responding; status offline, last seen 3 days 4 hours ago. Check: players over seven days. Average 1, peak 1.
Server
Which location does briter1337 run from?
No region comes from briter1337, and its region code is eu1. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 109.104.223.62:28115.
What Rust version is briter1337 on?
Rust network protocol 2635 and build 169224 on Windows is the build briter1337 runs. Matching protocol is required to join. Let Steam update your game.
How reliable is briter1337, and is it online now?
briter1337 reports offline. The last reading came 3 days 4 hours ago. Uptime for the last 7 full days: 2 of 168 hours, or 1%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
How is briter1337 configured, and what rules are in force?
Reading the name gives no gather rate for briter1337. The group limit is not published. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Connection
What do you do to join briter1337?
To join: start Rust, press F1 and type client.connect 109.104.223.62:28115. Or press Launch Rust here and Steam opens the game and connects you.