sensors Mode-S transponder
485171
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to PH-TLP · DASSAULT Falcon 7X
- Hex
- 485171
- Octal
- 22050561
- Decimal
- 4,739,441
- Country
- NL
- Tail
- PH-TLP
- Type
- FA7X
- Flights observed
- 61
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 23h ago
Last known position
Country allocation
The ICAO 24-bit address 485171 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 |
|---|---|---|---|
| FYG31P | - | 6 | 2026-07-16 |
| FYG121 | - | 5 | 2026-06-28 |
| FYG71P | - | 4 | 2026-07-18 |
| FYG82P | - | 3 | 2026-07-11 |
| FYG81P | - | 3 | 2026-07-10 |
| FYG72P | - | 3 | 2026-07-04 |
| FYG62P | - | 3 | 2026-07-18 |
| FYG52P | - | 3 | 2026-07-03 |
| FYG42P | Flying Service | 3 | 2026-06-23 |
| FYG32P | - | 3 | 2026-06-10 |
| FYG75P | - | 2 | 2026-07-10 |
| FYG51P | - | 2 | 2026-06-26 |
| FYG45P | - | 2 | 2026-04-21 |
| FYG43P | - | 2 | 2026-06-26 |
| FYG41P | - | 2 | 2026-06-19 |
| FYG85P | - | 1 | 2026-07-01 |
| FYG79P | - | 1 | 2026-07-15 |
| FYG78P | - | 1 | 2026-07-15 |
| FYG77P | - | 1 | 2026-07-15 |
| FYG74P | - | 1 | 2026-07-10 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | FYG71P | FAO → AMS | Jul 18, 13:35 UTC | Jul 18, 15:55 UTC | 2h 20m |
| 2026-07-18 | FYG62P | - | Jul 18, 11:05 UTC | Jul 18, 11:55 UTC | 50m |
| 2026-07-16 | FYG31P | - | Jul 16, 15:55 UTC | Jul 16, 18:05 UTC | 2h 10m |
| 2026-07-15 | FYG79P | - | Jul 15, 15:40 UTC | Jul 15, 16:00 UTC | 20m |
| 2026-07-15 | FYG78P | - | Jul 15, 12:40 UTC | Jul 15, 14:50 UTC | 2h 10m |
| 2026-07-15 | FYG77P | - | Jul 15, 10:45 UTC | Jul 15, 10:55 UTC | 10m |
| 2026-07-11 | FYG33P | - | Jul 11, 14:40 UTC | Jul 11, 16:45 UTC | 2h 5m |
| 2026-07-11 | FYG82P | BRN → LCA | Jul 11, 10:20 UTC | Jul 11, 13:25 UTC | 3h 5m |
| 2026-07-10 | FYG81P | - | Jul 10, 13:10 UTC | Jul 10, 14:40 UTC | 1h 30m |
| 2026-07-10 | FYG75P | - | Jul 10, 09:20 UTC | Jul 10, 10:55 UTC | 1h 35m |
| 2026-07-10 | FYG74P | - | Jul 10, 06:35 UTC | Jul 10, 07:35 UTC | 1h 0m |
| 2026-07-04 | FYG73P | - | Jul 4, 10:40 UTC | Jul 4, 11:35 UTC | 55m |
| 2026-07-04 | FYG72P | ANR → CPH | Jul 4, 08:15 UTC | Jul 4, 09:20 UTC | 1h 5m |
| 2026-07-03 | FYG52P | AMS → ANR | Jul 3, 12:50 UTC | Jul 3, 13:10 UTC | 20m |
| 2026-07-01 | FYG62P | IBZ → AMS | Jul 1, 14:35 UTC | Jul 1, 16:45 UTC | 2h 10m |
| 2026-07-01 | FYG71P | AMS → IBZ | Jul 1, 11:25 UTC | Jul 1, 13:25 UTC | 2h 0m |
| 2026-07-01 | FYG85P | BRU → AMS | Jul 1, 08:25 UTC | Jul 1, 08:55 UTC | 30m |
| 2026-06-29 | FYG122 | - | Jun 29, 20:09 UTC | Jun 30, 04:50 UTC | 8h 41m |
| 2026-06-28 | FYG75P | TEB → FTW | Jun 28, 21:10 UTC | Jun 29, 00:00 UTC | 2h 50m |
| 2026-06-28 | FYG121 | - | Jun 28, 12:09 UTC | Jun 28, 19:34 UTC | 7h 25m |
| 2026-06-27 | FYG44P | - | Jun 27, 15:05 UTC | Jun 27, 15:34 UTC | 30m |
| 2026-06-27 | FYG72P | FAO → AMS | Jun 27, 10:50 UTC | Jun 27, 13:09 UTC | 2h 20m |
| 2026-06-26 | FYG43P | IBZ → FAO | Jun 26, 18:20 UTC | Jun 26, 19:35 UTC | 1h 15m |
| 2026-06-26 | FYG82P | VIE → IBZ | Jun 26, 14:39 UTC | Jun 26, 16:49 UTC | 2h 10m |
| 2026-06-26 | FYG51P | AMS → VIE | Jun 26, 11:34 UTC | Jun 26, 12:55 UTC | 1h 20m |
| 2026-06-23 | FYG42P | LIN → AMS | Jun 23, 09:54 UTC | Jun 23, 11:59 UTC | 2h 5m |
| 2026-06-22 | FYG71P | - | Jun 22, 11:19 UTC | Jun 22, 13:10 UTC | 1h 50m |
| 2026-06-19 | FYG82P | - | Jun 19, 11:14 UTC | Jun 19, 13:09 UTC | 1h 55m |
| 2026-06-19 | FYG41P | - | Jun 19, 07:39 UTC | Jun 19, 09:44 UTC | 2h 5m |
| 2026-06-11 | FYG62P | FAO → AMS | Jun 11, 14:55 UTC | Jun 11, 17:35 UTC | 2h 40m |
| 2026-06-11 | FYG71P | - | Jun 11, 11:25 UTC | Jun 11, 13:55 UTC | 2h 30m |
| 2026-06-10 | FYG32P | - | Jun 10, 11:40 UTC | Jun 10, 14:35 UTC | 2h 55m |
| 2026-06-10 | FYG31P | - | Jun 10, 06:20 UTC | Jun 10, 09:15 UTC | 2h 55m |
| 2026-06-09 | FYG31P | - | Jun 9, 06:40 UTC | Jun 9, 14:35 UTC | 7h 55m |
| 2026-06-08 | FYG42P | LIN → AMS | Jun 8, 12:15 UTC | Jun 8, 15:04 UTC | 2h 50m |
| 2026-06-04 | FYG31P | - | Jun 4, 10:35 UTC | Jun 4, 13:35 UTC | 3h 0m |
| 2026-06-03 | FYG32P | - | Jun 3, 10:10 UTC | Jun 3, 17:25 UTC | 7h 15m |
| 2026-06-02 | FYG32P | - | Jun 2, 12:35 UTC | Jun 2, 15:50 UTC | 3h 15m |
| 2026-06-02 | FYG31P | - | Jun 2, 08:00 UTC | Jun 2, 10:45 UTC | 2h 45m |
| 2026-05-22 | FYG64P | - | May 22, 06:55 UTC | May 22, 07:45 UTC | 50m |
| 2026-05-21 | FYG113 | - | May 21, 23:45 UTC | May 22, 06:10 UTC | 6h 25m |
| 2026-05-19 | FYG112 | - | May 19, 13:50 UTC | May 19, 19:45 UTC | 5h 55m |
| 2026-05-19 | FYG41P | - | May 19, 11:05 UTC | May 19, 12:25 UTC | 1h 20m |
| 2026-05-16 | FYG72P | - | May 16, 10:31 UTC | May 16, 12:35 UTC | 2h 5m |
| 2026-05-16 | FYG61P | - | May 16, 07:05 UTC | May 16, 08:51 UTC | 1h 45m |
| 2026-05-03 | FYG43P | - | May 3, 18:00 UTC | May 3, 18:20 UTC | 20m |
| 2026-05-03 | FYG42P | LIN → AMS | May 3, 15:55 UTC | May 3, 17:05 UTC | 1h 10m |
| 2026-05-01 | FYG31P | - | May 1, 08:05 UTC | May 1, 09:10 UTC | 1h 5m |
| 2026-04-28 | FYG52P | FAO → AMS | Apr 28, 14:15 UTC | Apr 28, 16:40 UTC | 2h 25m |
| 2026-04-23 | FYG51P | - | Apr 23, 08:25 UTC | Apr 23, 11:01 UTC | 2h 35m |
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-TLP page for operator, model, and routing details .