sensors Mode-S transponder
E8404D
ICAO 24-bit transponder address · allocated to Ecuador
Currently assigned to HC-CJV · AIRBUS A-320
- Hex
- E8404D
- Octal
- 72040115
- Decimal
- 15,220,813
- Country
- EC
- Tail
- HC-CJV
- Type
- A320
- Flights observed
- 78
- Distinct callsigns
- 16
- Country
- EC
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address E8404D falls within the block assigned to Ecuador (EC) by ICAO Annex 10, Volume III. Every aircraft registered in Ecuador 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 |
|---|---|---|---|
| GLG7378 | - | 15 | 2026-07-12 |
| GLG7377 | - | 14 | 2026-07-12 |
| GLG8377 | Aerolineas Galapagos (Aerogal) | 5 | 2026-05-30 |
| GLG8373 | Aerolineas Galapagos (Aerogal) | 5 | 2026-06-12 |
| GLG7380 | Aerolineas Galapagos (Aerogal) | 5 | 2026-05-27 |
| GLG8396 | Aerolineas Galapagos (Aerogal) | 4 | 2026-05-30 |
| GLG8394 | Aerolineas Galapagos (Aerogal) | 4 | 2026-04-22 |
| GLG8380 | Aerolineas Galapagos (Aerogal) | 4 | 2026-05-24 |
| GLG7379 | Aerolineas Galapagos (Aerogal) | 4 | 2026-05-27 |
| GLG8391 | Aerolineas Galapagos (Aerogal) | 3 | 2026-06-12 |
| GLG8384 | Aerolineas Galapagos (Aerogal) | 3 | 2026-05-31 |
| GLG8383 | Aerolineas Galapagos (Aerogal) | 3 | 2026-05-28 |
| GLG8372 | Aerolineas Galapagos (Aerogal) | 3 | 2026-05-18 |
| GLG8395 | Aerolineas Galapagos (Aerogal) | 2 | 2026-05-28 |
| GLG8385 | Aerolineas Galapagos (Aerogal) | 2 | 2026-05-31 |
| GLG8376 | Aerolineas Galapagos (Aerogal) | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | GLG7377 | - | Jul 12, 05:50 UTC | Jul 12, 08:50 UTC | 3h 0m |
| 2026-07-12 | GLG7378 | - | Jul 12, 03:35 UTC | Jul 12, 04:10 UTC | 35m |
| 2026-07-06 | GLG7377 | - | Jul 6, 06:05 UTC | Jul 6, 07:55 UTC | 1h 50m |
| 2026-07-06 | GLG7378 | - | Jul 6, 03:30 UTC | Jul 6, 03:55 UTC | 25m |
| 2026-07-06 | GLG7378 | - | Jul 6, 02:00 UTC | Jul 6, 02:10 UTC | 10m |
| 2026-07-04 | GLG7377 | - | Jul 4, 05:55 UTC | Jul 4, 07:45 UTC | 1h 50m |
| 2026-07-04 | GLG7378 | - | Jul 4, 02:15 UTC | Jul 4, 04:15 UTC | 2h 0m |
| 2026-06-28 | GLG7377 | - | Jun 28, 06:05 UTC | Jun 28, 07:50 UTC | 1h 45m |
| 2026-06-28 | GLG7378 | - | Jun 28, 01:59 UTC | Jun 28, 03:50 UTC | 1h 50m |
| 2026-06-18 | GLG7377 | - | Jun 18, 06:05 UTC | Jun 18, 07:50 UTC | 1h 45m |
| 2026-06-18 | GLG7378 | - | Jun 18, 02:20 UTC | Jun 18, 04:15 UTC | 1h 55m |
| 2026-06-12 | GLG8373 | BOG → UIO | Jun 12, 21:35 UTC | Jun 13, 01:15 UTC | 3h 40m |
| 2026-06-12 | GLG8391 | BOG → GYE | Jun 12, 03:10 UTC | Jun 12, 03:20 UTC | 10m |
| 2026-06-11 | GLG7377 | MIA → GYE | Jun 11, 05:55 UTC | Jun 12, 01:15 UTC | 19h 21m |
| 2026-06-11 | GLG7378 | GYE → MIA | Jun 11, 03:30 UTC | Jun 11, 04:05 UTC | 35m |
| 2026-06-07 | GLG7377 | MIA → GYE | Jun 7, 05:55 UTC | Jun 7, 07:40 UTC | 1h 45m |
| 2026-06-06 | GLG7378 | GYE → MIA | Jun 6, 17:54 UTC | Jun 7, 03:55 UTC | 10h 0m |
| 2026-06-06 | GLG7377 | MIA → GYE | Jun 6, 06:05 UTC | Jun 6, 15:34 UTC | 9h 30m |
| 2026-06-06 | GLG7378 | GYE → MIA | Jun 6, 02:25 UTC | Jun 6, 04:25 UTC | 2h 0m |
| 2026-06-04 | GLG8376 | UIO → BOG | Jun 4, 01:00 UTC | Jun 4, 01:20 UTC | 20m |
| 2026-06-02 | GLG7377 | MIA → GYE | Jun 2, 06:00 UTC | Jun 2, 07:45 UTC | 1h 45m |
| 2026-06-02 | GLG7378 | GYE → MIA | Jun 2, 02:05 UTC | Jun 2, 04:05 UTC | 2h 0m |
| 2026-05-31 | GLG8373 | BOG → UIO | May 31, 21:40 UTC | May 31, 21:55 UTC | 15m |
| 2026-05-31 | GLG8384 | GYE → BOG | May 31, 16:20 UTC | May 31, 16:45 UTC | 25m |
| 2026-05-31 | GLG8385 | BOG → GYE | May 31, 12:25 UTC | May 31, 12:40 UTC | 15m |
| 2026-05-30 | GLG8377 | BOG → UIO | May 30, 18:00 UTC | May 31, 10:10 UTC | 16h 10m |
| 2026-05-30 | GLG8396 | BOG → UIO | May 30, 04:20 UTC | May 30, 08:05 UTC | 3h 45m |
| 2026-05-29 | GLG8373 | BOG → UIO | May 29, 21:25 UTC | May 30, 02:45 UTC | 5h 20m |
| 2026-05-28 | GLG8383 | BOG → GYE | May 28, 21:10 UTC | May 29, 01:25 UTC | 4h 15m |
| 2026-05-28 | GLG8384 | GYE → BOG | May 28, 12:45 UTC | May 28, 16:55 UTC | 4h 10m |
| 2026-05-28 | GLG8395 | UIO → BOG | May 28, 09:35 UTC | May 28, 09:55 UTC | 20m |
| 2026-05-27 | GLG7379 | MIA → GYE | May 27, 06:20 UTC | May 27, 08:15 UTC | 1h 55m |
| 2026-05-27 | GLG7380 | GYE → MIA | May 27, 02:44 UTC | May 27, 04:34 UTC | 1h 50m |
| 2026-05-26 | GLG7380 | GYE → MIA | May 26, 07:29 UTC | May 27, 04:34 UTC | 21h 5m |
| 2026-05-26 | GLG7377 | MIA → GYE | May 26, 06:10 UTC | May 27, 04:34 UTC | 22h 25m |
| 2026-05-26 | GLG7378 | GYE → MIA | May 26, 03:40 UTC | May 26, 04:15 UTC | 35m |
| 2026-05-24 | GLG8385 | BOG → GYE | May 24, 12:25 UTC | May 24, 12:45 UTC | 20m |
| 2026-05-24 | GLG8380 | CLO → BOG | May 24, 09:55 UTC | May 24, 10:15 UTC | 20m |
| 2026-05-18 | GLG8373 | BOG → UIO | May 18, 21:25 UTC | May 18, 21:40 UTC | 15m |
| 2026-05-18 | GLG8372 | UIO → BOG | May 18, 16:15 UTC | May 18, 16:35 UTC | 20m |
| 2026-05-18 | GLG8377 | BOG → UIO | May 18, 12:15 UTC | May 18, 12:35 UTC | 20m |
| 2026-05-18 | GLG8396 | BOG → UIO | May 18, 05:00 UTC | May 18, 09:50 UTC | 4h 50m |
| 2026-05-18 | GLG8376 | UIO → BOG | May 18, 00:55 UTC | May 18, 01:20 UTC | 25m |
| 2026-05-14 | GLG7377 | MIA → GYE | May 14, 06:00 UTC | May 14, 07:55 UTC | 1h 55m |
| 2026-05-14 | GLG7378 | GYE → MIA | May 14, 02:10 UTC | May 14, 03:55 UTC | 1h 45m |
| 2026-05-11 | GLG7377 | MIA → GYE | May 11, 06:10 UTC | May 11, 07:55 UTC | 1h 45m |
| 2026-05-11 | GLG7378 | GYE → MIA | May 11, 02:00 UTC | May 11, 03:55 UTC | 1h 55m |
| 2026-05-06 | GLG7379 | MIA → GYE | May 6, 06:15 UTC | May 6, 06:45 UTC | 30m |
| 2026-05-06 | GLG7380 | GYE → MIA | May 6, 02:20 UTC | May 6, 04:20 UTC | 2h 0m |
| 2026-05-05 | GLG7380 | GYE → MIA | May 5, 07:35 UTC | May 6, 04:20 UTC | 20h 45m |
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 HC-CJV page for operator, model, and routing details .