sensors Mode-S transponder
348390
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-OOI · AIRBUS A-330-300
- Hex
- 348390
- Octal
- 15101620
- Decimal
- 3,441,552
- Country
- ES
- Tail
- EC-OOI
- Type
- A333
- Flights observed
- 55
- Distinct callsigns
- 16
- Country
- ES
- Last broadcast
- 9m ago
Current position
Country allocation
The ICAO 24-bit address 348390 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 |
|---|---|---|---|
| TAR202 | Tunisair | 10 | 2026-05-20 |
| PUE221 | Aeropuelche | 9 | 2026-04-26 |
| TAR203 | Tunisair | 7 | 2026-05-21 |
| TAR718 | Tunisair | 6 | 2026-05-15 |
| TAR722 | Tunisair | 5 | 2026-05-15 |
| PUE702 | Aeropuelche | 4 | 2026-04-17 |
| PUE701 | - | 4 | 2026-04-16 |
| PUE301 | Aeropuelche | 2 | 2026-05-02 |
| TAR723 | Tunisair | 1 | 2026-05-10 |
| TAR719 | Tunisair | 1 | 2026-05-12 |
| PUE902 | - | 1 | 2026-05-28 |
| PUE901 | - | 1 | 2026-05-27 |
| PUE711 | - | 1 | 2026-04-12 |
| PUE302 | Aeropuelche | 1 | 2026-05-02 |
| PUE2P | - | 1 | 2026-05-21 |
| PUE003P | - | 1 | 2026-05-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | PUE003P | - | May 29, 12:55 UTC | May 30, 10:00 UTC | 21h 5m |
| 2026-05-28 | PUE902 | - | May 28, 05:50 UTC | May 28, 08:05 UTC | 2h 15m |
| 2026-05-27 | PUE901 | - | May 27, 06:20 UTC | May 27, 08:35 UTC | 2h 16m |
| 2026-05-21 | PUE2P | - | May 21, 02:05 UTC | May 21, 21:30 UTC | 19h 25m |
| 2026-05-21 | TAR203 | YUL → TUN | May 21, 00:55 UTC | May 21, 21:30 UTC | 20h 35m |
| 2026-05-20 | TAR203 | YUL → TUN | May 20, 20:05 UTC | May 21, 20:00 UTC | 23h 55m |
| 2026-05-20 | TAR203 | YUL → TUN | May 20, 19:40 UTC | May 21, 02:50 UTC | 7h 10m |
| 2026-05-20 | TAR202 | TUN → YUL | May 20, 09:10 UTC | May 20, 17:35 UTC | 8h 25m |
| 2026-05-18 | TAR203 | YUL → TUN | May 18, 19:30 UTC | May 19, 02:30 UTC | 7h 0m |
| 2026-05-18 | TAR202 | TUN → YUL | May 18, 09:10 UTC | May 18, 17:10 UTC | 8h 0m |
| 2026-05-16 | TAR203 | YUL → TUN | May 16, 21:30 UTC | May 17, 04:30 UTC | 7h 0m |
| 2026-05-16 | TAR202 | TUN → YUL | May 16, 09:16 UTC | May 16, 17:55 UTC | 8h 40m |
| 2026-05-15 | TAR202 | TUN → YUL | May 15, 19:30 UTC | May 16, 17:55 UTC | 22h 26m |
| 2026-05-15 | TAR722 | TUN → ORY | May 15, 11:55 UTC | May 15, 17:40 UTC | 5h 44m |
| 2026-05-15 | TAR718 | TUN → ORY | May 15, 07:50 UTC | May 15, 09:35 UTC | 1h 45m |
| 2026-05-14 | TAR718 | TUN → ORY | May 14, 12:05 UTC | May 15, 09:35 UTC | 21h 30m |
| 2026-05-14 | TAR718 | TUN → ORY | May 14, 11:10 UTC | May 15, 09:35 UTC | 22h 25m |
| 2026-05-13 | TAR203 | YUL → TUN | May 13, 20:05 UTC | May 14, 09:15 UTC | 13h 10m |
| 2026-05-13 | TAR202 | TUN → YUL | May 13, 09:20 UTC | May 13, 17:35 UTC | 8h 15m |
| 2026-05-12 | TAR202 | TUN → YUL | May 12, 20:05 UTC | May 13, 17:35 UTC | 21h 30m |
| 2026-05-12 | TAR202 | TUN → YUL | May 12, 19:25 UTC | May 13, 17:35 UTC | 22h 10m |
| 2026-05-12 | TAR722 | TUN → ORY | May 12, 16:00 UTC | May 12, 17:45 UTC | 1h 45m |
| 2026-05-12 | TAR719 | ORY → TUN | May 12, 11:10 UTC | May 12, 12:50 UTC | 1h 40m |
| 2026-05-12 | TAR718 | TUN → ORY | May 12, 07:30 UTC | May 12, 09:20 UTC | 1h 50m |
| 2026-05-10 | TAR723 | ORY → TUN | May 10, 20:30 UTC | May 10, 22:05 UTC | 1h 35m |
| 2026-05-10 | TAR722 | TUN → ORY | May 10, 11:25 UTC | May 10, 17:55 UTC | 6h 30m |
| 2026-05-09 | TAR203 | YUL → TUN | May 9, 19:45 UTC | May 10, 09:24 UTC | 13h 40m |
| 2026-05-09 | TAR202 | TUN → YUL | May 9, 09:25 UTC | May 9, 16:50 UTC | 7h 25m |
| 2026-05-08 | TAR202 | TUN → YUL | May 8, 20:05 UTC | May 9, 16:50 UTC | 20h 45m |
| 2026-05-08 | TAR202 | TUN → YUL | May 8, 19:20 UTC | May 9, 16:50 UTC | 21h 30m |
| 2026-05-08 | TAR722 | TUN → ORY | May 8, 11:19 UTC | May 8, 17:40 UTC | 6h 20m |
| 2026-05-07 | TAR718 | TUN → ORY | May 7, 20:40 UTC | May 8, 09:19 UTC | 12h 40m |
| 2026-05-07 | TAR722 | TUN → ORY | May 7, 12:20 UTC | May 7, 18:40 UTC | 6h 20m |
| 2026-05-06 | TAR718 | TUN → ORY | May 6, 15:30 UTC | May 7, 09:50 UTC | 18h 20m |
| 2026-05-02 | PUE302 | LIM → MAD | May 2, 17:55 UTC | May 3, 11:05 UTC | 17h 9m |
| 2026-05-02 | PUE301 | MAD → LIM | May 2, 10:05 UTC | May 3, 10:00 UTC | 23h 54m |
| 2026-05-02 | PUE301 | MAD → LIM | May 2, 09:40 UTC | May 3, 01:50 UTC | 16h 10m |
| 2026-04-26 | PUE221 | CTG → MAD | Apr 26, 06:15 UTC | Apr 26, 13:15 UTC | 7h 0m |
| 2026-04-25 | PUE221 | CTG → MAD | Apr 25, 13:25 UTC | Apr 25, 21:50 UTC | 8h 25m |
| 2026-04-23 | PUE221 | CTG → MAD | Apr 23, 02:00 UTC | Apr 23, 13:25 UTC | 11h 25m |
| 2026-04-22 | PUE221 | CTG → MAD | Apr 22, 23:45 UTC | Apr 23, 00:00 UTC | 15m |
| 2026-04-22 | PUE221 | CTG → MAD | Apr 22, 13:25 UTC | Apr 22, 14:40 UTC | 1h 15m |
| 2026-04-21 | PUE221 | CTG → MAD | Apr 21, 05:10 UTC | Apr 21, 13:10 UTC | 8h 0m |
| 2026-04-21 | PUE221 | CTG → MAD | Apr 21, 01:40 UTC | Apr 21, 01:45 UTC | 5m |
| 2026-04-20 | PUE221 | CTG → MAD | Apr 20, 23:10 UTC | Apr 20, 23:35 UTC | 25m |
| 2026-04-20 | PUE221 | CTG → MAD | Apr 20, 13:15 UTC | Apr 20, 14:35 UTC | 1h 20m |
| 2026-04-17 | PUE702 | CCS → MAD | Apr 17, 06:10 UTC | Apr 17, 07:15 UTC | 1h 5m |
| 2026-04-16 | PUE701 | - | Apr 16, 19:50 UTC | Apr 16, 20:05 UTC | 15m |
| 2026-04-16 | PUE701 | - | Apr 16, 11:25 UTC | Apr 16, 12:34 UTC | 1h 10m |
| 2026-04-15 | PUE702 | CCS → MAD | Apr 15, 07:01 UTC | Apr 15, 07:20 UTC | 20m |
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-OOI page for operator, model, and routing details .