sensors Mode-S transponder
345103
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-MII · AIRBUS A-330-300
- Hex
- 345103
- Octal
- 15050403
- Decimal
- 3,428,611
- Country
- ES
- Tail
- EC-MII
- Type
- A333
- Flights observed
- 74
- Distinct callsigns
- 15
- Country
- ES
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 345103 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| EVE801 | Air Evex | 14 | 2026-05-26 |
| EVE802 | Air Evex | 9 | 2026-05-27 |
| EVE898 | - | 8 | 2026-05-24 |
| ETR895 | Aerolíneas Estelar | 7 | 2026-05-27 |
| EVE198P | - | 6 | 2026-05-18 |
| EVE6421 | - | 5 | 2026-04-17 |
| ETR894 | Aerolíneas Estelar | 5 | 2026-05-29 |
| EVE897 | - | 3 | 2026-05-17 |
| EVE813 | Air Evex | 3 | 2026-05-25 |
| EVE455 | Air Evex | 3 | 2026-04-22 |
| EVE197P | - | 3 | 2026-05-10 |
| EVE122P | - | 3 | 2026-04-17 |
| EVE814 | Air Evex | 2 | 2026-05-26 |
| EVE120P | - | 2 | 2026-04-16 |
| EVE456 | Air Evex | 1 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | ETR894 | MAD → CCS | May 29, 13:30 UTC | May 29, 14:40 UTC | 1h 10m |
| 2026-05-27 | ETR895 | CCS → MAD | May 27, 13:20 UTC | May 28, 08:25 UTC | 19h 5m |
| 2026-05-27 | EVE802 | PUJ → MAD | May 27, 01:44 UTC | May 27, 09:15 UTC | 7h 30m |
| 2026-05-26 | EVE801 | MAD → PUJ | May 26, 14:30 UTC | May 26, 22:15 UTC | 7h 45m |
| 2026-05-26 | EVE814 | CUN → MAD | May 26, 02:35 UTC | May 26, 11:54 UTC | 9h 20m |
| 2026-05-25 | EVE813 | MAD → CUN | May 25, 13:45 UTC | May 25, 23:30 UTC | 9h 45m |
| 2026-05-24 | EVE898 | MAD → MAD | May 24, 14:45 UTC | May 25, 07:45 UTC | 17h 0m |
| 2026-05-23 | EVE801 | MAD → PUJ | May 23, 14:50 UTC | May 24, 09:20 UTC | 18h 30m |
| 2026-05-23 | ETR895 | CCS → MAD | May 23, 07:35 UTC | May 23, 08:55 UTC | 1h 20m |
| 2026-05-22 | ETR894 | MAD → CCS | May 22, 13:15 UTC | May 23, 08:55 UTC | 19h 39m |
| 2026-05-20 | ETR894 | MAD → CCS | May 20, 13:15 UTC | May 21, 08:45 UTC | 19h 30m |
| 2026-05-20 | EVE802 | PUJ → MAD | May 20, 02:00 UTC | May 20, 09:10 UTC | 7h 11m |
| 2026-05-19 | EVE801 | MAD → PUJ | May 19, 14:25 UTC | May 19, 22:35 UTC | 8h 10m |
| 2026-05-18 | EVE198P | - | May 18, 10:50 UTC | May 18, 11:25 UTC | 35m |
| 2026-05-17 | EVE897 | MAD → ZAZ | May 17, 18:25 UTC | May 18, 09:35 UTC | 15h 10m |
| 2026-05-17 | EVE802 | PUJ → MAD | May 17, 07:35 UTC | May 17, 08:50 UTC | 1h 15m |
| 2026-05-16 | EVE801 | MAD → PUJ | May 16, 14:31 UTC | May 16, 22:00 UTC | 7h 30m |
| 2026-05-15 | ETR895 | CCS → MAD | May 15, 14:50 UTC | May 16, 08:55 UTC | 18h 6m |
| 2026-05-15 | ETR895 | CCS → MAD | May 15, 13:25 UTC | May 16, 08:55 UTC | 19h 30m |
| 2026-05-13 | ETR895 | CCS → MAD | May 13, 13:10 UTC | May 14, 08:45 UTC | 19h 35m |
| 2026-05-13 | EVE802 | PUJ → MAD | May 13, 08:00 UTC | May 13, 09:10 UTC | 1h 10m |
| 2026-05-12 | EVE801 | MAD → PUJ | May 12, 14:25 UTC | May 12, 21:40 UTC | 7h 15m |
| 2026-05-11 | EVE198P | SVQ → MAD | May 11, 16:50 UTC | May 11, 17:35 UTC | 46m |
| 2026-05-10 | EVE898 | - | May 10, 20:50 UTC | May 11, 15:25 UTC | 18h 35m |
| 2026-05-10 | EVE898 | ZAZ → SVQ | May 10, 20:35 UTC | May 11, 15:25 UTC | 18h 50m |
| 2026-05-10 | EVE197P | MAD → ZAZ | May 10, 17:59 UTC | May 10, 18:35 UTC | 35m |
| 2026-05-10 | EVE802 | PUJ → MAD | May 10, 06:40 UTC | May 10, 09:10 UTC | 2h 30m |
| 2026-05-09 | EVE801 | MAD → PUJ | May 9, 15:05 UTC | May 9, 22:45 UTC | 7h 40m |
| 2026-05-08 | ETR895 | CCS → MAD | May 8, 14:50 UTC | May 9, 09:40 UTC | 18h 50m |
| 2026-05-08 | ETR895 | CCS → MAD | May 8, 13:55 UTC | May 9, 09:40 UTC | 19h 45m |
| 2026-05-06 | EVE802 | PUJ → MAD | May 6, 07:35 UTC | May 6, 08:50 UTC | 1h 15m |
| 2026-05-05 | EVE801 | MAD → PUJ | May 5, 14:25 UTC | May 5, 22:20 UTC | 7h 55m |
| 2026-05-05 | EVE814 | CUN → MAD | May 5, 03:30 UTC | May 5, 11:35 UTC | 8h 5m |
| 2026-05-05 | EVE813 | MAD → CUN | May 5, 00:25 UTC | May 5, 00:35 UTC | 10m |
| 2026-05-04 | EVE813 | MAD → CUN | May 4, 14:00 UTC | May 4, 23:55 UTC | 9h 56m |
| 2026-04-29 | EVE802 | PUJ → MAD | Apr 29, 01:50 UTC | Apr 29, 09:20 UTC | 7h 31m |
| 2026-04-28 | EVE801 | MAD → PUJ | Apr 28, 14:30 UTC | Apr 28, 23:00 UTC | 8h 30m |
| 2026-04-27 | EVE198P | - | Apr 27, 16:45 UTC | Apr 27, 17:35 UTC | 50m |
| 2026-04-26 | EVE898 | MAD → BCN | Apr 26, 20:50 UTC | Apr 27, 13:55 UTC | 17h 5m |
| 2026-04-25 | EVE801 | MAD → PUJ | Apr 25, 14:50 UTC | Apr 26, 09:20 UTC | 18h 30m |
| 2026-04-25 | EVE801 | MAD → PUJ | Apr 25, 14:40 UTC | Apr 26, 09:20 UTC | 18h 40m |
| 2026-04-24 | ETR894 | MAD → CCS | Apr 24, 14:50 UTC | Apr 25, 10:20 UTC | 19h 30m |
| 2026-04-24 | ETR894 | MAD → CCS | Apr 24, 14:40 UTC | Apr 25, 10:20 UTC | 19h 40m |
| 2026-04-24 | EVE456 | BOG → MAD | Apr 24, 01:40 UTC | Apr 24, 12:15 UTC | 10h 35m |
| 2026-04-22 | EVE455 | MAD → BOG | Apr 22, 17:40 UTC | Apr 22, 19:45 UTC | 2h 5m |
| 2026-04-22 | EVE455 | MAD → BOG | Apr 22, 15:00 UTC | Apr 22, 15:15 UTC | 15m |
| 2026-04-22 | EVE455 | MAD → BOG | Apr 22, 04:20 UTC | Apr 22, 14:00 UTC | 9h 40m |
| 2026-04-20 | EVE198P | - | Apr 20, 12:55 UTC | Apr 20, 13:45 UTC | 50m |
| 2026-04-19 | EVE898 | - | Apr 19, 19:05 UTC | Apr 20, 10:40 UTC | 15h 35m |
| 2026-04-19 | EVE197P | MAD → BCN | Apr 19, 15:40 UTC | Apr 19, 16:40 UTC | 1h 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 EC-MII page for operator, model, and routing details .