Last Night Test [TP|Kits|Events|Bosses]
Offline 109.195.21.162:29015 checked 2d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 48% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 6d 12h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC6d 12hFW
- WPT 2Tue 10 Nov, 19:00 UTC11d 12h
- WPT 3Tue 24 Nov, 19:00 UTC25d 12h
- WPT 4Thu 3 Dec, 19:00 UTC34d 12hFW
- WPT 5Tue 8 Dec, 19:00 UTC39d 12h
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 |
|---|---|---|---|---|
| Tue 27 Oct, 19:00 UTC2d ago | 1 | – | running | 0 |
| Thu 1 Oct, 18:21 UTC FW28d ago | 1 | halved by day 2 | 26 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- 5/15
- 4/100
- 2/100
- 1/100
- 3/100
- 0/40
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on Last Night Test [TP|Kits|Events|Bosses]?
An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 2 when it didn't.
When does Last Night Test [TP|Kits|Events|Bosses] wipe?
Its tag guides the prediction: too few of Last Night Test [TP|Kits|Events|Bosses]'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. The world in play was created 2 days 11 hours ago. A wipe schedule of every two weeks is published in its tags.
Tags
Which tags does Last Night Test [TP|Kits|Events|Bosses] carry, and what do they mean?
Tags published by Last Night Test [TP|Kits|Events|Bosses], read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^d (Combat training): Loot is handed to you on this training server for aim and PvP work; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show Last Night Test [TP|Kits|Events|Bosses]?
These Rust Metrics lists carry Last Night Test [TP|Kits|Events|Bosses]: Modded Rust servers, checked live and Aim training servers, live readings. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Biweekly ^b, Combat training ^d, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 3 days.
Occupancy
What position does Last Night Test [TP|Kits|Events|Bosses] hold among Rust servers?
Player hours over seven days put Last Night Test [TP|Kits|Events|Bosses] at #10,681, in the top 48% of all ranked servers.
What is the population on Last Night Test [TP|Kits|Events|Bosses]?
Last Night Test [TP|Kits|Events|Bosses] is not responding; status offline, last seen 2 days 8 hours ago. Check: players over seven days. Average 1, peak 1.
Server details
Where does Last Night Test [TP|Kits|Events|Bosses] sit?
No region tag on Last Night Test [TP|Kits|Events|Bosses]. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 109.195.21.162:29015.
What Rust version is Last Night Test [TP|Kits|Events|Bosses] on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by Last Night Test [TP|Kits|Events|Bosses]. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on Last Night Test [TP|Kits|Events|Bosses], and is it online?
Last Night Test [TP|Kits|Events|Bosses] reports offline. The last reading came 2 days 8 hours ago. Uptime for the last 7 full days: 4 of 168 hours, or 2%. The first sighting on Rust Metrics was 17 September 2026.
Map and rules
What rules does Last Night Test [TP|Kits|Events|Bosses] enforce, and what are its settings?
Check: gather rate. The name Last Night Test [TP|Kits|Events|Bosses] does not state one. 8 players per group, the default value. Mode check gives combat training; practice for aim and PvP, loot provided. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
What map is Last Night Test [TP|Kits|Events|Bosses] on?
Check: map. Procedural, size 3,000, seed 851509239, generated by the game on Last Night Test [TP|Kits|Events|Bosses]. View it on RustMaps from this page: matching size and seed give an identical map.
How to join
What do you do to join Last Night Test [TP|Kits|Events|Bosses]?
Press F1 in Rust and enter client.connect 109.195.21.162:29015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. You can find its website at https://wargm.ru/server/64488.