sensors Mode-S transponder
347555
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-OAP · AIRBUS A-330-200
- Hex
- 347555
- Octal
- 15072525
- Decimal
- 3,437,909
- Country
- ES
- Tail
- EC-OAP
- Type
- A332
- Flights observed
- 84
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 9d ago
Last known position
Country allocation
The ICAO 24-bit address 347555 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PUE302 | - | 22 | 2026-07-02 |
| PUE301 | - | 19 | 2026-07-01 |
| MMZ352 | EuroAtlantic Airways | 5 | 2026-07-03 |
| MMZ351 | - | 5 | 2026-07-03 |
| MMZ100P | - | 4 | 2026-07-02 |
| STP507 | - | 3 | 2026-06-26 |
| PUE702 | Aeropuelche | 3 | 2026-05-01 |
| PUE701 | Aeropuelche | 3 | 2026-04-30 |
| PUE242 | Aeropuelche | 3 | 2026-05-09 |
| STP508 | STP Airways | 2 | 2026-07-04 |
| PUE221 | Aeropuelche | 2 | 2026-05-02 |
| MMZ673 | - | 2 | 2026-06-28 |
| MMZ661P | - | 2 | 2026-06-28 |
| MMZ101P | - | 2 | 2026-06-20 |
| PUE502 | Aeropuelche | 1 | 2026-05-28 |
| PUE501 | Aeropuelche | 1 | 2026-05-27 |
| MMZ674P | - | 1 | 2026-06-28 |
| MMZ648P | - | 1 | 2026-06-18 |
| MMZ647 | EuroAtlantic Airways | 1 | 2026-06-18 |
| MMZ633 | - | 1 | 2026-06-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-04 | STP508 | TMS → LIS | Jul 4, 00:05 UTC | Jul 4, 14:15 UTC | 14h 10m |
| 2026-07-03 | MMZ352 | OXB → LIS | Jul 3, 15:35 UTC | Jul 3, 19:25 UTC | 3h 50m |
| 2026-07-03 | MMZ351 | - | Jul 3, 08:30 UTC | Jul 3, 12:15 UTC | 3h 45m |
| 2026-07-02 | MMZ100P | - | Jul 2, 21:00 UTC | Jul 2, 22:00 UTC | 1h 0m |
| 2026-07-02 | PUE302 | - | Jul 2, 01:10 UTC | Jul 2, 11:35 UTC | 10h 25m |
| 2026-07-01 | PUE301 | - | Jul 1, 09:55 UTC | Jul 1, 21:15 UTC | 11h 20m |
| 2026-06-28 | MMZ674P | - | Jun 28, 16:49 UTC | Jun 28, 20:19 UTC | 3h 30m |
| 2026-06-28 | MMZ673 | MAD → BGO | Jun 28, 12:15 UTC | Jun 28, 14:59 UTC | 2h 45m |
| 2026-06-28 | MMZ661P | - | Jun 28, 08:44 UTC | Jun 28, 09:39 UTC | 55m |
| 2026-06-26 | STP507 | LIS → LIS | Jun 26, 23:39 UTC | Jun 27, 15:05 UTC | 15h 25m |
| 2026-06-26 | MMZ352 | OXB → LIS | Jun 26, 15:49 UTC | Jun 26, 19:24 UTC | 3h 35m |
| 2026-06-26 | MMZ351 | - | Jun 26, 07:30 UTC | Jun 26, 11:14 UTC | 3h 45m |
| 2026-06-25 | MMZ100P | MAD → LIS | Jun 25, 16:55 UTC | Jun 25, 17:54 UTC | 1h 0m |
| 2026-06-20 | MMZ101P | LIS → MAD | Jun 20, 16:55 UTC | Jun 20, 17:49 UTC | 55m |
| 2026-06-19 | STP507 | LIS → TMS | Jun 19, 23:39 UTC | Jun 20, 14:39 UTC | 15h 0m |
| 2026-06-19 | MMZ352 | OXB → LIS | Jun 19, 15:29 UTC | Jun 19, 19:19 UTC | 3h 50m |
| 2026-06-19 | MMZ351 | LIS → OXB | Jun 19, 07:45 UTC | Jun 19, 11:45 UTC | 4h 0m |
| 2026-06-18 | MMZ648P | MUC → LIS | Jun 18, 19:50 UTC | Jun 18, 22:45 UTC | 2h 55m |
| 2026-06-18 | MMZ647 | AMS → TNG | Jun 18, 16:30 UTC | Jun 18, 18:35 UTC | 2h 5m |
| 2026-06-17 | MMZ633 | MUC → GAE | Jun 17, 05:05 UTC | Jun 17, 07:00 UTC | 1h 55m |
| 2026-06-15 | MMZ614P | - | Jun 15, 09:30 UTC | Jun 15, 15:55 UTC | 6h 25m |
| 2026-06-14 | MMZ673 | - | Jun 14, 06:55 UTC | Jun 14, 13:50 UTC | 6h 55m |
| 2026-06-13 | MMZ661P | LIS → RIX | Jun 13, 18:10 UTC | Jun 13, 22:00 UTC | 3h 50m |
| 2026-06-12 | STP507 | LIS → TMS | Jun 12, 23:50 UTC | Jun 13, 15:05 UTC | 15h 14m |
| 2026-06-12 | MMZ352 | OXB → LIS | Jun 12, 14:20 UTC | Jun 12, 18:05 UTC | 3h 45m |
| 2026-06-12 | MMZ351 | LIS → OXB | Jun 12, 07:30 UTC | Jun 12, 11:10 UTC | 3h 40m |
| 2026-06-11 | MMZ100P | - | Jun 11, 14:45 UTC | Jun 11, 15:45 UTC | 1h 0m |
| 2026-06-07 | PUE302 | LIM → MAD | Jun 7, 19:15 UTC | Jun 8, 10:25 UTC | 15h 10m |
| 2026-06-07 | PUE302 | LIM → MAD | Jun 7, 11:20 UTC | Jun 8, 10:25 UTC | 23h 5m |
| 2026-06-07 | PUE301 | MAD → LIM | Jun 7, 09:30 UTC | Jun 8, 09:15 UTC | 23h 45m |
| 2026-06-06 | MMZ101P | - | Jun 6, 18:09 UTC | Jun 6, 18:55 UTC | 45m |
| 2026-06-05 | STP508 | TMS → LIS | Jun 5, 23:40 UTC | Jun 6, 14:50 UTC | 15h 10m |
| 2026-06-05 | MMZ352 | OXB → LIS | Jun 5, 15:20 UTC | Jun 5, 19:10 UTC | 3h 50m |
| 2026-06-05 | MMZ351 | LIS → OXB | Jun 5, 08:05 UTC | Jun 5, 11:40 UTC | 3h 35m |
| 2026-06-04 | MMZ100P | MAD → LIS | Jun 4, 10:50 UTC | Jun 4, 12:00 UTC | 1h 10m |
| 2026-05-31 | PUE302 | LIM → MAD | May 31, 18:55 UTC | Jun 1, 11:10 UTC | 16h 15m |
| 2026-05-31 | PUE301 | MAD → LIM | May 31, 09:25 UTC | Jun 1, 01:20 UTC | 15h 55m |
| 2026-05-29 | PUE302 | LIM → MAD | May 29, 19:15 UTC | May 30, 11:15 UTC | 16h 0m |
| 2026-05-29 | PUE301 | MAD → LIM | May 29, 09:25 UTC | May 30, 03:25 UTC | 18h 0m |
| 2026-05-28 | PUE502 | EZE → MAD | May 28, 16:35 UTC | May 29, 04:20 UTC | 11h 45m |
| 2026-05-27 | PUE501 | MAD → EZE | May 27, 21:25 UTC | May 28, 09:55 UTC | 12h 30m |
| 2026-05-24 | PUE302 | LIM → MAD | May 24, 19:25 UTC | May 25, 10:35 UTC | 15h 10m |
| 2026-05-24 | PUE301 | MAD → LIM | May 24, 09:35 UTC | May 24, 20:15 UTC | 10h 40m |
| 2026-05-22 | PUE302 | LIM → MAD | May 22, 19:10 UTC | May 23, 10:50 UTC | 15h 39m |
| 2026-05-22 | PUE302 | LIM → MAD | May 22, 11:20 UTC | May 23, 10:50 UTC | 23h 30m |
| 2026-05-22 | PUE301 | MAD → LIM | May 22, 09:35 UTC | May 23, 01:15 UTC | 15h 40m |
| 2026-05-21 | PUE302 | LIM → MAD | May 21, 01:25 UTC | May 21, 11:25 UTC | 10h 0m |
| 2026-05-20 | PUE301 | MAD → LIM | May 20, 10:00 UTC | May 20, 22:00 UTC | 12h 0m |
| 2026-05-19 | PUE302 | LIM → MAD | May 19, 00:15 UTC | May 19, 11:05 UTC | 10h 50m |
| 2026-05-18 | PUE301 | MAD → LIM | May 18, 09:25 UTC | May 18, 21:15 UTC | 11h 49m |
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-OAP page for operator, model, and routing details .