sensors Mode-S transponder
348342
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-OND · AIRBUS A-330-300
- Hex
- 348342
- Octal
- 15101502
- Decimal
- 3,441,474
- Country
- ES
- Tail
- EC-OND
- Type
- A333
- Flights observed
- 61
- Distinct callsigns
- 16
- Country
- ES
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 348342 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| WPT3153 | Wapiti Aviation | 14 | 2026-06-09 |
| WPT3154 | Wapiti Aviation | 12 | 2026-06-08 |
| WPT2152 | Wapiti Aviation | 8 | 2026-06-08 |
| WPT2151 | Wapiti Aviation | 8 | 2026-06-07 |
| WPT215P | Wapiti Aviation | 5 | 2026-05-24 |
| WPT154P | Wapiti Aviation | 3 | 2026-05-27 |
| WFL001P | - | 2 | 2026-04-18 |
| WPT416P | Wapiti Aviation | 1 | 2026-06-04 |
| WPT4160 | Wapiti Aviation | 1 | 2026-06-10 |
| WPT4159 | Wapiti Aviation | 1 | 2026-06-04 |
| WPT316P | - | 1 | 2026-05-30 |
| WPT3161 | Wapiti Aviation | 1 | 2026-06-05 |
| WPT315P | Wapiti Aviation | 1 | 2026-04-28 |
| WFL7616 | - | 1 | 2026-05-15 |
| WFL7615 | World2Fly | 1 | 2026-05-15 |
| WFL3516 | World2Fly | 1 | 2026-05-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | WPT4160 | MBJ → LIS | Jun 10, 14:15 UTC | Jun 11, 05:00 UTC | 14h 45m |
| 2026-06-09 | WPT3153 | LIS → PUJ | Jun 9, 10:50 UTC | Jun 10, 05:20 UTC | 18h 30m |
| 2026-06-08 | WPT3154 | PUJ → LIS | Jun 8, 14:20 UTC | Jun 9, 07:30 UTC | 17h 10m |
| 2026-06-08 | WPT2152 | CUN → LIS | Jun 8, 01:35 UTC | Jun 8, 10:20 UTC | 8h 45m |
| 2026-06-07 | WPT2151 | LIS → CUN | Jun 7, 14:10 UTC | Jun 7, 23:35 UTC | 9h 25m |
| 2026-06-07 | WPT3154 | PUJ → LIS | Jun 7, 03:40 UTC | Jun 7, 10:20 UTC | 6h 40m |
| 2026-06-06 | WPT3153 | LIS → PUJ | Jun 6, 14:59 UTC | Jun 6, 22:00 UTC | 7h 0m |
| 2026-06-05 | WPT3161 | LIS → LRM | Jun 5, 15:35 UTC | Jun 6, 08:00 UTC | 16h 25m |
| 2026-06-04 | WPT416P | MBJ → LIS | Jun 4, 18:10 UTC | Jun 5, 11:50 UTC | 17h 40m |
| 2026-06-04 | WPT4159 | LIS → MBJ | Jun 4, 10:50 UTC | Jun 5, 04:35 UTC | 17h 45m |
| 2026-06-03 | WPT3154 | PUJ → LIS | Jun 3, 04:35 UTC | Jun 3, 05:10 UTC | 35m |
| 2026-06-02 | WPT3153 | LIS → PUJ | Jun 2, 10:55 UTC | Jun 2, 17:50 UTC | 6h 55m |
| 2026-06-02 | WPT3154 | PUJ → LIS | Jun 2, 00:25 UTC | Jun 2, 07:15 UTC | 6h 50m |
| 2026-06-01 | WPT3153 | LIS → PUJ | Jun 1, 14:05 UTC | Jun 1, 21:05 UTC | 7h 0m |
| 2026-05-31 | WPT2152 | CUN → LIS | May 31, 23:10 UTC | Jun 1, 11:10 UTC | 12h 0m |
| 2026-05-31 | WPT2151 | LIS → CUN | May 31, 15:05 UTC | Jun 1, 11:10 UTC | 20h 5m |
| 2026-05-31 | WPT3154 | PUJ → LIS | May 31, 09:30 UTC | May 31, 10:20 UTC | 50m |
| 2026-05-30 | WPT3153 | LIS → PUJ | May 30, 15:05 UTC | May 30, 22:15 UTC | 7h 10m |
| 2026-05-30 | WPT316P | - | May 30, 07:50 UTC | May 30, 08:45 UTC | 55m |
| 2026-05-27 | WPT154P | LIS → MAD | May 27, 08:35 UTC | May 27, 09:25 UTC | 50m |
| 2026-05-26 | WPT3154 | PUJ → LIS | May 26, 22:39 UTC | May 27, 05:29 UTC | 6h 50m |
| 2026-05-26 | WPT3153 | LIS → PUJ | May 26, 11:00 UTC | May 26, 18:10 UTC | 7h 10m |
| 2026-05-26 | WPT3154 | PUJ → LIS | May 26, 00:24 UTC | May 26, 07:05 UTC | 6h 40m |
| 2026-05-25 | WPT3153 | LIS → PUJ | May 25, 14:05 UTC | May 25, 21:19 UTC | 7h 14m |
| 2026-05-25 | WPT2152 | CUN → LIS | May 25, 01:55 UTC | May 25, 10:35 UTC | 8h 40m |
| 2026-05-24 | WPT2151 | LIS → CUN | May 24, 23:00 UTC | May 24, 23:15 UTC | 15m |
| 2026-05-24 | WPT2151 | LIS → CUN | May 24, 14:00 UTC | May 24, 15:50 UTC | 1h 50m |
| 2026-05-24 | WPT215P | LIS → CUN | May 24, 08:50 UTC | May 24, 09:45 UTC | 55m |
| 2026-05-20 | WPT154P | LIS → MAD | May 20, 08:20 UTC | May 20, 09:20 UTC | 1h 0m |
| 2026-05-19 | WPT3154 | PUJ → LIS | May 19, 22:50 UTC | May 20, 05:30 UTC | 6h 41m |
| 2026-05-19 | WPT3153 | LIS → PUJ | May 19, 10:55 UTC | May 19, 18:35 UTC | 7h 40m |
| 2026-05-19 | WPT3154 | PUJ → LIS | May 19, 06:20 UTC | May 19, 07:05 UTC | 45m |
| 2026-05-18 | WPT3153 | LIS → PUJ | May 18, 14:00 UTC | May 18, 21:30 UTC | 7h 29m |
| 2026-05-18 | WPT2152 | CUN → LIS | May 18, 01:50 UTC | May 18, 10:15 UTC | 8h 25m |
| 2026-05-17 | WPT2151 | LIS → CUN | May 17, 13:45 UTC | May 17, 23:25 UTC | 9h 40m |
| 2026-05-17 | WPT215P | LIS → CUN | May 17, 09:20 UTC | May 17, 10:40 UTC | 1h 20m |
| 2026-05-15 | WFL7616 | ATH → MAD | May 15, 11:30 UTC | May 15, 15:15 UTC | 3h 44m |
| 2026-05-15 | WFL7615 | MAD → ATH | May 15, 06:20 UTC | May 15, 08:50 UTC | 2h 30m |
| 2026-05-13 | WPT154P | LIS → MAD | May 13, 08:45 UTC | May 13, 09:30 UTC | 45m |
| 2026-05-12 | WPT3154 | PUJ → LIS | May 12, 22:45 UTC | May 13, 05:25 UTC | 6h 40m |
| 2026-05-12 | WPT3153 | LIS → PUJ | May 12, 11:05 UTC | May 12, 17:55 UTC | 6h 50m |
| 2026-05-11 | WPT3153 | LIS → PUJ | May 11, 14:25 UTC | May 12, 07:20 UTC | 16h 56m |
| 2026-05-10 | WPT2152 | CUN → LIS | May 10, 22:05 UTC | May 11, 10:35 UTC | 12h 30m |
| 2026-05-10 | WPT2152 | CUN → LIS | May 10, 14:34 UTC | May 11, 10:35 UTC | 20h 0m |
| 2026-05-10 | WPT2151 | LIS → CUN | May 10, 14:09 UTC | May 11, 10:35 UTC | 20h 25m |
| 2026-05-10 | WPT215P | LIS → CUN | May 10, 10:35 UTC | May 10, 11:40 UTC | 1h 5m |
| 2026-05-05 | WFL3516 | PUJ → MAD | May 5, 23:00 UTC | May 6, 06:00 UTC | 7h 0m |
| 2026-05-05 | WPT3153 | LIS → PUJ | May 5, 10:45 UTC | May 5, 17:55 UTC | 7h 10m |
| 2026-05-05 | WPT3154 | PUJ → LIS | May 5, 06:30 UTC | May 5, 07:05 UTC | 35m |
| 2026-05-04 | WPT3153 | LIS → PUJ | May 4, 14:20 UTC | May 4, 21:30 UTC | 7h 11m |
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-OND page for operator, model, and routing details .