sensors Mode-S transponder
4866C1
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-TFJ · BOEING 787-8 Dreamliner
- Hex
- 4866C1
- Octal
- 22063301
- Decimal
- 4,744,897
- Country
- NL
- Tail
- PH-TFJ
- Type
- B788
- Flights observed
- 89
- Distinct callsigns
- 17
- Country
- NL
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 4866C1 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TFL361 | Arkefly | 17 | 2026-05-29 |
| TFL368 | Arkefly | 16 | 2026-05-31 |
| TFL367 | Arkefly | 11 | 2026-05-31 |
| TFL365 | Arkefly | 11 | 2026-06-01 |
| TFL393 | Arkefly | 9 | 2026-04-28 |
| TFL511 | Arkefly | 5 | 2026-06-02 |
| TFL757 | Arkefly | 4 | 2026-05-07 |
| TFL391 | Arkefly | 3 | 2026-04-23 |
| TFL822 | Arkefly | 2 | 2026-05-23 |
| TFL821 | Arkefly | 2 | 2026-05-23 |
| TFL372 | Arkefly | 2 | 2026-05-07 |
| TFL371 | Arkefly | 2 | 2026-05-07 |
| TFL5YW | - | 1 | 2026-05-04 |
| TFL3DY | Arkefly | 1 | 2026-05-08 |
| TFL3BM | - | 1 | 2026-05-04 |
| TFL27G | - | 1 | 2026-05-08 |
| TFL064P | Arkefly | 1 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | TFL511 | CUN → AMS | Jun 2, 10:15 UTC | Jun 2, 19:05 UTC | 8h 50m |
| 2026-06-01 | TFL365 | BON → AMS | Jun 1, 10:20 UTC | Jun 2, 06:10 UTC | 19h 50m |
| 2026-06-01 | TFL365 | BON → AMS | Jun 1, 09:10 UTC | Jun 2, 06:10 UTC | 21h 0m |
| 2026-05-31 | TFL368 | CUR → AMS | May 31, 10:20 UTC | Jun 1, 05:00 UTC | 18h 40m |
| 2026-05-31 | TFL367 | AMS → CUR | May 31, 09:00 UTC | Jun 1, 05:00 UTC | 20h 0m |
| 2026-05-30 | TFL367 | AMS → CUR | May 30, 09:55 UTC | May 30, 22:55 UTC | 13h 0m |
| 2026-05-29 | TFL361 | AUA → AMS | May 29, 23:30 UTC | May 30, 07:10 UTC | 7h 40m |
| 2026-05-29 | TFL361 | AUA → AMS | May 29, 22:45 UTC | May 29, 22:55 UTC | 10m |
| 2026-05-29 | TFL361 | AUA → AMS | May 29, 21:05 UTC | May 29, 21:20 UTC | 15m |
| 2026-05-29 | TFL361 | AUA → AMS | May 29, 09:10 UTC | May 29, 17:45 UTC | 8h 35m |
| 2026-05-28 | TFL367 | AMS → CUR | May 28, 10:20 UTC | May 29, 05:45 UTC | 19h 25m |
| 2026-05-28 | TFL367 | AMS → CUR | May 28, 09:45 UTC | May 29, 05:45 UTC | 20h 0m |
| 2026-05-27 | TFL511 | CUN → AMS | May 27, 00:55 UTC | May 27, 10:15 UTC | 9h 21m |
| 2026-05-26 | TFL511 | CUN → AMS | May 26, 10:20 UTC | May 26, 22:54 UTC | 12h 35m |
| 2026-05-25 | TFL365 | BON → AMS | May 25, 16:45 UTC | May 26, 06:39 UTC | 13h 55m |
| 2026-05-25 | TFL365 | BON → AMS | May 25, 10:20 UTC | May 26, 06:39 UTC | 20h 19m |
| 2026-05-25 | TFL365 | BON → AMS | May 25, 08:55 UTC | May 26, 06:39 UTC | 21h 44m |
| 2026-05-25 | TFL368 | CUR → AMS | May 25, 04:20 UTC | May 25, 06:05 UTC | 1h 45m |
| 2026-05-24 | TFL367 | AMS → CUR | May 24, 08:35 UTC | May 25, 06:05 UTC | 21h 30m |
| 2026-05-23 | TFL822 | CUN → AMS | May 23, 19:50 UTC | May 24, 04:55 UTC | 9h 5m |
| 2026-05-23 | TFL821 | AMS → CUN | May 23, 07:10 UTC | May 23, 17:25 UTC | 10h 15m |
| 2026-05-20 | TFL511 | CUN → AMS | May 20, 01:05 UTC | May 20, 10:20 UTC | 9h 16m |
| 2026-05-19 | TFL511 | CUN → AMS | May 19, 10:05 UTC | May 19, 22:30 UTC | 12h 25m |
| 2026-05-18 | TFL365 | BON → AMS | May 18, 17:40 UTC | May 19, 06:55 UTC | 13h 14m |
| 2026-05-18 | TFL365 | BON → AMS | May 18, 10:25 UTC | May 19, 06:55 UTC | 20h 29m |
| 2026-05-18 | TFL365 | BON → AMS | May 18, 09:00 UTC | May 19, 06:55 UTC | 21h 54m |
| 2026-05-17 | TFL368 | CUR → AMS | May 17, 16:40 UTC | May 18, 04:40 UTC | 12h 0m |
| 2026-05-17 | TFL368 | CUR → AMS | May 17, 08:25 UTC | May 18, 04:40 UTC | 20h 15m |
| 2026-05-16 | TFL368 | CUR → AMS | May 16, 10:20 UTC | May 17, 05:35 UTC | 19h 15m |
| 2026-05-16 | TFL368 | CUR → AMS | May 16, 09:25 UTC | May 17, 05:35 UTC | 20h 10m |
| 2026-05-15 | TFL361 | AUA → AMS | May 15, 22:05 UTC | May 16, 06:41 UTC | 8h 36m |
| 2026-05-15 | TFL361 | AUA → AMS | May 15, 20:15 UTC | May 15, 20:35 UTC | 20m |
| 2026-05-15 | TFL361 | AUA → AMS | May 15, 09:25 UTC | May 15, 17:15 UTC | 7h 49m |
| 2026-05-14 | TFL368 | CUR → AMS | May 14, 18:10 UTC | May 15, 06:30 UTC | 12h 20m |
| 2026-05-14 | TFL368 | CUR → AMS | May 14, 10:20 UTC | May 15, 06:30 UTC | 20h 10m |
| 2026-05-14 | TFL368 | CUR → AMS | May 14, 10:10 UTC | May 15, 06:30 UTC | 20h 20m |
| 2026-05-12 | TFL822 | CUN → AMS | May 12, 06:25 UTC | May 12, 14:55 UTC | 8h 30m |
| 2026-05-09 | TFL821 | AMS → CUN | May 9, 07:50 UTC | May 9, 17:25 UTC | 9h 35m |
| 2026-05-08 | TFL3DY | ACE → AMS | May 8, 18:25 UTC | May 8, 21:50 UTC | 3h 25m |
| 2026-05-08 | TFL27G | AMS → AYT | May 8, 13:40 UTC | May 8, 16:50 UTC | 3h 10m |
| 2026-05-07 | TFL372 | CUR → AMS | May 7, 16:20 UTC | May 8, 11:30 UTC | 19h 9m |
| 2026-05-07 | TFL371 | AMS → CUR | May 7, 15:45 UTC | May 8, 11:30 UTC | 19h 44m |
| 2026-05-07 | TFL757 | CUR → AMS | May 7, 05:35 UTC | May 7, 13:15 UTC | 7h 40m |
| 2026-05-06 | TFL757 | CUR → AMS | May 6, 11:45 UTC | May 6, 23:25 UTC | 11h 39m |
| 2026-05-05 | TFL368 | CUR → AMS | May 5, 12:20 UTC | May 6, 08:10 UTC | 19h 50m |
| 2026-05-04 | TFL5YW | - | May 4, 18:20 UTC | May 4, 21:45 UTC | 3h 26m |
| 2026-05-04 | TFL3BM | - | May 4, 12:40 UTC | May 4, 16:30 UTC | 3h 50m |
| 2026-05-03 | TFL757 | CUR → AMS | May 3, 23:30 UTC | May 4, 07:55 UTC | 8h 25m |
| 2026-05-03 | TFL757 | CUR → AMS | May 3, 09:05 UTC | May 3, 17:05 UTC | 8h 0m |
| 2026-05-02 | TFL368 | CUR → AMS | May 2, 10:20 UTC | May 3, 05:50 UTC | 19h 29m |
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-TFJ page for operator, model, and routing details .