sensors Mode-S transponder
48506D
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-TFM · BOEING 787-8 Dreamliner
- Hex
- 48506D
- Octal
- 22050155
- Decimal
- 4,739,181
- Country
- NL
- Tail
- PH-TFM
- Type
- B788
- Flights observed
- 106
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 5h ago
Current position
Country allocation
The ICAO 24-bit address 48506D falls within the block assigned to Netherlands (NL) by ICAO Annex 10, Volume III. Every aircraft registered in Netherlands 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 |
|---|---|---|---|
| TFL365 | Arkefly | 16 | 2026-05-23 |
| TFL757 | Arkefly | 11 | 2026-05-20 |
| TFL511 | Arkefly | 11 | 2026-05-06 |
| TFL381 | Arkefly | 11 | 2026-05-19 |
| TFL368 | Arkefly | 10 | 2026-05-27 |
| TFL393 | Arkefly | 9 | 2026-05-29 |
| TFL372 | Arkefly | 7 | 2026-05-24 |
| TFL371 | Arkefly | 6 | 2026-05-24 |
| TFL367 | Arkefly | 5 | 2026-05-27 |
| TFL3BM | - | 4 | 2026-05-02 |
| TFL391 | Arkefly | 4 | 2026-05-28 |
| TFL5YW | - | 3 | 2026-05-02 |
| TFL942F | Arkefly | 1 | 2026-04-30 |
| TFL9422 | Arkefly | 1 | 2026-04-29 |
| TFL941F | Arkefly | 1 | 2026-04-29 |
| TFL822 | Arkefly | 1 | 2026-05-16 |
| TFL821 | Arkefly | 1 | 2026-05-16 |
| TFL70V | Arkefly | 1 | 2026-04-28 |
| TFL6GB | Arkefly | 1 | 2026-04-28 |
| TFL3DY | Arkefly | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TFL393 | CUR → AMS | May 29, 09:55 UTC | May 30, 00:35 UTC | 14h 40m |
| 2026-05-28 | TFL391 | CUR → AMS | May 28, 17:10 UTC | May 29, 07:05 UTC | 13h 55m |
| 2026-05-28 | TFL391 | CUR → AMS | May 28, 09:25 UTC | May 29, 07:05 UTC | 21h 40m |
| 2026-05-27 | TFL368 | CUR → AMS | May 27, 09:20 UTC | May 28, 04:40 UTC | 19h 20m |
| 2026-05-27 | TFL367 | AMS → CUR | May 27, 08:55 UTC | May 28, 04:40 UTC | 19h 45m |
| 2026-05-27 | TFL393 | CUR → AMS | May 27, 04:04 UTC | May 27, 05:45 UTC | 1h 40m |
| 2026-05-26 | TFL393 | CUR → AMS | May 26, 06:34 UTC | May 26, 15:45 UTC | 9h 10m |
| 2026-05-24 | TFL372 | CUR → AMS | May 24, 13:20 UTC | May 25, 08:50 UTC | 19h 30m |
| 2026-05-24 | TFL371 | AMS → CUR | May 24, 12:40 UTC | May 25, 08:50 UTC | 20h 10m |
| 2026-05-23 | TFL365 | BON → AMS | May 23, 20:25 UTC | May 24, 09:55 UTC | 13h 30m |
| 2026-05-23 | TFL365 | BON → AMS | May 23, 13:20 UTC | May 24, 09:55 UTC | 20h 35m |
| 2026-05-23 | TFL365 | BON → AMS | May 23, 12:10 UTC | May 24, 09:55 UTC | 21h 45m |
| 2026-05-22 | TFL393 | CUR → AMS | May 22, 20:45 UTC | May 23, 09:40 UTC | 12h 54m |
| 2026-05-22 | TFL393 | CUR → AMS | May 22, 13:20 UTC | May 23, 09:40 UTC | 20h 19m |
| 2026-05-22 | TFL393 | CUR → AMS | May 22, 12:30 UTC | May 23, 09:40 UTC | 21h 10m |
| 2026-05-21 | TFL372 | CUR → AMS | May 21, 22:00 UTC | May 22, 09:45 UTC | 11h 45m |
| 2026-05-21 | TFL371 | AMS → CUR | May 21, 13:35 UTC | May 22, 09:45 UTC | 20h 10m |
| 2026-05-20 | TFL757 | CUR → AMS | May 20, 19:55 UTC | May 21, 10:05 UTC | 14h 10m |
| 2026-05-20 | TFL757 | CUR → AMS | May 20, 13:20 UTC | May 21, 10:05 UTC | 20h 45m |
| 2026-05-20 | TFL757 | CUR → AMS | May 20, 11:40 UTC | May 21, 10:05 UTC | 22h 25m |
| 2026-05-19 | TFL368 | CUR → AMS | May 19, 13:20 UTC | May 20, 08:15 UTC | 18h 56m |
| 2026-05-19 | TFL367 | AMS → CUR | May 19, 12:10 UTC | May 20, 08:15 UTC | 20h 6m |
| 2026-05-19 | TFL381 | CUR → AMS | May 19, 00:55 UTC | May 19, 08:40 UTC | 7h 45m |
| 2026-05-18 | TFL381 | CUR → AMS | May 18, 22:10 UTC | May 18, 22:20 UTC | 10m |
| 2026-05-18 | TFL381 | CUR → AMS | May 18, 20:40 UTC | May 18, 20:55 UTC | 15m |
| 2026-05-18 | TFL381 | CUR → AMS | May 18, 10:55 UTC | May 18, 20:10 UTC | 9h 14m |
| 2026-05-18 | TFL757 | CUR → AMS | May 18, 00:20 UTC | May 18, 08:10 UTC | 7h 50m |
| 2026-05-17 | TFL757 | CUR → AMS | May 17, 08:45 UTC | May 17, 17:30 UTC | 8h 45m |
| 2026-05-16 | TFL822 | CUN → AMS | May 16, 19:50 UTC | May 17, 04:50 UTC | 9h 0m |
| 2026-05-16 | TFL821 | AMS → CUN | May 16, 07:05 UTC | May 16, 17:10 UTC | 10h 5m |
| 2026-05-14 | TFL372 | CUR → AMS | May 14, 21:20 UTC | May 15, 10:00 UTC | 12h 40m |
| 2026-05-14 | TFL372 | CUR → AMS | May 14, 13:20 UTC | May 15, 10:00 UTC | 20h 40m |
| 2026-05-13 | TFL757 | CUR → AMS | May 13, 19:45 UTC | May 14, 10:25 UTC | 14h 40m |
| 2026-05-13 | TFL757 | CUR → AMS | May 13, 11:35 UTC | May 14, 10:25 UTC | 22h 50m |
| 2026-05-12 | TFL368 | CUR → AMS | May 12, 13:20 UTC | May 13, 09:05 UTC | 19h 45m |
| 2026-05-12 | TFL368 | CUR → AMS | May 12, 12:50 UTC | May 13, 09:05 UTC | 20h 15m |
| 2026-05-12 | TFL381 | CUR → AMS | May 12, 08:35 UTC | May 12, 10:10 UTC | 1h 35m |
| 2026-05-11 | TFL381 | CUR → AMS | May 11, 21:15 UTC | May 11, 21:35 UTC | 20m |
| 2026-05-11 | TFL381 | CUR → AMS | May 11, 12:35 UTC | May 11, 20:40 UTC | 8h 6m |
| 2026-05-10 | TFL757 | CUR → AMS | May 10, 19:15 UTC | May 11, 10:10 UTC | 14h 55m |
| 2026-05-10 | TFL757 | CUR → AMS | May 10, 11:25 UTC | May 11, 10:10 UTC | 22h 45m |
| 2026-05-09 | TFL365 | BON → AMS | May 9, 18:50 UTC | May 10, 09:10 UTC | 14h 20m |
| 2026-05-09 | TFL365 | BON → AMS | May 9, 11:20 UTC | May 10, 09:10 UTC | 21h 50m |
| 2026-05-09 | TFL365 | BON → AMS | May 9, 11:00 UTC | May 10, 09:10 UTC | 22h 10m |
| 2026-05-08 | TFL393 | CUR → AMS | May 8, 18:10 UTC | May 9, 08:25 UTC | 14h 15m |
| 2026-05-08 | TFL393 | CUR → AMS | May 8, 11:19 UTC | May 9, 08:25 UTC | 21h 5m |
| 2026-05-08 | TFL393 | CUR → AMS | May 8, 10:19 UTC | May 9, 08:25 UTC | 22h 5m |
| 2026-05-07 | TFL391 | CUR → AMS | May 7, 17:20 UTC | May 8, 07:20 UTC | 13h 59m |
| 2026-05-07 | TFL391 | CUR → AMS | May 7, 09:25 UTC | May 8, 07:20 UTC | 21h 55m |
| 2026-05-06 | TFL511 | CUN → AMS | May 6, 01:40 UTC | May 6, 10:01 UTC | 8h 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 PH-TFM page for operator, model, and routing details .