☕ Maintaining it costs money
Logo TrackBans Reducido
Jeremyssz's avatar

Jeremyssz

76561198834340606 Steam ID
2005 hrs CS2 Hours
No VAC Ban
Analyzed by TrackBans AI on 09/04/2026 01:42
AI Cheat Probability
--%
Calculating...
Legit 0% Suspicious 50% Cheating 100%

AI Analysis Report

FACEIT ELO: 947 · Level 4
Player Analysis
Aim ScoreNORMAL
81/100
+55% avg 52/100 for this ELO range
Headshot %NORMAL
47.6%
+13% avg 42.0% for this ELO range
AccuracyNORMAL
8.9%
-25% avg 11.9% for this ELO range
FACEIT K/DNORMAL
0.84
-4% avg 0.87 for this ELO range
Reaction TimeNORMAL
0.615s
avg: 0.665s for this ELO range
KASTNORMAL
68.5%
avg: 67.9% for this ELO range
HLTV 2.0NORMAL
1.09
avg: 1.05 for this ELO range
Pre-AimSUSPICIOUS
7.1
avg: 10.2 for this ELO range
Time to KillNORMAL
1.027s
avg: 0.790s for this ELO range
Opening DuelsNORMAL
45.9%
avg: 48.8% for this ELO range
ADRNORMAL
81.9
avg: 77.4 for this ELO range
Win RateNORMAL
50.7%
avg: 50.7% for this ELO range
AWP AccNORMAL
40.6%
avg: 37.3% for this ELO range
PerformanceELEVATED
65.8
avg: 45.8 for this ELO range
Account TrustNORMAL
46.6
avg: 38.3 for this ELO range
Social RiskNORMAL
19.5
avg: 31.1 for this ELO range
avg for this ELO range
This profile has been analyzed 2 times
Data sourcesSteam ProfileGames ListStatsLeetifyFACEIT
(Probability: 0.02)

Supporting Evidence:

  • Clean Network: Social connections show low ban rates typical of legitimate players

Take Action

Review the analysis and decide your next steps.

This is a statistical analysis based on public data. Confidence is not 100% accurate. Results should be considered alongside other factors when making decisions.

FAQ

Frequently Asked Questions

What does TrackBans say about this player?

Jeremyssz has been analyzed by our AI. The score is based on 180+ public stats, not gameplay demos.

How many CS2 hours does this profile have?

According to Steam, the account has logged 2005 hours in Counter-Strike 2.

What does the percentage actually mean?

It reflects how closely this account's patterns match those of already-banned users. 0-29% low risk, 30-49% caution, 50-79% suspicious, 80-100% high risk.

Can the AI make mistakes?

Yes — statistical models can yield false positives/negatives. If you believe the result is wrong, re-analyse after a few days; fresh data may change the outcome.

How reliable is TrackBans for CS2 cheat detection?

Our AI model achieves 86.29% F1-Score and 93.60% ROC-AUC, trained on 204,000+ profiles.

Scroll al inicio