TacticPod IQ

Performance Centre
Session
No Pod Data Loaded
Not connected
Team/Match Settings
Measurement units
Upload any browser-supported image format; it is resized and stored as PNG. For the cleanest result, use a PNG with a transparent background. Other formats or non-transparent images may show a solid background. Search images or paste a direct image link, open it, then use Save image as and upload the image. The app cannot confirm usage rights.
No team logo uploaded
Squad Total Distance
0.0 KM
Team Top Speed
0.0 KM/H
Total Sprints
0
Avg Workload
0
Squad Physical Matrix
Player Pos Min Dist (km) HSR (m) Top Speed (km/h) Sprints Expl. A/D Mech. Load
Advanced metrics
Sensor-derived estimates, not injury diagnoses. Postural slump compares mean absolute upper-trunk angle (atan2(Ay, Az)) during running at ≥19.8 km/h in the early and late match; increases above 15% are flagged. Step-shock asymmetry compares alternating vertical-acceleration peaks at ≥7 km/h; use foot-strike side labels when available. High-g contacts (≥4 g) are heuristically grouped as aerial duels near jump markers, heavy falls when rotation is ≥180 degrees/s or speed is below 7 km/h, and shoulder tackles otherwise. S/A/F means shoulder/aerial/fall. Verify events against video.
PlayerMechanical load (AU)Explosive accel.Explosive decel.Load asym.Slump changeStep shock asym.Contacts (total; S/A/F)
Device data format
Required per sample: time_seconds, x/y in metres (0-105 / 0-68 for football), and speed_kmh. Optional IMU: accel_x/accel_y/accel_z in m/s²; impact_g in g; jump_detected (true/false); omega_x/omega_y in degrees/s; foot_strike_side (left/right); left_load/right_load as same-unit per-sample values. Missing sensor inputs show as unavailable. Explosive running counts use the existing ±3 m/s² speed-derived threshold.
Speed Profile & Velocity Chart
Impact peaks (≥3 g) and jump markers use optional impact_g and jump_detected samples.

Player comparison

Compare normalized match metrics for two players over the included periods.

Load at least two players with GPS data to compare them.

MetricPlayer APlayer B

The radar scales each metric against the higher of these two players. Contact events are sensor-derived estimates and may be unavailable.

Potential Highlights 0 FOUND
Moments flagged from GPS movement patterns.
Scans 8-second windows for fast forward movement or sprint surges. GPS-only suggestions: without ball or possession data, counter-attacks cannot be confirmed.
Import player GPS data to scan for fast transitions, team surges, and sprint bursts.
Tactical Pitch & Heatmaps
Off-pitch points are hidden. GPS error and actual movement beyond the lines can both contribute.
A B
Turn on the grid to click pitch zones or choose them below. Click again to deselect.
LowerHigher activity
Cumulative mode builds to the playhead; Time window centers on it. Last 10 min or Full match controls the available history.
Match time 120:00 / 120:00
Focus the timeline slider or controls and use ← / → to step. Change step size above.
00:00
Player dots and recent GPS trails are shown at the selected match time. Replay uses available GPS tracks; it does not reconstruct ball or possession events.