sensors Mode-S transponder
E80637
ICAO 24-bit transponder address · allocated to Chile
- Hex
- E80637
- Octal
- 72003067
- Decimal
- 15,205,943
- Country
- CL
- Flights observed
- 51
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- Jul 26, 19:10 UTC
Last known position
Country allocation
The ICAO 24-bit address E80637 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 |
|---|---|---|---|
| JAT544 | Jat Airways | 6 | 2026-07-21 |
| JAT664 | Jat Airways | 5 | 2026-07-24 |
| JAT549 | Jat Airways | 4 | 2026-07-23 |
| JAT311 | Jat Airways | 4 | 2026-07-24 |
| JAT690 | - | 2 | 2026-07-16 |
| JAT669 | - | 2 | 2026-07-14 |
| JAT665 | Jat Airways | 2 | 2026-07-24 |
| JAT550 | Jat Airways | 2 | 2026-07-19 |
| JAT532 | - | 2 | 2026-07-22 |
| JAT530 | Jat Airways | 2 | 2026-07-19 |
| JAT503 | Jat Airways | 2 | 2026-07-20 |
| JAT501 | Jat Airways | 2 | 2026-07-26 |
| JAT500 | Jat Airways | 2 | 2026-07-25 |
| JAT310 | - | 2 | 2026-07-14 |
| OMD251 | - | 1 | 2026-07-01 |
| JAT668 | - | 1 | 2026-07-13 |
| JAT631 | - | 1 | 2026-07-13 |
| JAT547 | Jat Airways | 1 | 2026-07-25 |
| JAT546 | Jat Airways | 1 | 2026-07-24 |
| JAT533 | Jat Airways | 1 | 2026-07-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | JAT501 | SCL → CCP | Jul 26, 04:00 UTC | Jul 26, 19:10 UTC | 15h 11m |
| 2026-07-26 | JAT196 | PMC → SCL | Jul 26, 01:00 UTC | Jul 26, 02:15 UTC | 1h 15m |
| 2026-07-25 | JAT197 | SCL → PMC | Jul 25, 22:45 UTC | Jul 25, 23:00 UTC | 15m |
| 2026-07-25 | JAT500 | CCP → SCL | Jul 25, 21:15 UTC | Jul 25, 21:25 UTC | 10m |
| 2026-07-25 | JAT547 | CJC → CCP | Jul 25, 04:05 UTC | Jul 25, 19:15 UTC | 15h 10m |
| 2026-07-24 | JAT546 | CCP → CJC | Jul 24, 23:25 UTC | Jul 25, 19:15 UTC | 19h 50m |
| 2026-07-24 | JAT665 | LSC → CCP | Jul 24, 21:20 UTC | Jul 25, 19:15 UTC | 21h 55m |
| 2026-07-24 | JAT664 | CCP → LSC | Jul 24, 13:15 UTC | Jul 25, 04:20 UTC | 15h 5m |
| 2026-07-24 | JAT311 | ANF → CCP | Jul 24, 04:20 UTC | Jul 24, 23:40 UTC | 19h 20m |
| 2026-07-23 | JAT311 | ANF → CCP | Jul 23, 17:50 UTC | Jul 24, 13:30 UTC | 19h 40m |
| 2026-07-23 | JAT311 | ANF → CCP | Jul 23, 12:35 UTC | Jul 24, 04:35 UTC | 16h 0m |
| 2026-07-23 | JAT549 | CJC → CCP | Jul 23, 02:05 UTC | Jul 23, 20:10 UTC | 18h 5m |
| 2026-07-22 | JAT549 | CJC → CCP | Jul 22, 21:50 UTC | Jul 23, 20:10 UTC | 22h 20m |
| 2026-07-22 | JAT549 | CJC → CCP | Jul 22, 21:40 UTC | Jul 23, 17:55 UTC | 20h 15m |
| 2026-07-22 | JAT533 | IQQ → CCP | Jul 22, 19:30 UTC | Jul 23, 17:45 UTC | 22h 15m |
| 2026-07-22 | JAT532 | CCP → IQQ | Jul 22, 14:15 UTC | Jul 23, 12:45 UTC | 22h 30m |
| 2026-07-22 | JAT532 | - | Jul 22, 02:10 UTC | Jul 22, 21:50 UTC | 19h 40m |
| 2026-07-21 | JAT549 | CJC → CCP | Jul 21, 15:55 UTC | Jul 22, 14:30 UTC | 22h 35m |
| 2026-07-21 | JAT544 | CCP → CJC | Jul 21, 11:25 UTC | Jul 22, 02:20 UTC | 14h 55m |
| 2026-07-21 | JAT544 | CCP → CJC | Jul 21, 03:20 UTC | Jul 21, 18:15 UTC | 14h 55m |
| 2026-07-20 | JAT544 | CCP → CJC | Jul 20, 22:10 UTC | Jul 21, 18:15 UTC | 20h 4m |
| 2026-07-20 | JAT503 | SCL → CCP | Jul 20, 19:50 UTC | Jul 21, 18:15 UTC | 22h 25m |
| 2026-07-20 | JAT502 | - | Jul 20, 18:00 UTC | Jul 20, 18:15 UTC | 15m |
| 2026-07-19 | JAT550 | CCP → ANF | Jul 19, 22:10 UTC | Jul 20, 16:10 UTC | 18h 0m |
| 2026-07-19 | JAT531 | - | Jul 19, 19:20 UTC | Jul 20, 16:10 UTC | 20h 50m |
| 2026-07-19 | JAT530 | CCP → IQQ | Jul 19, 14:05 UTC | Jul 20, 02:55 UTC | 12h 50m |
| 2026-07-18 | JAT530 | CCP → IQQ | Jul 18, 23:50 UTC | Jul 19, 22:15 UTC | 22h 25m |
| 2026-07-18 | JAT665 | LSC → CCP | Jul 18, 23:35 UTC | Jul 19, 19:30 UTC | 19h 55m |
| 2026-07-18 | JAT664 | CCP → LSC | Jul 18, 15:05 UTC | Jul 18, 23:50 UTC | 8h 45m |
| 2026-07-18 | JAT664 | CCP → LSC | Jul 18, 01:50 UTC | Jul 18, 23:50 UTC | 22h 1m |
| 2026-07-18 | JAT664 | CCP → LSC | Jul 18, 01:39 UTC | Jul 18, 23:45 UTC | 22h 6m |
| 2026-07-17 | JAT664 | CCP → LSC | Jul 17, 21:34 UTC | Jul 18, 15:20 UTC | 17h 46m |
| 2026-07-17 | JAT500 | CCP → SCL | Jul 17, 17:25 UTC | Jul 17, 17:40 UTC | 15m |
| 2026-07-16 | JAT503 | - | Jul 16, 17:54 UTC | Jul 17, 00:55 UTC | 7h 0m |
| 2026-07-16 | JAT051 | - | Jul 16, 16:19 UTC | Jul 16, 16:40 UTC | 20m |
| 2026-07-16 | JAT690 | - | Jul 16, 12:20 UTC | Jul 16, 12:30 UTC | 10m |
| 2026-07-16 | JAT690 | - | Jul 16, 10:35 UTC | Jul 16, 10:50 UTC | 15m |
| 2026-07-15 | JAT550 | - | Jul 15, 12:55 UTC | Jul 16, 03:45 UTC | 14h 50m |
| 2026-07-15 | JAT311 | - | Jul 15, 02:10 UTC | Jul 15, 19:35 UTC | 17h 25m |
| 2026-07-14 | JAT310 | - | Jul 14, 17:55 UTC | Jul 15, 17:10 UTC | 23h 14m |
| 2026-07-14 | JAT310 | - | Jul 14, 15:50 UTC | Jul 15, 13:10 UTC | 21h 19m |
| 2026-07-14 | JAT544 | - | Jul 14, 11:20 UTC | Jul 15, 02:25 UTC | 15h 4m |
| 2026-07-14 | JAT669 | - | Jul 14, 01:05 UTC | Jul 14, 18:10 UTC | 17h 5m |
| 2026-07-13 | JAT669 | - | Jul 13, 17:50 UTC | Jul 14, 16:00 UTC | 22h 10m |
| 2026-07-13 | JAT668 | - | Jul 13, 17:40 UTC | Jul 14, 15:45 UTC | 22h 5m |
| 2026-07-13 | JAT631 | - | Jul 13, 15:20 UTC | Jul 14, 11:35 UTC | 20h 15m |
| 2026-07-12 | JAT544 | - | Jul 12, 13:50 UTC | Jul 13, 09:20 UTC | 19h 30m |
| 2026-07-12 | JAT544 | - | Jul 12, 13:40 UTC | Jul 13, 09:20 UTC | 19h 40m |
| 2026-07-12 | JAT501 | - | Jul 12, 04:25 UTC | Jul 12, 23:40 UTC | 19h 15m |
| 2026-07-10 | JAT1392 | - | Jul 10, 15:00 UTC | Jul 10, 15:20 UTC | 20m |
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.