sensors Mode-S transponder
48506B
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-TFK · BOEING 787-8 Dreamliner
- Hex
- 48506B
- Octal
- 22050153
- Decimal
- 4,739,179
- Country
- NL
- Tail
- PH-TFK
- Type
- B788
- Flights observed
- 109
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 48506B 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 | Arkefly | 17 | 2026-05-19 |
| TFL757 | Arkefly | 11 | 2026-06-01 |
| TFL372 | Arkefly | 11 | 2026-05-28 |
| TFL368 | Arkefly | 11 | 2026-05-27 |
| TFL381 | Arkefly | 10 | 2026-06-02 |
| TFL367 | Arkefly | 10 | 2026-06-02 |
| TFL365 | Arkefly | 6 | 2026-05-16 |
| TFL822 | Arkefly | 4 | 2026-05-30 |
| TFL821 | Arkefly | 4 | 2026-05-30 |
| TFL391 | Arkefly | 4 | 2026-05-21 |
| TFL371 | Arkefly | 3 | 2026-05-28 |
| TFL361 | Arkefly | 3 | 2026-05-22 |
| TFL97M | Arkefly | 2 | 2026-05-01 |
| TFL7VN | - | 2 | 2026-05-01 |
| TFL70V | Arkefly | 2 | 2026-05-05 |
| TFL3NA | Arkefly | 2 | 2026-05-02 |
| TFL3DB | Arkefly | 2 | 2026-05-02 |
| TFL944F | Arkefly | 1 | 2026-05-07 |
| TFL943F | Arkefly | 1 | 2026-05-06 |
| TFL9421 | Arkefly | 1 | 2026-05-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | TFL367 | AMS → CUR | Jun 2, 13:30 UTC | Jun 2, 17:10 UTC | 3h 40m |
| 2026-06-02 | TFL381 | CUR → AMS | Jun 2, 03:25 UTC | Jun 2, 10:55 UTC | 7h 30m |
| 2026-06-02 | TFL381 | CUR → AMS | Jun 2, 00:10 UTC | Jun 2, 00:20 UTC | 10m |
| 2026-06-01 | TFL381 | CUR → AMS | Jun 1, 13:15 UTC | Jun 1, 23:00 UTC | 9h 45m |
| 2026-06-01 | TFL757 | CUR → AMS | Jun 1, 03:00 UTC | Jun 1, 10:30 UTC | 7h 30m |
| 2026-05-31 | TFL757 | CUR → AMS | May 31, 09:20 UTC | May 31, 18:10 UTC | 8h 50m |
| 2026-05-30 | TFL822 | CUN → AMS | May 30, 20:25 UTC | May 30, 21:35 UTC | 1h 10m |
| 2026-05-30 | TFL821 | AMS → CUN | May 30, 07:05 UTC | May 30, 17:00 UTC | 9h 55m |
| 2026-05-28 | TFL372 | CUR → AMS | May 28, 14:50 UTC | May 29, 10:20 UTC | 19h 30m |
| 2026-05-28 | TFL371 | AMS → CUR | May 28, 13:25 UTC | May 29, 10:20 UTC | 20h 55m |
| 2026-05-27 | TFL757 | CUR → AMS | May 27, 19:45 UTC | May 28, 09:50 UTC | 14h 5m |
| 2026-05-27 | TFL757 | CUR → AMS | May 27, 12:50 UTC | May 28, 09:50 UTC | 21h 0m |
| 2026-05-27 | TFL757 | CUR → AMS | May 27, 11:50 UTC | May 28, 09:50 UTC | 22h 0m |
| 2026-05-27 | TFL368 | CUR → AMS | May 27, 00:49 UTC | May 27, 08:50 UTC | 8h 1m |
| 2026-05-26 | TFL367 | AMS → CUR | May 26, 12:30 UTC | May 26, 21:40 UTC | 9h 10m |
| 2026-05-26 | TFL381 | CUR → AMS | May 26, 01:05 UTC | May 26, 08:59 UTC | 7h 55m |
| 2026-05-25 | TFL381 | CUR → AMS | May 25, 21:49 UTC | May 25, 22:00 UTC | 10m |
| 2026-05-25 | TFL381 | CUR → AMS | May 25, 20:09 UTC | May 25, 20:30 UTC | 20m |
| 2026-05-25 | TFL381 | CUR → AMS | May 25, 11:00 UTC | May 25, 19:35 UTC | 8h 34m |
| 2026-05-24 | TFL757 | CUR → AMS | May 24, 17:45 UTC | May 25, 08:10 UTC | 14h 25m |
| 2026-05-24 | TFL757 | CUR → AMS | May 24, 10:50 UTC | May 25, 08:10 UTC | 21h 20m |
| 2026-05-24 | TFL757 | CUR → AMS | May 24, 09:35 UTC | May 25, 08:10 UTC | 22h 35m |
| 2026-05-23 | TFL368 | CUR → AMS | May 23, 10:50 UTC | May 24, 06:45 UTC | 19h 55m |
| 2026-05-22 | TFL361 | AUA → AMS | May 22, 23:25 UTC | May 23, 07:55 UTC | 8h 29m |
| 2026-05-22 | TFL361 | AUA → AMS | May 22, 21:10 UTC | May 22, 21:35 UTC | 25m |
| 2026-05-22 | TFL361 | AUA → AMS | May 22, 09:35 UTC | May 22, 18:05 UTC | 8h 30m |
| 2026-05-21 | TFL391 | CUR → AMS | May 21, 17:00 UTC | May 22, 06:35 UTC | 13h 35m |
| 2026-05-21 | TFL391 | CUR → AMS | May 21, 08:50 UTC | May 22, 06:35 UTC | 21h 45m |
| 2026-05-20 | TFL368 | CUR → AMS | May 20, 16:25 UTC | May 21, 05:50 UTC | 13h 25m |
| 2026-05-20 | TFL367 | AMS → CUR | May 20, 08:50 UTC | May 21, 05:50 UTC | 21h 0m |
| 2026-05-20 | TFL367 | AMS → CUR | May 20, 08:25 UTC | May 21, 05:50 UTC | 21h 25m |
| 2026-05-19 | TFL393 | CUR → AMS | May 19, 14:20 UTC | May 20, 04:00 UTC | 13h 40m |
| 2026-05-19 | TFL393 | CUR → AMS | May 19, 06:50 UTC | May 20, 04:00 UTC | 21h 10m |
| 2026-05-19 | TFL393 | CUR → AMS | May 19, 06:25 UTC | May 20, 04:00 UTC | 21h 35m |
| 2026-05-17 | TFL372 | CUR → AMS | May 17, 12:50 UTC | May 18, 08:45 UTC | 19h 55m |
| 2026-05-17 | TFL372 | CUR → AMS | May 17, 12:25 UTC | May 18, 08:45 UTC | 20h 20m |
| 2026-05-16 | TFL365 | BON → AMS | May 16, 18:55 UTC | May 17, 08:10 UTC | 13h 15m |
| 2026-05-16 | TFL365 | BON → AMS | May 16, 10:55 UTC | May 17, 08:10 UTC | 21h 15m |
| 2026-05-15 | TFL393 | CUR → AMS | May 15, 18:00 UTC | May 16, 07:55 UTC | 13h 56m |
| 2026-05-15 | TFL393 | CUR → AMS | May 15, 10:50 UTC | May 16, 07:55 UTC | 21h 5m |
| 2026-05-15 | TFL393 | CUR → AMS | May 15, 10:10 UTC | May 16, 07:55 UTC | 21h 45m |
| 2026-05-14 | TFL391 | CUR → AMS | May 14, 16:55 UTC | May 15, 07:00 UTC | 14h 5m |
| 2026-05-14 | TFL391 | CUR → AMS | May 14, 08:55 UTC | May 15, 07:00 UTC | 22h 5m |
| 2026-05-13 | TFL368 | CUR → AMS | May 13, 16:45 UTC | May 14, 04:50 UTC | 12h 5m |
| 2026-05-13 | TFL368 | CUR → AMS | May 13, 08:50 UTC | May 14, 04:50 UTC | 20h 0m |
| 2026-05-12 | TFL393 | CUR → AMS | May 12, 14:35 UTC | May 13, 05:00 UTC | 14h 25m |
| 2026-05-12 | TFL393 | CUR → AMS | May 12, 06:50 UTC | May 13, 05:00 UTC | 22h 10m |
| 2026-05-12 | TFL393 | CUR → AMS | May 12, 06:40 UTC | May 13, 04:45 UTC | 22h 5m |
| 2026-05-10 | TFL372 | CUR → AMS | May 10, 22:05 UTC | May 11, 10:55 UTC | 12h 50m |
| 2026-05-10 | TFL372 | CUR → AMS | May 10, 14:49 UTC | May 11, 10:55 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-TFK page for operator, model, and routing details .