RUST METRICSFlight deck · live data
Data live Servers11,685 Players51,425 Populated3,180 Fresh wipes 3 h127 Scan5 min
‹ All servers87.117.33.33:28015
Online Full Queue Fresh wipe Wipe due No query

TEAM PROJECT

Online EU 87.117.33.33:28015 checked 9m ago

weekly wipes vanillamoddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 38 75 112 150 PAX 0 /150

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak 1
Rank#14,527top 65% · #2488 in EU
Last wipe5d agoweekly schedule
Next wipe1d 8hFri 30 Oct, 18:11 UTC
Memory–48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75107:0008:00

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 65% of all ranked servers, top 85% in EU. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Friday 30 October, 18:11 UTC, in 1d 8h. Its weekly schedule tag · low confidence

usual gap9.1 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak1players, last three wipes
crowd held50%else halves by day 3

Coming wipes

  1. WPT 1Fri 30 Oct, 18:11 UTC1d 8h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 9hFW
  3. WPT 3Fri 6 Nov, 18:11 UTC8d 8h
  4. WPT 4Fri 13 Nov, 18:11 UTC15d 8h
  5. WPT 5Fri 20 Nov, 18:11 UTC22d 8h
  6. WPT 6Fri 27 Nov, 18:11 UTC29d 8h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 9hFW
  8. WPT 8Fri 4 Dec, 18:11 UTC36d 8h

The first 48 hours of its last wipes

Fri 23 OctWed 14 OctSun 4 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 18:11 UTC5d ago 1 – running 0
Wed 14 Oct, 16:46 UTC14d ago 1 held half 9.1 days 1
Sun 4 Oct, 16:50 UTC24d ago 0 – 10 days 1
Tue 22 Sep, 18:39 UTC36d ago 1 halved by day 3 11.9 days 0
Sun 20 Sep, 08:43 UTC39d ago 0 – 2.4 days 1
Sun 13 Sep, 19:56 UTC45d ago 0 – 6.5 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on TEAM PROJECT when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 50% of its recent wipes. When it didn't hold, by day 3 it fell below half.

How often does TEAM PROJECT wipe, and when?

Its tag guides the prediction: too few of TEAM PROJECT's wipes are on record to confirm its schedule. On Friday 30 October at 18:11 UTC its next wipe is due. 5 days 15 hours ago the current world was made. A weekly wipe schedule is published in its tags.

Tags

How should you read the tags on TEAM PROJECT?

These are the tags TEAM PROJECT publishes, and the server browser reads them: gmvanilla (Game mode): The mode is vanilla survival; mp150 (Max players): Slots: 150; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^w (Weekly): Wipe cycle: weekly; ^v (Vanilla): Rates, kits and rules are exactly as Facepunch ships them; ^i (Battlefield): Fast PvP served by kits and boosted rates; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; EU (Europe): The server browser files it under Europe. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show TEAM PROJECT?

On Rust Metrics, TEAM PROJECT sits in these lists: EU Rust servers, checked, Modded Rust servers, checked live and Rust battlefield servers: check the readings. Reading: server list filters. It comes up under Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Battlefield ^i, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last week.

Player count

Where does TEAM PROJECT sit in the rankings?

Player hours over the last seven days put TEAM PROJECT at #14,527, #2,488 in Europe, in the top 65% of all ranked servers.

What is the population on TEAM PROJECT?

Current headcount on TEAM PROJECT: 0 players, 150 slots available. Seven-day check: 0 players on average. Peak reading: 1. Check: 48-hour peak. 08:00 UTC, 0 players on average.

Server

Which location does TEAM PROJECT run from?

TEAM PROJECT gives Europe as its location, with the EU tag. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 87.117.33.33:28015.

What Rust version is TEAM PROJECT on?

Reading: TEAM PROJECT, Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is TEAM PROJECT up, and how often does it stay up?

TEAM PROJECT reports online. Status: normal. Uptime for the last 7 full days: 1 of 168 hours, or 1%. The first sighting on Rust Metrics was 13 September 2026.

Settings and map

What settings and rules apply on TEAM PROJECT?

Check: gather rate. The name TEAM PROJECT does not state one. 8 players per group, the default value. The mode is battlefield. Note the following: high rates and kits for fast PvP. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. The server calls itself vanilla, with this meaning: rates, kits and rules are exactly as Facepunch ships them. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TEAM PROJECT?

From seed 1337, the game generates the procedural map on TEAM PROJECT. Its size is 1,750. View it on RustMaps from this page: matching size and seed give an identical map. Map name, as listed: Custom Map.

Join

How can you get onto TEAM PROJECT?

Check: join. Open Rust, press F1, then enter client.connect 87.117.33.33:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp150,ptrak,$r?,v2635,^w,^v,^i,EU,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode The mode is vanilla survival.
mp150
Max players Slots: 150.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Difficulty

^v
Vanilla Rates, kits and rules are exactly as Facepunch ships them.

Gameplay

^i
Battlefield Fast PvP served by kits and boosted rates.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

Region

EU
Europe The server browser files it under Europe.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.