sensors Mode-S transponder
48412F
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to P4-BFX · GULFSTREAM 4
- Hex
- 48412F
- Octal
- 22040457
- Decimal
- 4,735,279
- Country
- NL
- Tail
- P4-BFX
- Type
- GLF4
- Flights observed
- 45
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 48412F 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 |
|---|---|---|---|
| P4BFX | - | 9 | 2026-05-28 |
| BFY624P | - | 3 | 2026-04-17 |
| BFY556P | - | 3 | 2026-04-14 |
| BFY692R | - | 2 | 2026-04-29 |
| BFY690R | - | 2 | 2026-04-26 |
| BFY690P | - | 2 | 2026-04-26 |
| BFY633P | - | 2 | 2026-04-19 |
| BFY625R | - | 2 | 2026-04-21 |
| BFY621R | - | 2 | 2026-04-16 |
| BFY614R | - | 2 | 2026-04-17 |
| BFY554R | - | 2 | 2026-04-14 |
| BFY743P | - | 1 | 2026-05-05 |
| BFY724R | - | 1 | 2026-05-02 |
| BFY721R | - | 1 | 2026-05-02 |
| BFY720P | - | 1 | 2026-05-01 |
| BFY693R | - | 1 | 2026-04-30 |
| BFY692P | - | 1 | 2026-04-28 |
| BFY678R | - | 1 | 2026-04-24 |
| BFY626R | - | 1 | 2026-04-21 |
| BFY621P | - | 1 | 2026-04-16 |
Recent flights last 45
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | P4BFX | - | May 28, 22:50 UTC | May 28, 23:50 UTC | 1h 0m |
| 2026-05-28 | P4BFX | - | May 28, 19:55 UTC | May 28, 21:50 UTC | 1h 55m |
| 2026-05-28 | P4BFX | - | May 28, 13:45 UTC | May 28, 14:00 UTC | 15m |
| 2026-05-27 | P4BFX | - | May 27, 10:45 UTC | May 27, 17:00 UTC | 6h 15m |
| 2026-05-27 | P4BFX | - | May 27, 08:40 UTC | May 27, 09:25 UTC | 45m |
| 2026-05-25 | P4BFX | - | May 25, 15:40 UTC | May 25, 22:49 UTC | 7h 9m |
| 2026-05-10 | P4BFX | - | May 10, 14:45 UTC | May 10, 21:49 UTC | 7h 5m |
| 2026-05-09 | P4BFX | - | May 9, 02:45 UTC | May 9, 10:00 UTC | 7h 15m |
| 2026-05-06 | P4BFX | - | May 6, 10:20 UTC | May 6, 13:45 UTC | 3h 25m |
| 2026-05-05 | BFY743P | - | May 5, 13:45 UTC | May 5, 13:55 UTC | 10m |
| 2026-05-02 | BFY724R | MAD → LAD | May 2, 23:55 UTC | May 3, 06:40 UTC | 6h 44m |
| 2026-05-02 | BFY721R | - | May 2, 20:35 UTC | May 2, 22:30 UTC | 1h 55m |
| 2026-05-01 | BFY720P | - | May 1, 01:05 UTC | May 1, 09:15 UTC | 8h 10m |
| 2026-04-30 | BFY693R | - | Apr 30, 05:25 UTC | Apr 30, 05:40 UTC | 15m |
| 2026-04-29 | BFY692R | - | Apr 29, 10:35 UTC | Apr 29, 10:50 UTC | 15m |
| 2026-04-28 | BFY692R | - | Apr 28, 16:10 UTC | Apr 28, 16:30 UTC | 20m |
| 2026-04-28 | BFY692P | - | Apr 28, 14:45 UTC | Apr 28, 15:05 UTC | 20m |
| 2026-04-26 | BFY690R | - | Apr 26, 19:45 UTC | Apr 26, 20:40 UTC | 55m |
| 2026-04-26 | BFY690P | - | Apr 26, 17:50 UTC | Apr 26, 18:40 UTC | 50m |
| 2026-04-26 | BFY690P | - | Apr 26, 14:00 UTC | Apr 26, 14:15 UTC | 15m |
| 2026-04-25 | BFY690R | - | Apr 25, 13:35 UTC | Apr 25, 15:40 UTC | 2h 5m |
| 2026-04-24 | BFY678R | - | Apr 24, 01:35 UTC | Apr 24, 09:35 UTC | 8h 0m |
| 2026-04-21 | BFY626R | - | Apr 21, 14:20 UTC | Apr 21, 17:05 UTC | 2h 45m |
| 2026-04-21 | BFY625R | - | Apr 21, 00:35 UTC | Apr 21, 00:55 UTC | 20m |
| 2026-04-20 | BFY625R | - | Apr 20, 19:20 UTC | Apr 20, 21:30 UTC | 2h 10m |
| 2026-04-19 | BFY633P | - | Apr 19, 02:10 UTC | Apr 19, 03:55 UTC | 1h 45m |
| 2026-04-18 | BFY633P | - | Apr 18, 18:50 UTC | Apr 18, 19:00 UTC | 10m |
| 2026-04-18 | BFY614P | - | Apr 18, 08:55 UTC | Apr 18, 16:00 UTC | 7h 5m |
| 2026-04-17 | BFY614R | - | Apr 17, 21:30 UTC | Apr 17, 22:40 UTC | 1h 10m |
| 2026-04-17 | BFY614R | - | Apr 17, 15:20 UTC | Apr 17, 15:50 UTC | 30m |
| 2026-04-17 | BFY624P | - | Apr 17, 14:15 UTC | Apr 17, 14:30 UTC | 15m |
| 2026-04-17 | BFY624P | - | Apr 17, 07:20 UTC | Apr 17, 08:10 UTC | 50m |
| 2026-04-17 | BFY624P | - | Apr 17, 07:05 UTC | Apr 17, 07:15 UTC | 10m |
| 2026-04-16 | BFY621R | - | Apr 16, 19:15 UTC | Apr 16, 19:30 UTC | 15m |
| 2026-04-16 | BFY621R | - | Apr 16, 18:35 UTC | Apr 16, 19:10 UTC | 35m |
| 2026-04-16 | BFY621P | - | Apr 16, 09:24 UTC | Apr 16, 09:39 UTC | 15m |
| 2026-04-15 | BFY613R | - | Apr 15, 17:45 UTC | Apr 15, 18:15 UTC | 30m |
| 2026-04-15 | BFY612R | - | Apr 15, 11:00 UTC | Apr 15, 11:25 UTC | 25m |
| 2026-04-15 | BFY611R | - | Apr 15, 05:00 UTC | Apr 15, 05:25 UTC | 25m |
| 2026-04-14 | BFY556P | - | Apr 14, 07:10 UTC | Apr 14, 08:40 UTC | 1h 30m |
| 2026-04-14 | BFY556R | - | Apr 14, 06:50 UTC | Apr 14, 07:10 UTC | 20m |
| 2026-04-14 | BFY554R | - | Apr 14, 05:15 UTC | Apr 14, 05:30 UTC | 15m |
| 2026-04-13 | BFY554R | - | Apr 13, 22:30 UTC | Apr 13, 23:40 UTC | 1h 10m |
| 2026-04-13 | BFY556P | - | Apr 13, 04:30 UTC | Apr 13, 06:05 UTC | 1h 35m |
| 2026-04-12 | BFY556P | - | Apr 12, 23:55 UTC | Apr 13, 00:05 UTC | 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 P4-BFX page for operator, model, and routing details .