sensors Mode-S transponder
E80622
ICAO 24-bit transponder address · allocated to Chile
Currently assigned to CC-DII · AIRBUS A-320neo
- Hex
- E80622
- Octal
- 72003042
- Decimal
- 15,205,922
- Country
- CL
- Tail
- CC-DII
- Type
- A20N
- Flights observed
- 171
- Distinct callsigns
- 20
- Country
- CL
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address E80622 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 |
|---|---|---|---|
| JAP7801 | - | 15 | 2026-06-30 |
| JAP7800 | - | 15 | 2026-06-30 |
| JAP7319 | - | 12 | 2026-06-16 |
| JAP7318 | - | 12 | 2026-06-16 |
| JAP7753 | - | 10 | 2026-06-11 |
| JAP7752 | - | 9 | 2026-06-11 |
| JAP7255 | - | 9 | 2026-07-13 |
| JAP7222 | - | 8 | 2026-07-12 |
| JAP7781 | - | 7 | 2026-07-09 |
| JAP7166 | - | 7 | 2026-06-15 |
| JAP7167 | - | 6 | 2026-06-15 |
| JAP7254 | - | 5 | 2026-05-22 |
| JAP7163 | - | 5 | 2026-06-11 |
| JAP7162 | - | 5 | 2026-06-11 |
| JAP7730 | - | 4 | 2026-07-02 |
| JAP7258 | - | 4 | 2026-06-16 |
| JAP7780 | - | 3 | 2026-04-13 |
| JAP7259 | - | 3 | 2026-06-07 |
| JAP7256 | - | 3 | 2026-06-13 |
| JAP7220 | - | 3 | 2026-06-15 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | JAP7169 | - | Jul 14, 02:25 UTC | Jul 14, 03:00 UTC | 35m |
| 2026-07-14 | JAP7168 | - | Jul 14, 00:30 UTC | Jul 14, 01:05 UTC | 35m |
| 2026-07-13 | JAP7255 | - | Jul 13, 20:00 UTC | Jul 13, 22:35 UTC | 2h 35m |
| 2026-07-12 | JAP7222 | - | Jul 12, 16:40 UTC | Jul 12, 19:45 UTC | 3h 5m |
| 2026-07-12 | JAP7161 | - | Jul 12, 06:25 UTC | Jul 12, 07:05 UTC | 40m |
| 2026-07-12 | JAP7160 | - | Jul 12, 04:35 UTC | Jul 12, 05:10 UTC | 35m |
| 2026-07-10 | JAP7255 | - | Jul 10, 20:05 UTC | Jul 10, 22:30 UTC | 2h 25m |
| 2026-07-10 | JAP7222 | - | Jul 10, 15:35 UTC | Jul 10, 18:25 UTC | 2h 50m |
| 2026-07-09 | JAP7781 | - | Jul 9, 17:10 UTC | Jul 9, 22:25 UTC | 5h 15m |
| 2026-07-08 | JAT990 | - | Jul 8, 20:00 UTC | Jul 8, 20:10 UTC | 10m |
| 2026-07-08 | JAT755 | - | Jul 8, 13:30 UTC | Jul 8, 16:55 UTC | 3h 25m |
| 2026-07-08 | JAT754 | - | Jul 8, 08:55 UTC | Jul 8, 11:55 UTC | 3h 0m |
| 2026-07-08 | JAT754 | - | Jul 8, 08:15 UTC | Jul 8, 08:25 UTC | 10m |
| 2026-07-02 | JAP7781 | - | Jul 2, 15:50 UTC | Jul 2, 22:50 UTC | 7h 0m |
| 2026-07-02 | JAP7730 | - | Jul 2, 10:30 UTC | Jul 2, 10:40 UTC | 10m |
| 2026-07-01 | JAP7255 | - | Jul 1, 22:15 UTC | Jul 1, 22:30 UTC | 15m |
| 2026-06-30 | JAP7801 | - | Jun 30, 08:40 UTC | Jun 30, 09:55 UTC | 1h 15m |
| 2026-06-30 | JAP7800 | - | Jun 30, 06:00 UTC | Jun 30, 07:10 UTC | 1h 10m |
| 2026-06-26 | JAP7730 | - | Jun 26, 09:30 UTC | Jun 26, 09:39 UTC | 10m |
| 2026-06-25 | JAP7730 | - | Jun 25, 09:14 UTC | Jun 25, 09:25 UTC | 10m |
| 2026-06-20 | JAP7801 | - | Jun 20, 11:40 UTC | Jun 20, 12:19 UTC | 40m |
| 2026-06-20 | JAP7800 | - | Jun 20, 09:44 UTC | Jun 20, 10:20 UTC | 35m |
| 2026-06-18 | JAP7801 | - | Jun 18, 08:25 UTC | Jun 18, 09:10 UTC | 45m |
| 2026-06-18 | JAP7800 | - | Jun 18, 06:35 UTC | Jun 18, 07:10 UTC | 35m |
| 2026-06-16 | JAP7258 | - | Jun 16, 14:25 UTC | Jun 16, 14:39 UTC | 15m |
| 2026-06-16 | JAP7319 | - | Jun 16, 12:20 UTC | Jun 16, 12:45 UTC | 25m |
| 2026-06-16 | JAP7318 | - | Jun 16, 10:40 UTC | Jun 16, 11:15 UTC | 35m |
| 2026-06-15 | JAP7220 | - | Jun 15, 20:54 UTC | Jun 15, 23:54 UTC | 3h 0m |
| 2026-06-15 | JAP7167 | - | Jun 15, 18:10 UTC | Jun 15, 18:40 UTC | 30m |
| 2026-06-15 | JAP7166 | - | Jun 15, 16:09 UTC | Jun 15, 16:45 UTC | 35m |
| 2026-06-14 | JAP7261 | - | Jun 14, 19:55 UTC | Jun 14, 22:15 UTC | 2h 20m |
| 2026-06-13 | JAP7256 | - | Jun 13, 20:40 UTC | Jun 13, 23:30 UTC | 2h 50m |
| 2026-06-12 | JAP7801 | - | Jun 12, 08:35 UTC | Jun 12, 23:55 UTC | 15h 20m |
| 2026-06-12 | JAP7800 | - | Jun 12, 06:50 UTC | Jun 12, 07:15 UTC | 25m |
| 2026-06-11 | JAP7753 | - | Jun 11, 22:55 UTC | Jun 12, 00:55 UTC | 2h 1m |
| 2026-06-11 | JAP7752 | - | Jun 11, 18:50 UTC | Jun 11, 21:05 UTC | 2h 15m |
| 2026-06-11 | JAP7163 | - | Jun 11, 16:15 UTC | Jun 11, 16:50 UTC | 35m |
| 2026-06-11 | JAP7162 | - | Jun 11, 14:30 UTC | Jun 11, 15:05 UTC | 35m |
| 2026-06-11 | JAP7318 | - | Jun 11, 10:25 UTC | Jun 11, 12:50 UTC | 2h 25m |
| 2026-06-10 | JAP7801 | - | Jun 10, 08:30 UTC | Jun 10, 23:40 UTC | 15h 10m |
| 2026-06-10 | JAP7800 | - | Jun 10, 06:45 UTC | Jun 10, 07:10 UTC | 25m |
| 2026-06-09 | JAP7257 | - | Jun 9, 19:05 UTC | Jun 9, 19:20 UTC | 15m |
| 2026-06-08 | JAP7801 | - | Jun 8, 08:40 UTC | Jun 8, 22:30 UTC | 13h 50m |
| 2026-06-08 | JAP7800 | - | Jun 8, 06:35 UTC | Jun 8, 07:00 UTC | 25m |
| 2026-06-07 | JAP7753 | - | Jun 7, 23:05 UTC | Jun 8, 01:05 UTC | 2h 0m |
| 2026-06-07 | JAP7752 | - | Jun 7, 20:50 UTC | Jun 7, 21:05 UTC | 15m |
| 2026-06-07 | JAP7259 | - | Jun 7, 16:35 UTC | Jun 7, 16:50 UTC | 15m |
| 2026-06-07 | JAP7319 | - | Jun 7, 12:30 UTC | Jun 7, 12:55 UTC | 25m |
| 2026-06-07 | JAP7318 | - | Jun 7, 10:40 UTC | Jun 7, 11:15 UTC | 35m |
| 2026-06-06 | JAP7167 | - | Jun 6, 04:10 UTC | Jun 6, 04:35 UTC | 25m |
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-DII page for operator, model, and routing details .