sensors Mode-S transponder
682308
ICAO 24-bit transponder address · allocated to Mongolia
Currently assigned to JU-1410 · AIRBUS A-320
- Hex
- 682308
- Octal
- 32021410
- Decimal
- 6,824,712
- Country
- MN
- Tail
- JU-1410
- Type
- A320
- Flights observed
- 34
- Distinct callsigns
- 16
- Country
- MN
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 682308 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| BAV281 | Bay Aviation Ltd | 4 | 2026-06-01 |
| BAV242 | Bay Aviation Ltd | 4 | 2026-06-01 |
| BAV283 | - | 3 | 2026-06-02 |
| BAV1215 | Bay Aviation Ltd | 3 | 2026-06-01 |
| BAV251 | Bay Aviation Ltd | 2 | 2026-06-02 |
| BAV240 | - | 2 | 2026-04-21 |
| BAV224 | Bay Aviation Ltd | 2 | 2026-04-23 |
| BAV211 | Bay Aviation Ltd | 2 | 2026-06-03 |
| BAV1125 | Bay Aviation Ltd | 2 | 2026-04-24 |
| BAV1124 | Bay Aviation Ltd | 2 | 2026-04-25 |
| BAV268 | - | 1 | 2026-05-28 |
| BAV261 | - | 1 | 2026-04-18 |
| BAV255 | Bay Aviation Ltd | 1 | 2026-05-30 |
| BAV204 | Bay Aviation Ltd | 1 | 2026-04-21 |
| BAV150 | Bay Aviation Ltd | 1 | 2026-04-16 |
| BAV1214 | Bay Aviation Ltd | 1 | 2026-05-27 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | BAV211 | HAN → SGN | Jun 3, 03:50 UTC | Jun 3, 04:10 UTC | 20m |
| 2026-06-02 | BAV283 | - | Jun 2, 15:20 UTC | Jun 3, 01:55 UTC | 10h 35m |
| 2026-06-02 | BAV251 | HAN → SGN | Jun 2, 09:45 UTC | Jun 2, 14:15 UTC | 4h 30m |
| 2026-06-02 | BAV211 | HAN → SGN | Jun 2, 03:25 UTC | Jun 2, 07:55 UTC | 4h 30m |
| 2026-06-01 | BAV281 | HAN → SGN | Jun 1, 14:40 UTC | Jun 2, 02:15 UTC | 11h 35m |
| 2026-06-01 | BAV1215 | HAN → UIH | Jun 1, 09:50 UTC | Jun 1, 13:10 UTC | 3h 20m |
| 2026-06-01 | BAV242 | SGN → HAN | Jun 1, 03:30 UTC | Jun 1, 08:10 UTC | 4h 40m |
| 2026-05-31 | BAV281 | HAN → SGN | May 31, 14:35 UTC | Jun 1, 02:00 UTC | 11h 25m |
| 2026-05-31 | BAV1215 | HAN → UIH | May 31, 09:45 UTC | May 31, 13:15 UTC | 3h 30m |
| 2026-05-30 | BAV283 | - | May 30, 16:00 UTC | May 30, 16:25 UTC | 25m |
| 2026-05-30 | BAV255 | HAN → SGN | May 30, 09:35 UTC | May 30, 14:50 UTC | 5h 15m |
| 2026-05-30 | BAV242 | SGN → HAN | May 30, 03:30 UTC | May 30, 08:10 UTC | 4h 40m |
| 2026-05-29 | BAV281 | HAN → SGN | May 29, 14:45 UTC | May 30, 02:00 UTC | 11h 15m |
| 2026-05-29 | BAV1215 | HAN → UIH | May 29, 10:00 UTC | May 29, 13:25 UTC | 3h 25m |
| 2026-05-29 | BAV242 | SGN → HAN | May 29, 03:35 UTC | May 29, 08:30 UTC | 4h 55m |
| 2026-05-28 | BAV283 | - | May 28, 15:40 UTC | May 29, 01:35 UTC | 9h 55m |
| 2026-05-28 | BAV268 | - | May 28, 09:45 UTC | May 28, 14:35 UTC | 4h 50m |
| 2026-05-28 | BAV242 | SGN → HAN | May 28, 03:25 UTC | May 28, 08:25 UTC | 5h 0m |
| 2026-05-27 | BAV281 | - | May 27, 16:45 UTC | May 28, 01:55 UTC | 9h 10m |
| 2026-05-27 | BAV1214 | UIH → HAN | May 27, 11:35 UTC | May 27, 15:35 UTC | 4h 0m |
| 2026-04-26 | BAV251 | HAN → SGN | Apr 26, 08:40 UTC | Apr 26, 08:50 UTC | 10m |
| 2026-04-25 | BAV1124 | SGN → UIH | Apr 25, 13:35 UTC | Apr 25, 13:45 UTC | 10m |
| 2026-04-24 | BAV1125 | UIH → SGN | Apr 24, 13:20 UTC | Apr 24, 13:30 UTC | 10m |
| 2026-04-24 | BAV1124 | SGN → UIH | Apr 24, 11:00 UTC | Apr 24, 11:10 UTC | 10m |
| 2026-04-24 | - | - | Apr 24, 09:05 UTC | Apr 24, 09:15 UTC | 10m |
| 2026-04-23 | BAV224 | SGN → HAN | Apr 23, 01:45 UTC | Apr 23, 01:55 UTC | 10m |
| 2026-04-22 | BAV1125 | UIH → SGN | Apr 22, 12:55 UTC | Apr 22, 13:10 UTC | 15m |
| 2026-04-21 | BAV240 | - | Apr 21, 06:25 UTC | Apr 21, 06:35 UTC | 10m |
| 2026-04-21 | BAV204 | SGN → HAN | Apr 21, 00:20 UTC | Apr 21, 00:40 UTC | 20m |
| 2026-04-19 | BAV240 | - | Apr 19, 03:55 UTC | Apr 19, 04:05 UTC | 10m |
| 2026-04-18 | BAV261 | - | Apr 18, 11:25 UTC | Apr 18, 11:35 UTC | 10m |
| 2026-04-17 | BAV224 | SGN → HAN | Apr 17, 11:30 UTC | Apr 17, 11:40 UTC | 10m |
| 2026-04-17 | - | - | Apr 17, 02:15 UTC | Apr 17, 02:25 UTC | 10m |
| 2026-04-16 | BAV150 | SGN → DAD | Apr 16, 23:25 UTC | Apr 16, 23:35 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-1410 page for operator, model, and routing details .