sensors Mode-S transponder
48506C
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-TFL · BOEING 787-8 Dreamliner
- Hex
- 48506C
- Octal
- 22050154
- Decimal
- 4,739,180
- Country
- NL
- Tail
- PH-TFL
- Type
- B788
- Flights observed
- 102
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 48506C 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 | Arkefly | 13 | 2026-04-26 |
| TFL368 | Arkefly | 13 | 2026-05-10 |
| TFL361 | - | 11 | 2026-06-26 |
| TFL391 | - | 10 | 2026-06-25 |
| TFL381 | Arkefly | 10 | 2026-04-21 |
| TFL511 | - | 6 | 2026-07-02 |
| TFL393 | Arkefly | 6 | 2026-05-05 |
| TFL367 | Arkefly | 5 | 2026-05-07 |
| TFL365 | Arkefly | 4 | 2026-05-11 |
| TFL372 | Arkefly | 3 | 2026-05-03 |
| TFL822 | - | 2 | 2026-07-12 |
| TFL821 | - | 2 | 2026-07-11 |
| TFL5YW | - | 2 | 2026-07-02 |
| TFL4368 | - | 2 | 2026-06-30 |
| TFL3BM | - | 2 | 2026-07-02 |
| TFL7GX | - | 1 | 2026-04-18 |
| TFL5EH | - | 1 | 2026-07-03 |
| TFL4ND | - | 1 | 2026-07-03 |
| TFL4BC | - | 1 | 2026-04-18 |
| TFL4367 | - | 1 | 2026-06-29 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-12 | TFL067P | AMS → BRU | Jul 12, 15:01 UTC | Jul 12, 15:25 UTC | 25m |
| 2026-07-12 | TFL822 | CUN → AMS | Jul 12, 03:30 UTC | Jul 12, 12:35 UTC | 9h 5m |
| 2026-07-11 | TFL821 | AMS → CUN | Jul 11, 15:30 UTC | Jul 12, 01:20 UTC | 9h 50m |
| 2026-07-11 | TFL3DB | - | Jul 11, 09:05 UTC | Jul 11, 12:35 UTC | 3h 30m |
| 2026-07-11 | TFL3NA | - | Jul 11, 04:30 UTC | Jul 11, 07:40 UTC | 3h 10m |
| 2026-07-03 | TFL4ND | - | Jul 3, 10:30 UTC | Jul 3, 14:25 UTC | 3h 55m |
| 2026-07-03 | TFL5EH | - | Jul 3, 04:45 UTC | Jul 3, 08:45 UTC | 4h 0m |
| 2026-07-02 | TFL5YW | - | Jul 2, 19:40 UTC | Jul 2, 23:30 UTC | 3h 50m |
| 2026-07-02 | TFL3BM | - | Jul 2, 14:00 UTC | Jul 2, 18:10 UTC | 4h 10m |
| 2026-07-02 | TFL511 | - | Jul 2, 00:55 UTC | Jul 2, 10:00 UTC | 9h 5m |
| 2026-07-01 | TFL511 | - | Jul 1, 10:10 UTC | Jul 1, 22:55 UTC | 12h 45m |
| 2026-06-30 | TFL4368 | - | Jun 30, 15:05 UTC | Jun 30, 22:50 UTC | 7h 45m |
| 2026-06-29 | TFL4368 | - | Jun 29, 23:14 UTC | Jun 30, 22:50 UTC | 23h 36m |
| 2026-06-29 | TFL4367 | - | Jun 29, 15:04 UTC | Jun 29, 23:25 UTC | 8h 20m |
| 2026-06-29 | TFL822 | CUN → AMS | Jun 29, 03:20 UTC | Jun 29, 12:09 UTC | 8h 50m |
| 2026-06-28 | TFL821 | AMS → CUN | Jun 28, 14:50 UTC | Jun 29, 00:49 UTC | 10h 0m |
| 2026-06-26 | TFL361 | - | Jun 26, 22:49 UTC | Jun 27, 07:39 UTC | 8h 50m |
| 2026-06-26 | TFL361 | - | Jun 26, 20:50 UTC | Jun 26, 21:10 UTC | 20m |
| 2026-06-26 | TFL361 | - | Jun 26, 09:24 UTC | Jun 26, 17:54 UTC | 8h 30m |
| 2026-06-25 | TFL391 | - | Jun 25, 16:55 UTC | Jun 26, 06:50 UTC | 13h 55m |
| 2026-06-25 | TFL391 | - | Jun 25, 09:10 UTC | Jun 26, 06:50 UTC | 21h 40m |
| 2026-06-24 | TFL068P | TPE → AMS | Jun 24, 11:24 UTC | Jun 25, 01:30 UTC | 14h 5m |
| 2026-05-13 | TFL061P | AMS → ARN | May 13, 14:05 UTC | May 14, 03:20 UTC | 13h 15m |
| 2026-05-13 | TFL511 | CUN → AMS | May 13, 01:50 UTC | May 13, 10:50 UTC | 9h 0m |
| 2026-05-12 | TFL511 | CUN → AMS | May 12, 11:35 UTC | May 12, 13:00 UTC | 1h 25m |
| 2026-05-11 | TFL365 | BON → AMS | May 11, 16:55 UTC | May 12, 06:50 UTC | 13h 56m |
| 2026-05-11 | TFL365 | BON → AMS | May 11, 09:20 UTC | May 12, 06:50 UTC | 21h 30m |
| 2026-05-10 | TFL368 | CUR → AMS | May 10, 16:14 UTC | May 11, 05:10 UTC | 12h 55m |
| 2026-05-10 | TFL368 | CUR → AMS | May 10, 09:05 UTC | May 11, 05:10 UTC | 20h 5m |
| 2026-05-10 | TFL368 | CUR → AMS | May 10, 08:30 UTC | May 11, 05:10 UTC | 20h 40m |
| 2026-05-09 | TFL368 | CUR → AMS | May 9, 11:05 UTC | May 10, 06:04 UTC | 19h 0m |
| 2026-05-09 | TFL368 | CUR → AMS | May 9, 09:40 UTC | May 10, 06:04 UTC | 20h 25m |
| 2026-05-08 | TFL361 | AUA → AMS | May 8, 22:55 UTC | May 9, 07:15 UTC | 8h 20m |
| 2026-05-08 | TFL361 | AUA → AMS | May 8, 22:10 UTC | May 8, 22:20 UTC | 10m |
| 2026-05-08 | TFL361 | AUA → AMS | May 8, 20:20 UTC | May 8, 20:35 UTC | 15m |
| 2026-05-08 | TFL361 | AUA → AMS | May 8, 09:04 UTC | May 8, 17:10 UTC | 8h 5m |
| 2026-05-07 | TFL368 | CUR → AMS | May 7, 11:05 UTC | May 8, 05:24 UTC | 18h 20m |
| 2026-05-07 | TFL367 | AMS → CUR | May 7, 09:25 UTC | May 8, 05:24 UTC | 20h 0m |
| 2026-05-06 | TFL368 | CUR → AMS | May 6, 17:55 UTC | May 7, 05:35 UTC | 11h 40m |
| 2026-05-06 | TFL368 | CUR → AMS | May 6, 09:25 UTC | May 7, 05:35 UTC | 20h 9m |
| 2026-05-05 | TFL393 | CUR → AMS | May 5, 15:55 UTC | May 6, 05:30 UTC | 13h 35m |
| 2026-05-05 | TFL393 | CUR → AMS | May 5, 09:05 UTC | May 6, 05:30 UTC | 20h 25m |
| 2026-05-05 | TFL393 | CUR → AMS | May 5, 07:50 UTC | May 6, 05:30 UTC | 21h 40m |
| 2026-05-03 | TFL372 | CUR → AMS | May 3, 20:30 UTC | May 4, 09:10 UTC | 12h 40m |
| 2026-05-03 | TFL372 | CUR → AMS | May 3, 13:05 UTC | May 4, 09:10 UTC | 20h 5m |
| 2026-05-03 | TFL372 | CUR → AMS | May 3, 12:30 UTC | May 4, 09:10 UTC | 20h 40m |
| 2026-05-02 | TFL365 | BON → AMS | May 2, 18:55 UTC | May 3, 08:55 UTC | 13h 59m |
| 2026-05-02 | TFL365 | BON → AMS | May 2, 11:05 UTC | May 3, 08:55 UTC | 21h 49m |
| 2026-05-01 | TFL393 | CUR → AMS | May 1, 18:20 UTC | May 2, 08:10 UTC | 13h 50m |
| 2026-05-01 | TFL393 | CUR → AMS | May 1, 11:05 UTC | May 2, 08:10 UTC | 21h 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-TFL page for operator, model, and routing details .