Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

682276

ICAO 24-bit transponder address · allocated to Mongolia

Currently assigned to JU-1199 · AIRBUS A-319

Hex
682276
Octal
32021166
Decimal
6,824,566
Country
MN
Tail
JU-1199
Type
A319
No current signal · last broadcast 21h ago
Flights observed
64
Distinct callsigns
6
Country
MN
Last broadcast
21h ago

Last known position

Most recent position reported by Mode-S 682276.

Country allocation

The ICAO 24-bit address 682276 falls within the block assigned to Mongolia (MN) by ICAO Annex 10, Volume III. Every aircraft registered in Mongolia receives a permanent address from this block at the time of registration; the address stays with the airframe even if the aircraft is re-registered to a different operator within the country.

Callsign history 6 distinct

Callsign Airline Flights Last seen
MNG601 - 21 2026-07-17
MNG602 - 19 2026-07-17
MNG901 Aero Mongolia 12 2026-06-11
MNG902 Aero Mongolia 7 2026-06-12
MNG6011 Aero Mongolia 3 2026-05-21
MNG6012 Aero Mongolia 2 2026-05-21

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-17 MNG602 - Jul 17, 10:20 UTCJul 17, 10:40 UTC20m
2026-07-17 MNG602 - Jul 17, 09:10 UTCJul 17, 09:30 UTC20m
2026-07-17 MNG601 - Jul 17, 07:14 UTCJul 17, 07:30 UTC15m
2026-07-12 MNG602 - Jul 12, 08:45 UTCJul 12, 10:10 UTC1h 25m
2026-07-12 MNG601 - Jul 12, 07:01 UTCJul 12, 07:25 UTC25m
2026-07-10 MNG602 - Jul 10, 08:40 UTCJul 10, 10:10 UTC1h 30m
2026-07-10 MNG601 - Jul 10, 07:05 UTCJul 10, 07:25 UTC20m
2026-07-10 MNG601 - Jul 10, 06:00 UTCJul 10, 06:15 UTC15m
2026-07-08 MNG602 - Jul 8, 08:00 UTCJul 8, 09:35 UTC1h 35m
2026-07-08 MNG601 - Jul 8, 06:15 UTCJul 8, 06:35 UTC20m
2026-06-24 MNG602 ICN → UBN Jun 24, 07:50 UTCJun 24, 09:29 UTC1h 40m
2026-06-24 MNG601 UBN → ICN Jun 24, 05:54 UTCJun 24, 06:20 UTC25m
2026-06-24 MNG601 UBN → ICN Jun 24, 04:55 UTCJun 24, 05:05 UTC10m
2026-06-21 MNG602 ICN → UBN Jun 21, 08:49 UTCJun 21, 10:34 UTC1h 45m
2026-06-21 MNG601 UBN → ICN Jun 21, 07:00 UTCJun 21, 07:25 UTC25m
2026-06-17 MNG602 ICN → UBN Jun 17, 07:40 UTCJun 17, 08:05 UTC25m
2026-06-17 MNG601 UBN → ICN Jun 17, 06:00 UTCJun 17, 06:20 UTC20m
2026-06-12 MNG902 NRT → UBN Jun 12, 08:20 UTCJun 12, 12:05 UTC3h 45m
2026-06-11 MNG901 UBN → NRT Jun 11, 10:00 UTCJun 12, 05:30 UTC19h 31m
2026-06-11 MNG901 UBN → NRT Jun 11, 08:45 UTCJun 12, 05:30 UTC20h 46m
2026-06-11 MNG601 UBN → ICN Jun 11, 07:10 UTCJun 11, 07:30 UTC20m
2026-06-10 MNG602 ICN → UBN Jun 10, 08:10 UTCJun 10, 09:50 UTC1h 40m
2026-06-10 MNG601 UBN → ICN Jun 10, 06:25 UTCJun 10, 07:00 UTC35m
2026-06-10 MNG601 UBN → ICN Jun 10, 05:20 UTCJun 10, 05:35 UTC15m
2026-06-07 MNG602 ICN → UBN Jun 7, 08:45 UTCJun 7, 10:30 UTC1h 45m
2026-06-07 MNG601 UBN → ICN Jun 7, 07:05 UTCJun 7, 07:25 UTC20m
2026-06-05 MNG602 ICN → UBN Jun 5, 08:40 UTCJun 5, 10:25 UTC1h 45m
2026-06-05 MNG601 UBN → ICN Jun 5, 06:50 UTCJun 5, 07:20 UTC30m
2026-05-27 MNG602 ICN → UBN May 27, 09:10 UTCMay 27, 09:30 UTC20m
2026-05-27 MNG602 ICN → UBN May 27, 07:50 UTCMay 27, 08:15 UTC25m
2026-05-27 MNG601 UBN → ICN May 27, 06:04 UTCMay 27, 06:29 UTC25m
2026-05-21 MNG6012 ICN → UBN May 21, 08:50 UTCMay 21, 10:25 UTC1h 35m
2026-05-21 MNG6011 UBN → ICN May 21, 07:05 UTCMay 21, 07:25 UTC20m
2026-05-20 MNG602 ICN → UBN May 20, 09:25 UTCMay 20, 09:45 UTC20m
2026-05-20 MNG602 ICN → UBN May 20, 08:05 UTCMay 20, 08:25 UTC20m
2026-05-20 MNG601 UBN → ICN May 20, 06:25 UTCMay 20, 06:45 UTC20m
2026-05-19 MNG902 NRT → UBN May 19, 06:10 UTCMay 19, 09:25 UTC3h 15m
2026-05-18 MNG901 UBN → NRT May 18, 10:00 UTCMay 19, 04:40 UTC18h 39m
2026-05-18 MNG901 UBN → NRT May 18, 08:45 UTCMay 19, 04:40 UTC19h 54m
2026-05-18 MNG601 UBN → ICN May 18, 07:00 UTCMay 18, 07:25 UTC25m
2026-05-16 MNG602 ICN → UBN May 16, 07:51 UTCMay 16, 08:11 UTC20m
2026-05-16 MNG601 UBN → ICN May 16, 06:16 UTCMay 16, 06:31 UTC15m
2026-05-15 MNG902 NRT → UBN May 15, 05:55 UTCMay 15, 07:45 UTC1h 50m
2026-05-15 MNG901 UBN → NRT May 15, 02:20 UTCMay 15, 04:40 UTC2h 20m
2026-05-14 MNG901 UBN → NRT May 14, 08:55 UTCMay 15, 04:40 UTC19h 45m
2026-05-14 MNG6011 UBN → ICN May 14, 07:20 UTCMay 14, 07:35 UTC15m
2026-05-12 MNG902 NRT → UBN May 12, 06:00 UTCMay 12, 07:55 UTC1h 55m
2026-05-12 MNG901 UBN → NRT May 12, 02:45 UTCMay 12, 04:30 UTC1h 45m
2026-05-11 MNG901 UBN → NRT May 11, 08:40 UTCMay 12, 04:30 UTC19h 51m
2026-05-10 MNG902 NRT → UBN May 10, 06:00 UTCMay 10, 08:05 UTC2h 5m

About Mode-S

A Mode-S transponder code (also called an "ICAO 24-bit address" or "hex code") is a 6-character hexadecimal identifier permanently assigned to an aircraft when it's first registered. Unlike callsigns (which change with each flight) or registrations (which can change if an aircraft is sold internationally), the Mode-S address stays with the airframe for the life of the aircraft in that country.

Every ADS-B transmission from an aircraft includes its Mode-S address, making it the most reliable way to identify a specific airframe. Flight-tracking services like Apparatus use the Mode-S address as the primary key for tying position broadcasts, callsigns, and ownership records together.

Prefer a tail-number view? See the JU-1199 page for operator, model, and routing details .

Mode-S 682276 frequently asked

What is Mode-S code 682276?
682276 is an ICAO 24-bit transponder address. Allocated to Mongolia. Assigned to JU-1199.
Where is Mode-S 682276 registered?
Mode-S code 682276 is allocated to Mongolia (MN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 682276 broadcasting right now?
No active broadcast right now. Last signal was 21h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 682276, octal 32021166, decimal 6,824,566.
What flights does 682276 operate?
Mode-S 682276 has broadcast 6 distinct callsigns, including MNG601, MNG602, MNG901, MNG902, MNG6011.