Research map / Benchmarks / ScanNet v2
ScanNet v2 leaderboard
102 papers at ICML, NeurIPS, ICLR, CVPR, AAAI, ICCV and ECCV, and the journals TPAMI, IJCV and JMLR report results on ScanNet v2. Best mIoU (val): 78.52 (AnIsoNet (Ours), ICML 2026).
Numbers are as each paper reports them, read by AI from its results tables and not checked by hand. Papers can differ in setting (training data, model size, extra data); the topic column shows what each paper is about. Open the paper before you compare or quote a number.
ScanNet v2 · mIoU (val)
26 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · mIoU
25 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · mAP@0.25
20 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · mAP@0.25 (val)
17 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · mAP@0.5
17 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · AP50
16 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · mAP (val)
15 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · mAP@0.5 (val)
15 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · AP50 (val)
13 papers, each with its best reported number for its own method; higher is better.
Sign in free to see all
ScanNet v2 · AP25 (val)
10 papers, each with its best reported number for its own method; higher is better.
ScanNet v2 · mAP
10 papers, each with its best reported number for its own method; higher is better.
ScanNet v2 · AP25
10 papers, each with its best reported number for its own method; higher is better.
Not affiliated with any conference, journal or the benchmark's authors. Corrections: contact@latenticlabs.com.
