sensors Mode-S transponder
E80621
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-DID
- Hex
- E80621
- Octal
- 72003041
- Decimal
- 15,205,921
- Country
- CL
- Tail
- CC-DID
- Type
- A20N
- Flights observed
- 229
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 12d ago
Last known position
Country allocation
The ICAO 24-bit address E80621 falls within the block assigned to Chile (CL) by ICAO Annex 10, Volume III. Every aircraft registered in Chile 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 |
|---|---|---|---|
| JAT731 | - | 11 | 2026-07-12 |
| JAT852 | Jat Airways | 9 | 2026-07-08 |
| JAT550 | Jat Airways | 9 | 2026-07-22 |
| JAT532 | - | 8 | 2026-07-16 |
| JAT546 | - | 7 | 2026-07-14 |
| JAT311 | - | 7 | 2026-07-17 |
| JAT762 | Jat Airways | 6 | 2026-05-30 |
| JAT730 | - | 6 | 2026-07-13 |
| JAT664 | Jat Airways | 6 | 2026-07-25 |
| JAT500 | Jat Airways | 6 | 2026-07-24 |
| JAT853 | - | 5 | 2026-07-08 |
| JAT776 | - | 5 | 2026-07-13 |
| JAT634 | - | 5 | 2026-07-12 |
| JAT633 | - | 5 | 2026-07-12 |
| JAT501 | Jat Airways | 5 | 2026-07-24 |
| JAT763 | Jat Airways | 4 | 2026-05-30 |
| JAT733 | - | 4 | 2026-07-10 |
| JAT732 | - | 4 | 2026-07-10 |
| JAT548 | - | 4 | 2026-07-15 |
| JAT544 | - | 4 | 2026-07-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | JAT665 | LSC → CCP | Jul 25, 23:00 UTC | Jul 26, 21:10 UTC | 22h 11m |
| 2026-07-25 | JAT664 | CCP → LSC | Jul 25, 15:15 UTC | Jul 26, 13:40 UTC | 22h 26m |
| 2026-07-25 | JAT555 | ANF → CCP | Jul 25, 01:30 UTC | Jul 25, 23:10 UTC | 21h 40m |
| 2026-07-24 | JAT555 | ANF → CCP | Jul 24, 21:15 UTC | Jul 25, 15:30 UTC | 18h 15m |
| 2026-07-24 | JAT501 | SCL → CCP | Jul 24, 19:10 UTC | Jul 25, 15:30 UTC | 20h 20m |
| 2026-07-24 | JAT500 | CCP → SCL | Jul 24, 17:10 UTC | Jul 24, 17:25 UTC | 15m |
| 2026-07-23 | JAT503 | SCL → CCP | Jul 23, 18:00 UTC | Jul 24, 01:20 UTC | 7h 20m |
| 2026-07-23 | JAT622 | CCP → SCL | Jul 23, 12:10 UTC | Jul 23, 12:20 UTC | 10m |
| 2026-07-23 | JAT622 | CCP → SCL | Jul 23, 10:50 UTC | Jul 23, 11:05 UTC | 15m |
| 2026-07-22 | JAT550 | CCP → ANF | Jul 22, 11:50 UTC | Jul 23, 02:55 UTC | 15h 5m |
| 2026-07-22 | JAT550 | CCP → ANF | Jul 22, 03:40 UTC | Jul 22, 18:25 UTC | 14h 45m |
| 2026-07-21 | JAT550 | CCP → ANF | Jul 21, 23:10 UTC | Jul 22, 18:25 UTC | 19h 15m |
| 2026-07-21 | JAT550 | CCP → ANF | Jul 21, 21:00 UTC | Jul 22, 18:25 UTC | 21h 25m |
| 2026-07-21 | JAT550 | CCP → ANF | Jul 21, 15:50 UTC | Jul 22, 12:05 UTC | 20h 15m |
| 2026-07-20 | JAT631 | ZCO → BBA | Jul 20, 15:15 UTC | Jul 20, 15:30 UTC | 15m |
| 2026-07-19 | JAT544 | - | Jul 19, 21:35 UTC | Jul 20, 09:25 UTC | 11h 50m |
| 2026-07-19 | JAT544 | - | Jul 19, 13:20 UTC | Jul 20, 09:25 UTC | 20h 5m |
| 2026-07-19 | JAT501 | - | Jul 19, 02:20 UTC | Jul 19, 23:50 UTC | 21h 30m |
| 2026-07-19 | JAT501 | - | Jul 19, 02:10 UTC | Jul 19, 23:50 UTC | 21h 40m |
| 2026-07-19 | JAT196 | - | Jul 19, 00:00 UTC | Jul 19, 00:15 UTC | 15m |
| 2026-07-18 | JAT197 | - | Jul 18, 20:40 UTC | Jul 18, 20:55 UTC | 15m |
| 2026-07-18 | JAT500 | CCP → SCL | Jul 18, 19:10 UTC | Jul 18, 19:25 UTC | 15m |
| 2026-07-17 | JAT664 | CCP → LSC | Jul 17, 13:35 UTC | Jul 18, 04:00 UTC | 14h 26m |
| 2026-07-17 | JAT311 | - | Jul 17, 06:45 UTC | Jul 18, 04:00 UTC | 21h 16m |
| 2026-07-16 | JAT310 | - | Jul 16, 20:35 UTC | Jul 17, 13:45 UTC | 17h 10m |
| 2026-07-16 | JAT310 | - | Jul 16, 16:44 UTC | Jul 17, 13:45 UTC | 21h 0m |
| 2026-07-16 | JAT532 | - | Jul 16, 11:45 UTC | Jul 17, 06:54 UTC | 19h 10m |
| 2026-07-16 | JAT532 | - | Jul 16, 01:50 UTC | Jul 16, 20:49 UTC | 19h 0m |
| 2026-07-15 | JAT548 | - | Jul 15, 21:25 UTC | Jul 16, 16:55 UTC | 19h 30m |
| 2026-07-15 | JAT533 | - | Jul 15, 19:05 UTC | Jul 16, 16:55 UTC | 21h 50m |
| 2026-07-15 | JAT532 | - | Jul 15, 14:20 UTC | Jul 16, 12:00 UTC | 21h 40m |
| 2026-07-15 | JAT532 | - | Jul 15, 14:10 UTC | Jul 16, 12:00 UTC | 21h 50m |
| 2026-07-15 | JAT532 | - | Jul 15, 02:30 UTC | Jul 16, 02:00 UTC | 23h 30m |
| 2026-07-14 | JAT546 | - | Jul 14, 22:00 UTC | Jul 15, 19:15 UTC | 21h 14m |
| 2026-07-14 | JAT503 | - | Jul 14, 19:35 UTC | Jul 15, 14:25 UTC | 18h 49m |
| 2026-07-14 | JAT030 | - | Jul 14, 13:55 UTC | Jul 14, 14:05 UTC | 10m |
| 2026-07-13 | JAT777 | - | Jul 13, 14:05 UTC | Jul 13, 17:10 UTC | 3h 5m |
| 2026-07-13 | JAT776 | - | Jul 13, 10:00 UTC | Jul 13, 12:25 UTC | 2h 25m |
| 2026-07-13 | JAT776 | - | Jul 13, 09:15 UTC | Jul 13, 09:25 UTC | 10m |
| 2026-07-13 | JAT730 | - | Jul 13, 01:25 UTC | Jul 13, 02:01 UTC | 35m |
| 2026-07-12 | JAT731 | - | Jul 12, 23:25 UTC | Jul 12, 23:55 UTC | 30m |
| 2026-07-12 | JAT731 | - | Jul 12, 22:25 UTC | Jul 12, 22:35 UTC | 10m |
| 2026-07-12 | JAT634 | - | Jul 12, 20:05 UTC | Jul 12, 20:15 UTC | 10m |
| 2026-07-12 | JAT633 | - | Jul 12, 17:35 UTC | Jul 12, 17:45 UTC | 10m |
| 2026-07-10 | JAT732 | - | Jul 10, 19:45 UTC | Jul 10, 20:20 UTC | 35m |
| 2026-07-10 | JAT733 | - | Jul 10, 17:35 UTC | Jul 10, 18:40 UTC | 1h 5m |
| 2026-07-10 | JAT634 | - | Jul 10, 14:40 UTC | Jul 10, 14:55 UTC | 15m |
| 2026-07-10 | JAT633 | - | Jul 10, 12:05 UTC | Jul 10, 12:20 UTC | 15m |
| 2026-07-09 | JAT044 | - | Jul 9, 20:10 UTC | Jul 9, 20:20 UTC | 10m |
| 2026-07-09 | JAT777 | - | Jul 9, 14:10 UTC | Jul 9, 17:10 UTC | 3h 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 CC-DID page for operator, model, and routing details .