sensors Mode-S transponder

68220D

ICAO 24-bit transponder address · allocated to Mongolia

Currently assigned to JU-1015 · BOEING 737-800

Hex
68220D
Octal
32021015
Decimal
6,824,461
Country
MN
Tail
JU-1015
Type
B738
No current signal · last broadcast 1h ago
Flights observed
172
Distinct callsigns
20
Country
MN
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S 68220D.

Country allocation

The ICAO 24-bit address 68220D 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 20 distinct

Callsign Airline Flights Last seen
MGL298 - 30 2026-07-13
MGL297 - 28 2026-07-12
MGL2971 - 23 2026-07-14
MGL502 - 14 2026-06-25
MGL501 - 13 2026-06-24
MGL2972 - 13 2026-07-10
MGL223 - 8 2026-07-12
MGL224 - 6 2026-07-12
MGL504 - 5 2026-07-11
MGL503 - 4 2026-07-11
MGL227 - 4 2026-07-04
MGL7308 - 3 2026-05-21
MGL7307 - 3 2026-05-21
MGL307 - 3 2026-06-28
MGL228 - 3 2026-07-04
MGL309 MIAT Mongolian Airlines 2 2026-07-02
MGL308 - 2 2026-06-28
MGL304 - 2 2026-07-09
MGL303 - 2 2026-07-09
MGL7310 - 1 2026-04-15

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-14 MGL2971 - Jul 14, 06:20 UTCJul 14, 09:15 UTC2h 55m
2026-07-13 MGL298 - Jul 13, 04:45 UTCJul 13, 05:01 UTC15m
2026-07-12 MGL297 - Jul 12, 23:45 UTCJul 13, 02:35 UTC2h 50m
2026-07-12 MGL224 - Jul 12, 13:40 UTCJul 12, 13:55 UTC15m
2026-07-12 MGL223 - Jul 12, 11:40 UTCJul 12, 12:01 UTC20m
2026-07-11 MGL504 - Jul 11, 05:15 UTCJul 11, 08:25 UTC3h 10m
2026-07-11 MGL503 - Jul 11, 00:30 UTCJul 11, 03:30 UTC3h 0m
2026-07-10 MGL2972 - Jul 10, 11:05 UTCJul 10, 11:20 UTC15m
2026-07-10 MGL2971 - Jul 10, 06:25 UTCJul 10, 09:25 UTC3h 0m
2026-07-09 MGL304 - Jul 9, 07:25 UTCJul 10, 06:40 UTC23h 15m
2026-07-09 MGL303 - Jul 9, 05:30 UTCJul 9, 05:50 UTC20m
2026-07-08 MGL504 - Jul 8, 07:20 UTCJul 9, 04:35 UTC21h 15m
2026-07-08 MGL504 - Jul 8, 05:35 UTCJul 9, 04:35 UTC23h 0m
2026-07-08 MGL503 - Jul 8, 01:40 UTCJul 8, 03:40 UTC2h 0m
2026-07-07 MGL2972 - Jul 7, 11:00 UTCJul 7, 11:15 UTC15m
2026-07-07 MGL2971 - Jul 7, 06:10 UTCJul 7, 09:25 UTC3h 15m
2026-07-06 MGL2971 HKG → HKG Jul 6, 11:45 UTCJul 7, 09:25 UTC21h 40m
2026-07-06 MGL2971 - Jul 6, 09:15 UTCJul 6, 10:00 UTC45m
2026-07-05 MGL510 - Jul 5, 12:35 UTCJul 6, 06:50 UTC18h 15m
2026-07-05 MGL509 - Jul 5, 08:45 UTCJul 5, 10:45 UTC2h 0m
2026-07-04 MGL228 - Jul 4, 20:05 UTCJul 4, 20:20 UTC15m
2026-07-04 MGL227 - Jul 4, 17:15 UTCJul 4, 17:35 UTC20m
2026-07-04 MGL504 - Jul 4, 05:25 UTCJul 4, 08:50 UTC3h 25m
2026-07-04 MGL503 - Jul 4, 01:40 UTCJul 4, 03:40 UTC2h 0m
2026-07-03 MGL2972 - Jul 3, 12:15 UTCJul 3, 12:30 UTC15m
2026-07-02 MGL2971 ICN → HKG Jul 2, 16:45 UTCJul 3, 09:15 UTC16h 30m
2026-07-02 MGL309 UBN → ICN Jul 2, 14:40 UTCJul 2, 15:00 UTC20m
2026-07-02 MGL304 - Jul 2, 07:30 UTCJul 2, 09:05 UTC1h 35m
2026-07-02 MGL303 - Jul 2, 05:35 UTCJul 2, 05:55 UTC20m
2026-07-01 MGL504 - Jul 1, 05:20 UTCJul 1, 08:45 UTC3h 25m
2026-07-01 MGL503 - Jul 1, 01:25 UTCJul 1, 03:35 UTC2h 10m
2026-06-30 MGL224 - Jun 30, 13:35 UTCJun 30, 13:50 UTC15m
2026-06-30 MGL223 - Jun 30, 11:30 UTCJun 30, 11:50 UTC20m
2026-06-29 MGL228 PEK → UBN Jun 29, 20:09 UTCJun 29, 20:24 UTC15m
2026-06-29 MGL227 UBN → PEK Jun 29, 17:19 UTCJun 29, 17:45 UTC25m
2026-06-29 MGL224 - Jun 29, 01:50 UTCJun 29, 02:00 UTC10m
2026-06-28 MGL223 - Jun 28, 23:29 UTCJun 28, 23:50 UTC20m
2026-06-28 MGL308 - Jun 28, 15:09 UTCJun 28, 16:45 UTC1h 35m
2026-06-28 MGL307 - Jun 28, 13:19 UTCJun 28, 13:45 UTC25m
2026-06-28 MGL298 - Jun 28, 05:24 UTCJun 28, 08:19 UTC2h 55m
2026-06-28 MGL297 - Jun 28, 02:10 UTCJun 28, 02:39 UTC30m
2026-06-27 MGL2972 - Jun 27, 11:09 UTCJun 27, 23:50 UTC12h 40m
2026-06-27 MGL2971 - Jun 27, 06:40 UTCJun 27, 09:24 UTC2h 45m
2026-06-25 MGL502 - Jun 25, 06:44 UTCJun 25, 10:25 UTC3h 40m
2026-06-24 MGL501 - Jun 24, 19:34 UTCJun 25, 04:10 UTC8h 35m
2026-06-24 MGL227 UBN → PEK Jun 24, 17:20 UTCJun 24, 17:34 UTC15m
2026-06-24 MGL298 - Jun 24, 10:39 UTCJun 24, 10:55 UTC15m
2026-06-24 MGL297 - Jun 24, 06:15 UTCJun 24, 09:15 UTC3h 0m
2026-06-23 MGL298 - Jun 23, 04:39 UTCJun 23, 04:55 UTC15m
2026-06-22 MGL297 - Jun 22, 23:50 UTCJun 23, 02:49 UTC3h 0m

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-1015 page for operator, model, and routing details .

Mode-S 68220D frequently asked

What is Mode-S code 68220D?
68220D is an ICAO 24-bit transponder address. Allocated to Mongolia. Assigned to JU-1015.
Where is Mode-S 68220D registered?
Mode-S code 68220D is allocated to Mongolia (MN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 68220D broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 68220D, octal 32021015, decimal 6,824,461.
What flights does 68220D operate?
Mode-S 68220D has broadcast 20 distinct callsigns, including MGL298, MGL297, MGL2971, MGL502, MGL501.