Competitive Programming Record · Ahsanul Haque 5,943 Accepted problems across 14 judge accounts, of which at least 5,332 are distinct

Recorded judge by judge, and every figure on this page links to the profile it came from.

  • 34th ICPC Asia Dhaka Regional · 2025, of 300+ teams
  • 2nd NWU IUPC 2025 · national 1st runner-up
Codeforces profile LeetCode profile GitHub
Last verified 6 live APIs 4 profile syncs 4 tracked snapshots

The shape of the record

Each band is one judge, ranked largest first — its width is that judge's share of the total, read against the axis below.

Hover or click any band to inspect volume share, rank, and jump to verified credentials
Method Each judge counts its own account, so the total is an upper bound: a problem solved on both Virtual Judge and its original judge is counted twice. Dropping Virtual Judge — which mirrors the others — leaves the 5,332 that are certainly distinct.

    Competitive results

    Ordered by weight — the ICPC regional first, then the national inter-university circuit, then campus championships.

    • 34th regional

      ICPC Asia Dhaka Regional — 34th

      2025, team JUST_ORIONS · 63rd in 2024, team JUST_TRIPLE_HELIX · 2× regionalist among 300+ university teams

    • 2nd place

      NWU IUPC 2025 — 1st Runner-Up

      National inter-university programming contest · team JUST_ORIONS

    • 1st place

      JUST IDPC — Champion

      Inter-departmental programming contest

    • 14+ on-site IUPCs

      National IUPC circuit

      2026: 11th NDUB, 13th SUST, 15th DUET, 16th BUET · 2024: 7th KU KRIUPC · sustained top-20 finishes at national level

    • 1st champion

      JUST ACM Laboratory Farewell Contest

      Senior Category Champion (2026) · 1st Runner-Up (2025) · Junior Champion (2024)

    Judges & profiles

    10 of 14 judges refresh automatically — daily at 00:00 UTC and on every deploy. The remaining 4 are verified snapshots.

    Virtual Judge mirrors problems from the other judges, so its solves can double-count.

      Difficulty mix

      LeetCode is the only judge in this record that publishes a per-difficulty breakdown — so these figures describe its solves, not all of them.

      LeetCode

        Verify figures

        Every figure can be checked against the live profile it came from, and every card states which way it was read.

        Where a number comes from

        • Live API

          Read from the judge's own public API at sync time — the freshest source, no manual step.

        • Profile sync

          Read from the judge's public profile page every day, because that judge publishes no API for this figure.

        • Snapshot

          Hand-checked against the profile and kept in the repository between syncs — the number is dated, not stale.

        How do I spot-check a number?

        Open any judge card and follow its outbound profile link, then compare the solve count on the live profile. Every card states its source — Live API, Profile sync or Snapshot — so you know how the figure was read.

        Why is the total an upper bound?

        Each judge counts its own account, so a problem solved on both Virtual Judge and its original judge is counted twice. Flip “Exclude Virtual Judge overlaps” for the deduplicated figure; the Method note defines it.

        What is a snapshot, and how fresh is the data?

        A snapshot is a hand-checked figure stored in the repository between syncs. GitHub Actions refreshes daily at 00:00 UTC and on every deploy, and the header timestamp records the last successful verification.

        Statistics updated