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