Station XX-15849 · no signal
Olo testing
Offline 80.57.92.220:25565 checked 19d ago
- Players now
- 0/ 2
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,849
- top 72%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 2.6 daysbetween real wipes
- on rhythm
- 0%of its recent wipes
- wipe-day peak
- 2players, 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 2, 20 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 18:34 UTC FW27d ago | M0.0▲rising | 2 | – | running | 1 | |
| Sun 27 Sep, 11:18 UTC31d ago | M0.0▲rising | 2 | held half | 4.3 days | 1 | |
| Sat 26 Sep, 15:27 UTC32d ago | M0.3▲rising | 2 | – | 0.8 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 pageMap and rules
Which map is running on Olo testing?
A procedural map runs on Olo testing, generated by the game.
Which settings and rules apply on Olo testing?
The name of Olo testing gives no gather rate. The group limit is 8 players, the game's default. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on Olo testing?
No players are recorded on Olo testing at this moment; it is offline, and the last sighting was 19 days 9 hours ago.
How does Olo testing rank against other Rust servers?
On player hours for the past week, Olo testing sits at #15,849, which puts it inside the top 72% of every ranked server.
Server facts
How reliably does Olo testing stay online?
No contact with Olo testing right now, and the last recorded contact was 19 days 9 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 26 September 2026.
Where in the world is Olo testing hosted?
No region is published by Olo testing. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 80.57.92.220:25565.
What build of Rust does Olo testing use?
Olo testing is running Rust network protocol 2634 and build 166586 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on Olo testing?
2 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 20 hours after the wipe. Until the next wipe the crowd remained above half that peak in 100% of its recent wipes.
On what timetable does Olo testing run its wipes?
No next wipe can be predicted for Olo testing, which wipes at irregular times. 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 27 days 12 hours.
Server tags
What do the server tags on Olo testing mean?
Tags published by Olo testing and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp2 (Max players): 2 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166586 (Build): It runs game build 166586; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed 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 Olo testing appear?
These Rust Server Trends lists include Olo testing: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
What steps get you onto Olo testing?
You can connect by pressing F1 in Rust and typing client.connect 80.57.92.220:25565 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.