Station XX-15423 · no signal
TeamKit essai
Offline 82.64.202.252:28015 checked 7d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,423
- top 69%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 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 69% of all ranked servers, and #627 of the quad servers (top 76%). 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.1 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Tue 20 Oct, 17:39 UTC8d ago | M0.0■steady | 0 | – | running | 0 | |
| Mon 19 Oct, 15:36 UTC9d ago | M0.0■steady | 0 | – | 1.1 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 TeamKit essai?
A procedural map runs on TeamKit essai, generated by the game.
Which settings and rules apply on TeamKit essai?
The name of TeamKit essai gives no gather rate. You can have up to 4 players in a group (quad). It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on TeamKit essai?
TeamKit essai is not responding at this moment and is offline, last seen 7 days 14 hours ago. Averaged across the last seven days, the population was 0 players.
How does TeamKit essai rank against other Rust servers?
Over the last seven days, TeamKit essai recorded enough player hours to reach #15,423 worldwide, placing it in the top 69% of all ranked servers. It sits at #627 among quad servers.
Operator and location
How reliably does TeamKit essai stay online?
As recorded now, TeamKit essai is not reachable, the last contact having been 7 days 14 hours ago. It was up 4% of the time across the last 7 full days: 6 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 17 October 2026.
Which region does TeamKit essai run from?
No region is published by TeamKit essai. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 82.64.202.252:28015.
What build of Rust does TeamKit essai use?
TeamKit essai is running Rust network protocol 2634 and build 167781 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on TeamKit essai?
On average, the busiest point of its recent wipes drew 0 players. 0 hours into the latest wipe, the crowd reached its peak.
How often does TeamKit essai wipe, and on which days?
On record so far are too few of TeamKit essai's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 10 days 22 hours is how long the current world has been running.
Lists and tags
What do the server tags on TeamKit essai mean?
The game's server browser reads the tags TeamKit essai publishes: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): The server has 10 slots; ts4 (Group limit): Teams are capped at 4 players; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): The game is changed by plugins or settings, placing it 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 TeamKit essai appear?
You will find TeamKit essai on the following Rust Server Trends lists: 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: Quad; Last wipe: In the last 2 weeks.
Join the server
What steps get you onto TeamKit essai?
To join, enter client.connect 82.64.202.252:28015 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.