Station XX-15318 · recording
Tournament 100Pabajo
Online 85.190.159.156:10200 checked 10m ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,318
- top 69%
- Last wipe
- 25d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M0.0■steady+0 players
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 2 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
- 1.5 daysbetween real wipes
- wipe-day peak
- 6players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 10, 21 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 4 Oct, 04:19 UTC25d ago | M1.0▲rising | 10 | – | running | 0 | |
| Fri 2 Oct, 16:35 UTC26d ago | M0.5▲rising | 3 | – | 1.5 days | 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 pageRules and settings
Which map is running on Tournament 100Pabajo?
The procedural map on Tournament 100Pabajo is size 2,000 with seed 1019820938, generated by the game. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on Tournament 100Pabajo?
No gather rate appears in the name of Tournament 100Pabajo. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Player counts
How many players are recorded on Tournament 100Pabajo right now?
A reading taken now shows 0 players on Tournament 100Pabajo, which has 50 slots. The population averaged 0 players over the past week.
How does Tournament 100Pabajo rank against other Rust servers?
On player hours for the past week, Tournament 100Pabajo sits at #15,318, which puts it inside the top 69% of every ranked server.
Operator and location
How reliably does Tournament 100Pabajo stay online?
As recorded now, Tournament 100Pabajo is running. Going by the uptime figure it reports, it restarted about 3 days ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 2 October 2026 it was recorded for the first time by Rust Server Trends.
How well does Tournament 100Pabajo perform under load?
The 48-hour average is 10 server fps; 10 is the lowest observed. At its highest, it carried 19,816 entities: buildings, deployables and the world's other contents. Its highest memory use was 1,680 MB. Low fps together with a growing entity count is what players experience as lag.
Where in the world is Tournament 100Pabajo hosted?
Nothing about a region comes from Tournament 100Pabajo. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 85.190.159.156:10200 is the address it uses.
Which Rust version is Tournament 100Pabajo running?
On Windows, Tournament 100Pabajo runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on Tournament 100Pabajo?
6 players, on average, was the busiest crowd at its recent wipes. 21 hours after the latest wipe, the crowd peaked.
How often does Tournament 100Pabajo wipe, and on which days?
The rhythm of Tournament 100Pabajo 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. 25 days 7 hours is how long the current world has been running.
Tags
What do the server tags on Tournament 100Pabajo mean?
Tags published by Tournament 100Pabajo and read by the game's server browser include gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running 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 Tournament 100Pabajo appear?
The Rust Server Trends lists that take in Tournament 100Pabajo are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
How do you connect to Tournament 100Pabajo?
To join, enter client.connect 85.190.159.156:10200 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.