sensors Mode-S transponder
3463DA
ICAO 24-bit transponder address · allocated to Spain
Currently assigned to EC-NHM · AIRBUS A-330-300
- Hex
- 3463DA
- Octal
- 15061732
- Decimal
- 3,433,434
- Country
- ES
- Tail
- EC-NHM
- Type
- A333
- Flights observed
- 113
- Distinct callsigns
- 20
- Country
- ES
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 3463DA 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 |
|---|---|---|---|
| TFL368 | Arkefly | 7 | 2026-07-22 |
| SVA9544 | - | 5 | 2026-05-18 |
| SVA9351 | - | 5 | 2026-04-28 |
| SVA9461 | - | 4 | 2026-05-09 |
| SVA5358 | Saudi Arabian Airlines | 4 | 2026-06-09 |
| SVA5180 | - | 4 | 2026-06-17 |
| SVA5135 | - | 4 | 2026-04-27 |
| TFL381 | - | 3 | 2026-07-15 |
| TFL367 | - | 3 | 2026-07-21 |
| SVA9525 | - | 3 | 2026-05-16 |
| SVA9457 | - | 3 | 2026-05-08 |
| SVA9448 | - | 3 | 2026-05-07 |
| SVA9302 | - | 3 | 2026-05-18 |
| SVA5347 | - | 3 | 2026-05-10 |
| SVA5188 | - | 3 | 2026-06-03 |
| TLF368 | - | 2 | 2026-07-08 |
| TFL70V | - | 2 | 2026-07-18 |
| TFL066P | Arkefly | 2 | 2026-07-22 |
| SVA9534 | - | 2 | 2026-05-17 |
| SVA5232 | - | 2 | 2026-06-04 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | CRL924 | ORY → FDF | Jul 25, 20:20 UTC | Jul 25, 20:45 UTC | 25m |
| 2026-07-25 | CRL924 | ORY → FDF | Jul 25, 12:35 UTC | Jul 25, 13:55 UTC | 1h 20m |
| 2026-07-25 | CRL024 | MAD → ORY | Jul 25, 08:20 UTC | Jul 25, 09:50 UTC | 1h 30m |
| 2026-07-22 | TFL066P | WAW → BRU | Jul 22, 13:55 UTC | Jul 22, 16:00 UTC | 2h 5m |
| 2026-07-22 | TFL368 | CUR → AMS | Jul 22, 11:10 UTC | Jul 22, 11:30 UTC | 20m |
| 2026-07-21 | TFL367 | - | Jul 21, 14:35 UTC | Jul 22, 10:25 UTC | 19h 50m |
| 2026-07-21 | TFL367 | - | Jul 21, 13:30 UTC | Jul 22, 10:25 UTC | 20h 55m |
| 2026-07-20 | TFL368 | CUR → AMS | Jul 20, 20:05 UTC | Jul 21, 10:20 UTC | 14h 15m |
| 2026-07-20 | TFL368 | CUR → AMS | Jul 20, 12:35 UTC | Jul 21, 10:20 UTC | 21h 45m |
| 2026-07-18 | TFL6GB | - | Jul 18, 18:15 UTC | Jul 18, 21:40 UTC | 3h 25m |
| 2026-07-18 | TFL70V | - | Jul 18, 15:40 UTC | Jul 18, 16:05 UTC | 25m |
| 2026-07-18 | TFL70V | - | Jul 18, 12:05 UTC | Jul 18, 15:10 UTC | 3h 5m |
| 2026-07-16 | TFL368 | - | Jul 16, 23:20 UTC | Jul 17, 08:04 UTC | 8h 45m |
| 2026-07-16 | TFL368 | - | Jul 16, 10:35 UTC | Jul 17, 08:04 UTC | 21h 30m |
| 2026-07-16 | TFL368 | - | Jul 16, 10:25 UTC | Jul 17, 08:04 UTC | 21h 40m |
| 2026-07-15 | TFL381 | - | Jul 15, 16:15 UTC | Jul 16, 00:50 UTC | 8h 35m |
| 2026-07-14 | TFL381 | - | Jul 14, 20:00 UTC | Jul 14, 20:15 UTC | 15m |
| 2026-07-14 | TFL381 | - | Jul 14, 10:55 UTC | Jul 14, 12:30 UTC | 1h 35m |
| 2026-07-14 | TFL065P | - | Jul 14, 06:20 UTC | Jul 14, 08:10 UTC | 1h 50m |
| 2026-07-13 | VKG4950 | - | Jul 13, 19:00 UTC | Jul 13, 22:20 UTC | 3h 20m |
| 2026-07-13 | VKG513 | AYT → ARN | Jul 13, 14:05 UTC | Jul 13, 17:40 UTC | 3h 35m |
| 2026-07-12 | VKG512 | ARN → AYT | Jul 12, 21:25 UTC | Jul 13, 00:55 UTC | 3h 30m |
| 2026-07-12 | VKG4912 | MAD → ARN | Jul 12, 16:05 UTC | Jul 12, 19:20 UTC | 3h 15m |
| 2026-07-10 | TFL069P | - | Jul 10, 08:30 UTC | Jul 10, 10:30 UTC | 2h 0m |
| 2026-07-09 | TFL368 | - | Jul 9, 10:35 UTC | Jul 10, 06:30 UTC | 19h 55m |
| 2026-07-09 | TFL367 | - | Jul 9, 09:40 UTC | Jul 10, 06:30 UTC | 20h 50m |
| 2026-07-08 | TLF368 | - | Jul 8, 11:00 UTC | Jul 9, 06:30 UTC | 19h 30m |
| 2026-07-08 | TLF368 | - | Jul 8, 09:05 UTC | Jul 9, 06:30 UTC | 21h 25m |
| 2026-07-07 | TFL066P | - | Jul 7, 15:35 UTC | Jul 7, 17:45 UTC | 2h 10m |
| 2026-06-30 | PLM209P | - | Jun 30, 18:35 UTC | Jul 1, 13:00 UTC | 18h 25m |
| 2026-06-30 | PLM209P | - | Jun 30, 17:05 UTC | Jul 1, 13:00 UTC | 19h 55m |
| 2026-06-30 | SVA2345 | - | Jun 30, 12:10 UTC | Jul 1, 10:30 UTC | 22h 20m |
| 2026-06-30 | SVA2345 | - | Jun 30, 01:35 UTC | Jun 30, 19:50 UTC | 18h 15m |
| 2026-06-29 | SVA5117 | - | Jun 29, 19:54 UTC | Jun 29, 23:14 UTC | 3h 20m |
| 2026-06-26 | SVA9404 | - | Jun 26, 02:14 UTC | Jun 26, 05:10 UTC | 2h 55m |
| 2026-06-25 | SVA5109 | - | Jun 25, 11:44 UTC | Jun 25, 23:59 UTC | 12h 15m |
| 2026-06-25 | SVA5108 | - | Jun 25, 06:30 UTC | Jun 25, 09:50 UTC | 3h 20m |
| 2026-06-19 | SVA9530 | - | Jun 19, 18:59 UTC | Jun 20, 02:59 UTC | 8h 0m |
| 2026-06-17 | SVA5202 | - | Jun 17, 20:30 UTC | Jun 18, 13:50 UTC | 17h 20m |
| 2026-06-17 | SVA5202 | - | Jun 17, 16:35 UTC | Jun 18, 13:50 UTC | 21h 15m |
| 2026-06-17 | SVA5180 | - | Jun 17, 15:20 UTC | Jun 18, 13:50 UTC | 22h 30m |
| 2026-06-17 | SVA5180 | - | Jun 17, 02:35 UTC | Jun 17, 23:10 UTC | 20h 35m |
| 2026-06-17 | SVA5180 | - | Jun 17, 01:45 UTC | Jun 17, 23:10 UTC | 21h 25m |
| 2026-06-16 | SVA5180 | - | Jun 16, 20:35 UTC | Jun 17, 20:30 UTC | 23h 55m |
| 2026-06-16 | SVA5160 | - | Jun 16, 19:40 UTC | Jun 17, 17:15 UTC | 21h 36m |
| 2026-06-16 | SVA9350 | - | Jun 16, 08:44 UTC | Jun 17, 04:10 UTC | 19h 26m |
| 2026-06-15 | SVA5132 | - | Jun 15, 12:35 UTC | Jun 16, 07:09 UTC | 18h 35m |
| 2026-06-15 | SVA5132 | - | Jun 15, 11:39 UTC | Jun 16, 07:09 UTC | 19h 30m |
| 2026-06-11 | SVA9402 | - | Jun 11, 03:10 UTC | Jun 11, 03:45 UTC | 35m |
| 2026-06-10 | SVA5107 | - | Jun 10, 14:20 UTC | Jun 11, 01:10 UTC | 10h 50m |
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-NHM page for operator, model, and routing details .