Browse State-of-the-Art › Multiple Object Tracking

Multiple Object Tracking

149 papers with code · 11 benchmarks · 18 datasets archive 2025-07-28

Computer Vision

Multiple Object Tracking is the problem of automatically identifying multiple objects in a video and representing them as a set of trajectories with high accuracy.

Source: SOT for MOT

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

11 leaderboard tables shown for this task, 11 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted. 10 shown of 11 until expanded.

Syntology 3 newer papers were judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): SportsMOT (2 judged, 0 placed), BDD100K val (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
KITTI Test (Online Methods) (34 rows) RobMOT (Dynamic) Towards Accurate State Estimation: Kalman Filter Incorporating... — — Compare
SportsMOT (19 rows) DeepEIoU + GTA GTA: Global Tracklet Association for Multi-Object Tracking in Sports code — Compare
BDD100K val (9 rows) ByteTrack ByteTrack: Multi-Object Tracking by Associating Every Detection Box code Syntology official (archive's flag): 4 ran · 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified Compare
BDD100K test (5 rows) ContrasTR Contrastive Learning for Multi-Object Tracking with Transformers code — Compare
CroHD (5 rows) PP-Tracking PP-YOLOE: An evolved version of YOLO code Syntology official (archive's flag): 2 ran · 22 ran (of which 0 constructed an object rather than computing a result; 19 with no instrument failure: 2 honoured, 0 violated, 17 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified Compare
KITTI Test (Offline Methods) (2 rows) MCTrack MCTrack: A Unified 3D Multi-Object Tracking Framework for... code — Compare
RADIATE (2 rows) SIRA SIRA: Scalable Inter-frame Relation and Association for Radar Perception — — Compare
Waymo Open Dataset (2 rows) QDTrack Quasi-Dense Similarity Learning for Multiple Object Tracking code — Compare
GMOT-40 (1 row) MAC-SORT TP-GMOT: Tracking Generic Multiple Object by Textual Prompt with... code — Compare
UA-DETRAC (1 row) EB & TADN Transformer-based assignment decision network for multiple object tracking code — Compare
YouTube-Hands (1 row) HandLer Forward Propagation, Backward Regression, and Pose Association for... code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

18 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

2 subtasks in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 318 · with a code link: 149 · where Syntology ran a sample: 34 (34 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (34 of 318 tagged: 34 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 4: papers 1 to 100 of 318, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 26 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections