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
- 196
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 8h ago
Last known 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 |
|---|---|---|---|
| TFL393 | - | 38 | 2026-07-07 |
| TFL365 | - | 27 | 2026-07-13 |
| TFL368 | - | 24 | 2026-07-12 |
| TFL191 | - | 18 | 2026-07-09 |
| TFL391 | - | 14 | 2026-07-02 |
| TFL511 | - | 13 | 2026-06-24 |
| TFL757 | Arkefly | 11 | 2026-05-20 |
| TFL381 | Arkefly | 11 | 2026-05-19 |
| TFL372 | Arkefly | 7 | 2026-05-24 |
| TFL371 | Arkefly | 6 | 2026-05-24 |
| TFL367 | Arkefly | 5 | 2026-05-27 |
| TFL3BM | - | 4 | 2026-05-02 |
| TFL5YW | - | 3 | 2026-05-02 |
| TFL822 | - | 2 | 2026-07-05 |
| TFL821 | - | 2 | 2026-07-04 |
| TFL942F | Arkefly | 1 | 2026-04-30 |
| TFL9422 | Arkefly | 1 | 2026-04-29 |
| TFL941F | Arkefly | 1 | 2026-04-29 |
| TFL7GX | - | 1 | 2026-07-09 |
| TFL79B | - | 1 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | TFL365 | - | Jul 13, 09:15 UTC | Jul 13, 22:55 UTC | 13h 40m |
| 2026-07-12 | TFL368 | - | Jul 12, 16:35 UTC | Jul 13, 05:35 UTC | 13h 0m |
| 2026-07-12 | TFL368 | - | Jul 12, 09:20 UTC | Jul 13, 05:35 UTC | 20h 15m |
| 2026-07-12 | TFL368 | - | Jul 12, 09:00 UTC | Jul 13, 05:35 UTC | 20h 35m |
| 2026-07-11 | TFL368 | - | Jul 11, 17:30 UTC | Jul 12, 06:05 UTC | 12h 35m |
| 2026-07-11 | TFL368 | - | Jul 11, 09:40 UTC | Jul 12, 06:05 UTC | 20h 25m |
| 2026-07-09 | TFL191 | - | Jul 9, 19:20 UTC | Jul 10, 15:55 UTC | 20h 35m |
| 2026-07-09 | TFL191 | AMS → AMS | Jul 9, 18:50 UTC | Jul 10, 15:55 UTC | 21h 5m |
| 2026-07-09 | TFL7GX | - | Jul 9, 12:00 UTC | Jul 9, 15:35 UTC | 3h 35m |
| 2026-07-09 | TFL4BC | - | Jul 9, 07:20 UTC | Jul 9, 10:25 UTC | 3h 5m |
| 2026-07-08 | TFL79B | - | Jul 8, 18:25 UTC | Jul 8, 22:05 UTC | 3h 40m |
| 2026-07-08 | TFL50G | - | Jul 8, 13:00 UTC | Jul 8, 16:45 UTC | 3h 45m |
| 2026-07-07 | TFL393 | - | Jul 7, 14:35 UTC | Jul 8, 04:40 UTC | 14h 5m |
| 2026-07-07 | TFL393 | - | Jul 7, 07:20 UTC | Jul 8, 04:40 UTC | 21h 20m |
| 2026-07-07 | TFL393 | AMS → AMS | Jul 7, 06:35 UTC | Jul 8, 04:40 UTC | 22h 5m |
| 2026-07-05 | TFL191 | - | Jul 5, 23:25 UTC | Jul 6, 17:45 UTC | 18h 20m |
| 2026-07-05 | TFL191 | - | Jul 5, 21:20 UTC | Jul 6, 17:45 UTC | 20h 25m |
| 2026-07-05 | TFL191 | AMS → AMS | Jul 5, 20:05 UTC | Jul 6, 17:45 UTC | 21h 40m |
| 2026-07-05 | TFL822 | CUN → AMS | Jul 5, 03:30 UTC | Jul 5, 12:15 UTC | 8h 45m |
| 2026-07-04 | TFL821 | AMS → CUN | Jul 4, 15:25 UTC | Jul 5, 01:20 UTC | 9h 55m |
| 2026-07-03 | TFL393 | - | Jul 3, 17:55 UTC | Jul 4, 07:55 UTC | 14h 0m |
| 2026-07-03 | TFL393 | - | Jul 3, 11:20 UTC | Jul 4, 07:55 UTC | 20h 35m |
| 2026-07-03 | TFL393 | - | Jul 3, 10:05 UTC | Jul 4, 07:55 UTC | 21h 50m |
| 2026-07-02 | TFL391 | - | Jul 2, 17:10 UTC | Jul 3, 06:25 UTC | 13h 15m |
| 2026-07-02 | TFL391 | - | Jul 2, 09:20 UTC | Jul 3, 06:25 UTC | 21h 5m |
| 2026-07-02 | TFL391 | - | Jul 2, 09:00 UTC | Jul 3, 06:25 UTC | 21h 25m |
| 2026-06-26 | TFL393 | - | Jun 26, 18:39 UTC | Jun 27, 08:29 UTC | 13h 50m |
| 2026-06-26 | TFL393 | - | Jun 26, 11:20 UTC | Jun 27, 08:29 UTC | 21h 10m |
| 2026-06-26 | TFL393 | AMS → AMS | Jun 26, 10:35 UTC | Jun 27, 08:29 UTC | 21h 55m |
| 2026-06-25 | TFL368 | - | Jun 25, 18:24 UTC | Jun 26, 07:30 UTC | 13h 5m |
| 2026-06-25 | TFL368 | - | Jun 25, 11:19 UTC | Jun 26, 07:30 UTC | 20h 10m |
| 2026-06-25 | TFL368 | - | Jun 25, 10:35 UTC | Jun 26, 07:30 UTC | 20h 55m |
| 2026-06-24 | TFL511 | CUN → AMS | Jun 24, 22:39 UTC | Jun 25, 07:30 UTC | 8h 50m |
| 2026-06-24 | TFL511 | AMS → CUN | Jun 24, 08:20 UTC | Jun 24, 20:40 UTC | 12h 20m |
| 2026-06-23 | TFL191 | AMS → CFU | Jun 23, 21:49 UTC | Jun 24, 00:59 UTC | 3h 10m |
| 2026-06-22 | TFL191 | AMS → CFU | Jun 22, 17:50 UTC | Jun 22, 19:19 UTC | 1h 30m |
| 2026-06-21 | TFL191 | AMS → CFU | Jun 21, 23:24 UTC | Jun 22, 19:19 UTC | 19h 55m |
| 2026-06-21 | TFL191 | AMS → CFU | Jun 21, 21:19 UTC | Jun 22, 19:19 UTC | 22h 0m |
| 2026-06-21 | TFL191 | AMS → CFU | Jun 21, 21:10 UTC | Jun 22, 19:14 UTC | 22h 5m |
| 2026-06-20 | TFL365 | - | Jun 20, 19:04 UTC | Jun 21, 09:00 UTC | 13h 55m |
| 2026-06-20 | TFL365 | - | Jun 20, 11:20 UTC | Jun 21, 09:00 UTC | 21h 40m |
| 2026-06-20 | TFL365 | AMS → AMS | Jun 20, 11:14 UTC | Jun 21, 09:00 UTC | 21h 45m |
| 2026-06-19 | TFL393 | - | Jun 19, 18:05 UTC | Jun 20, 08:05 UTC | 14h 0m |
| 2026-06-19 | TFL393 | - | Jun 19, 11:20 UTC | Jun 20, 08:05 UTC | 20h 45m |
| 2026-06-19 | TFL393 | - | Jun 19, 10:14 UTC | Jun 20, 08:05 UTC | 21h 50m |
| 2026-06-18 | TFL391 | - | Jun 18, 16:55 UTC | Jun 19, 06:39 UTC | 13h 44m |
| 2026-06-18 | TFL391 | - | Jun 18, 09:20 UTC | Jun 19, 06:39 UTC | 21h 19m |
| 2026-06-18 | TFL391 | AMS → AMS | Jun 18, 08:45 UTC | Jun 19, 06:39 UTC | 21h 54m |
| 2026-06-17 | TFL368 | - | Jun 17, 09:20 UTC | Jun 18, 04:40 UTC | 19h 20m |
| 2026-06-17 | TFL368 | - | Jun 17, 08:35 UTC | Jun 18, 04:40 UTC | 20h 5m |
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 .