sensors Mode-S transponder
682231
ICAO 24-bit transponder address · allocated to Mongolia
Currently assigned to JU-1088 · BOEING 737-800
- Hex
- 682231
- Octal
- 32021061
- Decimal
- 6,824,497
- Country
- MN
- Tail
- JU-1088
- Type
- B738
- Flights observed
- 51
- Distinct callsigns
- 12
- Country
- MN
- Last broadcast
- 19h ago
Last known position
Country allocation
The ICAO 24-bit address 682231 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 12 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MGL302 | MIAT Mongolian Airlines | 15 | 2026-05-26 |
| MGL301 | MIAT Mongolian Airlines | 9 | 2026-05-26 |
| MGL307 | MIAT Mongolian Airlines | 7 | 2026-05-29 |
| MGL308 | MIAT Mongolian Airlines | 5 | 2026-05-29 |
| MGL297 | MIAT Mongolian Airlines | 3 | 2026-05-15 |
| MGL223 | MIAT Mongolian Airlines | 3 | 2026-05-17 |
| MGL7308 | - | 2 | 2026-05-28 |
| MGL298 | MIAT Mongolian Airlines | 2 | 2026-05-15 |
| MGL224 | MIAT Mongolian Airlines | 2 | 2026-05-17 |
| MGL7307 | - | 1 | 2026-05-28 |
| MGL708 | - | 1 | 2026-05-22 |
| MGL2972 | MIAT Mongolian Airlines | 1 | 2026-05-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | MGL308 | ICN → UBN | May 29, 15:35 UTC | May 29, 17:20 UTC | 1h 45m |
| 2026-05-29 | MGL307 | UBN → ICN | May 29, 12:45 UTC | May 29, 13:10 UTC | 25m |
| 2026-05-28 | MGL7308 | - | May 28, 15:05 UTC | May 28, 16:50 UTC | 1h 45m |
| 2026-05-28 | MGL7307 | - | May 28, 12:30 UTC | May 28, 12:50 UTC | 20m |
| 2026-05-26 | MGL302 | ICN → UBN | May 26, 05:45 UTC | May 26, 07:19 UTC | 1h 35m |
| 2026-05-26 | MGL301 | UBN → ICN | May 26, 03:15 UTC | May 26, 03:40 UTC | 25m |
| 2026-05-24 | MGL308 | ICN → UBN | May 24, 15:20 UTC | May 24, 15:40 UTC | 20m |
| 2026-05-24 | MGL307 | UBN → ICN | May 24, 12:40 UTC | May 24, 13:05 UTC | 25m |
| 2026-05-22 | MGL708 | - | May 22, 15:15 UTC | May 22, 15:40 UTC | 25m |
| 2026-05-22 | MGL307 | UBN → ICN | May 22, 12:55 UTC | May 22, 13:15 UTC | 20m |
| 2026-05-19 | MGL308 | ICN → UBN | May 19, 15:20 UTC | May 19, 16:55 UTC | 1h 35m |
| 2026-05-19 | MGL307 | UBN → ICN | May 19, 12:45 UTC | May 19, 13:05 UTC | 20m |
| 2026-05-17 | MGL224 | PEK → UBN | May 17, 13:45 UTC | May 17, 14:01 UTC | 15m |
| 2026-05-17 | MGL223 | UBN → PEK | May 17, 11:35 UTC | May 17, 11:55 UTC | 20m |
| 2026-05-16 | MGL2972 | HKG → UBN | May 16, 11:01 UTC | May 16, 11:16 UTC | 15m |
| 2026-05-15 | MGL298 | HKG → ULN | May 15, 17:25 UTC | May 16, 09:31 UTC | 16h 6m |
| 2026-05-15 | MGL297 | ULN → HKG | May 15, 02:40 UTC | May 15, 02:45 UTC | 5m |
| 2026-05-15 | MGL297 | ULN → HKG | May 15, 02:00 UTC | May 15, 02:10 UTC | 10m |
| 2026-05-12 | MGL301 | UBN → ICN | May 12, 03:30 UTC | May 12, 03:40 UTC | 10m |
| 2026-05-09 | MGL302 | ICN → UBN | May 9, 07:10 UTC | May 9, 07:30 UTC | 20m |
| 2026-05-09 | MGL302 | ICN → UBN | May 9, 05:50 UTC | May 9, 06:00 UTC | 10m |
| 2026-05-07 | MGL302 | ICN → UBN | May 7, 05:45 UTC | May 7, 07:35 UTC | 1h 50m |
| 2026-05-06 | MGL302 | ICN → UBN | May 6, 05:40 UTC | May 6, 07:15 UTC | 1h 35m |
| 2026-05-04 | MGL302 | ICN → UBN | May 4, 06:50 UTC | May 4, 07:10 UTC | 20m |
| 2026-05-03 | MGL223 | UBN → PEK | May 3, 11:15 UTC | May 3, 11:40 UTC | 25m |
| 2026-05-02 | MGL302 | ICN → UBN | May 2, 05:35 UTC | May 2, 07:10 UTC | 1h 35m |
| 2026-05-02 | MGL301 | UBN → ICN | May 2, 03:10 UTC | May 2, 03:25 UTC | 15m |
| 2026-04-30 | MGL302 | ICN → UBN | Apr 30, 05:45 UTC | Apr 30, 07:15 UTC | 1h 30m |
| 2026-04-30 | MGL301 | UBN → ICN | Apr 30, 03:30 UTC | Apr 30, 03:40 UTC | 10m |
| 2026-04-28 | MGL302 | ICN → UBN | Apr 28, 05:45 UTC | Apr 28, 07:35 UTC | 1h 50m |
| 2026-04-28 | MGL301 | UBN → ICN | Apr 28, 03:15 UTC | Apr 28, 03:30 UTC | 15m |
| 2026-04-27 | MGL224 | PEK → UBN | Apr 27, 01:40 UTC | Apr 27, 01:50 UTC | 10m |
| 2026-04-24 | MGL223 | UBN → PEK | Apr 24, 11:25 UTC | Apr 24, 11:45 UTC | 20m |
| 2026-04-24 | MGL302 | ICN → UBN | Apr 24, 05:40 UTC | Apr 24, 07:10 UTC | 1h 30m |
| 2026-04-24 | MGL301 | UBN → ICN | Apr 24, 03:15 UTC | Apr 24, 03:40 UTC | 25m |
| 2026-04-23 | MGL302 | ICN → UBN | Apr 23, 07:05 UTC | Apr 23, 07:30 UTC | 25m |
| 2026-04-23 | MGL301 | UBN → ICN | Apr 23, 03:30 UTC | Apr 23, 03:40 UTC | 10m |
| 2026-04-22 | MGL302 | ICN → UBN | Apr 22, 05:50 UTC | Apr 22, 06:01 UTC | 10m |
| 2026-04-22 | MGL301 | UBN → ICN | Apr 22, 03:10 UTC | Apr 22, 03:25 UTC | 15m |
| 2026-04-21 | MGL308 | ICN → UBN | Apr 21, 15:25 UTC | Apr 21, 17:10 UTC | 1h 45m |
| 2026-04-21 | MGL307 | UBN → ICN | Apr 21, 12:40 UTC | Apr 21, 13:01 UTC | 20m |
| 2026-04-21 | MGL302 | ICN → UBN | Apr 21, 05:50 UTC | Apr 21, 07:35 UTC | 1h 45m |
| 2026-04-19 | MGL308 | ICN → UBN | Apr 19, 15:20 UTC | Apr 19, 17:00 UTC | 1h 40m |
| 2026-04-19 | MGL307 | UBN → ICN | Apr 19, 13:00 UTC | Apr 19, 13:10 UTC | 10m |
| 2026-04-17 | MGL307 | UBN → ICN | Apr 17, 12:45 UTC | Apr 17, 13:05 UTC | 20m |
| 2026-04-17 | MGL302 | ICN → UBN | Apr 17, 05:50 UTC | Apr 17, 06:00 UTC | 10m |
| 2026-04-17 | MGL301 | UBN → ICN | Apr 17, 03:20 UTC | Apr 17, 03:35 UTC | 15m |
| 2026-04-16 | MGL298 | HKG → ULN | Apr 16, 04:34 UTC | Apr 16, 04:49 UTC | 15m |
| 2026-04-16 | MGL297 | ULN → HKG | Apr 16, 02:19 UTC | Apr 16, 02:50 UTC | 30m |
| 2026-04-14 | MGL302 | ICN → UBN | Apr 14, 05:45 UTC | Apr 14, 05:55 UTC | 10m |
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-1088 page for operator, model, and routing details .