sensors Mode-S transponder
346390
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NGY · AIRBUS A-350-900
- Hex
- 346390
- Octal
- 15061620
- Decimal
- 3,433,360
- Country
- ES
- Tail
- EC-NGY
- Type
- A359
- Flights observed
- 86
- Distinct callsigns
- 14
- Country
- ES
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 346390 falls within the block assigned to Spain (ES) by ICAO Annex 10, Volume III. Every aircraft registered in Spain 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 14 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| EVE858 | Air Evex | 13 | 2026-05-26 |
| EVE846 | Air Evex | 13 | 2026-05-29 |
| EVE845 | Air Evex | 12 | 2026-05-28 |
| EVE815 | Air Evex | 12 | 2026-05-27 |
| EVE816 | Air Evex | 10 | 2026-05-20 |
| EVE857 | Air Evex | 8 | 2026-05-26 |
| EVE813 | Air Evex | 4 | 2026-04-27 |
| EVE814 | Air Evex | 3 | 2026-04-28 |
| EVE803 | - | 3 | 2026-04-29 |
| EVE806 | - | 2 | 2026-04-30 |
| EVE805 | - | 2 | 2026-04-28 |
| EVE804 | - | 2 | 2026-04-28 |
| EVE725P | Air Evex | 1 | 2026-04-20 |
| EVE7250 | Air Evex | 1 | 2026-04-19 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | EVE846 | BKK → MAD | May 29, 12:55 UTC | May 30, 00:30 UTC | 11h 35m |
| 2026-05-29 | EVE846 | BKK → MAD | May 29, 12:15 UTC | May 29, 12:25 UTC | 10m |
| 2026-05-28 | EVE845 | MAD → BKK | May 28, 21:00 UTC | May 29, 08:35 UTC | 11h 35m |
| 2026-05-27 | EVE815 | MAD → QRO | May 27, 20:30 UTC | May 28, 15:50 UTC | 19h 20m |
| 2026-05-27 | EVE815 | MAD → QRO | May 27, 16:05 UTC | May 28, 15:50 UTC | 23h 45m |
| 2026-05-27 | EVE815 | MAD → QRO | May 27, 15:25 UTC | May 28, 10:10 UTC | 18h 45m |
| 2026-05-26 | EVE858 | SJO → MAD | May 26, 14:05 UTC | May 27, 11:50 UTC | 21h 45m |
| 2026-05-26 | EVE857 | MAD → SJO | May 26, 12:54 UTC | May 27, 11:50 UTC | 22h 55m |
| 2026-05-23 | EVE858 | SJO → MAD | May 23, 23:00 UTC | May 24, 12:55 UTC | 13h 55m |
| 2026-05-23 | EVE858 | SJO → MAD | May 23, 16:30 UTC | May 24, 12:55 UTC | 20h 25m |
| 2026-05-23 | EVE857 | MAD → SJO | May 23, 14:10 UTC | May 24, 12:55 UTC | 22h 45m |
| 2026-05-22 | EVE846 | BKK → MAD | May 22, 12:20 UTC | May 23, 00:30 UTC | 12h 10m |
| 2026-05-21 | EVE845 | MAD → BKK | May 21, 20:40 UTC | May 22, 08:15 UTC | 11h 35m |
| 2026-05-20 | EVE816 | QRO → MAD | May 20, 22:15 UTC | May 21, 16:01 UTC | 17h 45m |
| 2026-05-20 | EVE816 | QRO → MAD | May 20, 16:05 UTC | May 21, 16:01 UTC | 23h 55m |
| 2026-05-20 | EVE816 | QRO → MAD | May 20, 15:30 UTC | May 21, 11:15 UTC | 19h 45m |
| 2026-05-19 | EVE858 | SJO → MAD | May 19, 22:05 UTC | May 20, 11:15 UTC | 13h 11m |
| 2026-05-19 | EVE858 | SJO → MAD | May 19, 12:35 UTC | May 20, 11:15 UTC | 22h 41m |
| 2026-05-15 | EVE846 | BKK → MAD | May 15, 14:15 UTC | May 16, 01:00 UTC | 10h 44m |
| 2026-05-15 | EVE846 | BKK → MAD | May 15, 12:30 UTC | May 15, 12:55 UTC | 25m |
| 2026-05-14 | EVE845 | MAD → BKK | May 14, 20:30 UTC | May 15, 07:25 UTC | 10h 55m |
| 2026-05-13 | EVE816 | QRO → MAD | May 13, 22:05 UTC | May 14, 16:25 UTC | 18h 20m |
| 2026-05-13 | EVE816 | QRO → MAD | May 13, 20:35 UTC | May 14, 16:25 UTC | 19h 50m |
| 2026-05-13 | EVE815 | MAD → QRO | May 13, 16:05 UTC | May 14, 16:00 UTC | 23h 55m |
| 2026-05-13 | EVE815 | MAD → QRO | May 13, 15:15 UTC | May 14, 11:25 UTC | 20h 10m |
| 2026-05-12 | EVE858 | SJO → MAD | May 12, 19:55 UTC | May 13, 11:25 UTC | 15h 30m |
| 2026-05-12 | EVE858 | SJO → MAD | May 12, 14:05 UTC | May 13, 11:25 UTC | 21h 20m |
| 2026-05-12 | EVE857 | MAD → SJO | May 12, 13:10 UTC | May 13, 11:25 UTC | 22h 15m |
| 2026-05-08 | EVE846 | BKK → MAD | May 8, 12:20 UTC | May 9, 01:15 UTC | 12h 55m |
| 2026-05-07 | EVE845 | MAD → BKK | May 7, 20:45 UTC | May 8, 03:44 UTC | 7h 0m |
| 2026-05-06 | EVE815 | MAD → QRO | May 6, 23:40 UTC | May 7, 16:30 UTC | 16h 51m |
| 2026-05-06 | EVE815 | MAD → QRO | May 6, 20:55 UTC | May 7, 16:30 UTC | 19h 36m |
| 2026-05-06 | EVE815 | MAD → QRO | May 6, 16:05 UTC | May 7, 16:00 UTC | 23h 55m |
| 2026-05-06 | EVE815 | MAD → QRO | May 6, 15:35 UTC | May 7, 09:05 UTC | 17h 30m |
| 2026-05-05 | EVE858 | SJO → MAD | May 5, 19:45 UTC | May 6, 11:00 UTC | 15h 15m |
| 2026-05-05 | EVE857 | MAD → SJO | May 5, 12:40 UTC | May 6, 11:00 UTC | 22h 20m |
| 2026-05-02 | EVE858 | SJO → MAD | May 2, 22:05 UTC | May 3, 13:25 UTC | 15h 19m |
| 2026-05-02 | EVE857 | MAD → SJO | May 2, 14:40 UTC | May 3, 13:25 UTC | 22h 44m |
| 2026-05-01 | EVE846 | BKK → MAD | May 1, 12:35 UTC | May 2, 01:10 UTC | 12h 35m |
| 2026-04-30 | EVE845 | MAD → BKK | Apr 30, 20:45 UTC | May 1, 07:45 UTC | 11h 0m |
| 2026-04-30 | EVE806 | - | Apr 30, 01:05 UTC | Apr 30, 15:15 UTC | 14h 10m |
| 2026-04-29 | EVE803 | - | Apr 29, 16:05 UTC | Apr 30, 15:15 UTC | 23h 9m |
| 2026-04-28 | EVE804 | - | Apr 28, 21:00 UTC | Apr 29, 11:25 UTC | 14h 25m |
| 2026-04-28 | EVE805 | MAD → BCN | Apr 28, 12:55 UTC | Apr 29, 11:25 UTC | 22h 30m |
| 2026-04-28 | EVE814 | CUN → MAD | Apr 28, 00:50 UTC | Apr 28, 09:30 UTC | 8h 40m |
| 2026-04-27 | EVE813 | MAD → CUN | Apr 27, 13:00 UTC | Apr 27, 22:45 UTC | 9h 45m |
| 2026-04-25 | EVE814 | CUN → MAD | Apr 25, 02:25 UTC | Apr 25, 11:00 UTC | 8h 35m |
| 2026-04-24 | EVE813 | MAD → CUN | Apr 24, 14:00 UTC | Apr 24, 23:45 UTC | 9h 45m |
| 2026-04-22 | EVE806 | - | Apr 22, 22:45 UTC | Apr 23, 13:00 UTC | 14h 15m |
| 2026-04-22 | EVE803 | - | Apr 22, 14:05 UTC | Apr 23, 13:00 UTC | 22h 55m |
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 EC-NGY page for operator, model, and routing details .