sensors Mode-S transponder
4850A1
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to P4-BFH · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 4850A1
- Octal
- 22050241
- Decimal
- 4,739,233
- Country
- NL
- Tail
- P4-BFH
- Type
- GLEX
- Flights observed
- 40
- Distinct callsigns
- 20
- Country
- NL
- Last broadcast
- 8d ago
Last known position
Country allocation
The ICAO 24-bit address 4850A1 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 |
|---|---|---|---|
| P4BFH | - | 19 | 2026-05-25 |
| BFY748R | - | 2 | 2026-05-06 |
| BFY714P | - | 2 | 2026-05-03 |
| BFY751P | - | 1 | 2026-05-06 |
| BFY747R | - | 1 | 2026-05-06 |
| BFY723R | - | 1 | 2026-04-30 |
| BFY722R | - | 1 | 2026-04-30 |
| BFY713R | - | 1 | 2026-05-03 |
| BFY713P | - | 1 | 2026-05-01 |
| BFY700R | - | 1 | 2026-04-28 |
| BFY700P | - | 1 | 2026-04-28 |
| BFY692R | - | 1 | 2026-04-28 |
| BFY658R | - | 1 | 2026-04-21 |
| BFY649R | - | 1 | 2026-04-21 |
| BFY638P | - | 1 | 2026-04-20 |
| BFY622P | - | 1 | 2026-04-15 |
| BFY617R | - | 1 | 2026-04-16 |
| BFY615R | - | 1 | 2026-04-18 |
| BFY615P | - | 1 | 2026-04-18 |
| BFY579R | - | 1 | 2026-04-13 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-25 | P4BFH | - | May 25, 07:15 UTC | May 25, 07:30 UTC | 15m |
| 2026-05-23 | P4BFH | - | May 23, 11:00 UTC | May 23, 21:30 UTC | 10h 31m |
| 2026-05-19 | P4BFH | - | May 19, 17:50 UTC | May 19, 18:25 UTC | 35m |
| 2026-05-19 | P4BFH | - | May 19, 07:10 UTC | May 19, 07:35 UTC | 25m |
| 2026-05-18 | P4BFH | - | May 18, 16:05 UTC | May 18, 22:20 UTC | 6h 14m |
| 2026-05-18 | P4BFH | - | May 18, 13:15 UTC | May 18, 14:55 UTC | 1h 40m |
| 2026-05-18 | P4BFH | - | May 18, 10:00 UTC | May 18, 11:55 UTC | 1h 55m |
| 2026-05-16 | P4BFH | - | May 16, 08:01 UTC | May 16, 08:41 UTC | 40m |
| 2026-05-16 | P4BFH | - | May 16, 05:05 UTC | May 16, 07:11 UTC | 2h 6m |
| 2026-05-15 | P4BFH | - | May 15, 01:30 UTC | May 15, 11:25 UTC | 9h 55m |
| 2026-05-12 | P4BFH | - | May 12, 16:40 UTC | May 13, 12:15 UTC | 19h 35m |
| 2026-05-11 | P4BFH | - | May 11, 19:10 UTC | May 12, 18:15 UTC | 23h 5m |
| 2026-05-10 | P4BFH | - | May 10, 22:20 UTC | May 11, 19:30 UTC | 21h 11m |
| 2026-05-10 | P4BFH | - | May 10, 21:59 UTC | May 11, 19:30 UTC | 21h 31m |
| 2026-05-10 | P4BFH | - | May 10, 16:00 UTC | May 10, 23:44 UTC | 7h 45m |
| 2026-05-09 | P4BFH | - | May 9, 18:20 UTC | May 10, 16:04 UTC | 21h 45m |
| 2026-05-09 | P4BFH | - | May 9, 16:20 UTC | May 10, 16:04 UTC | 23h 45m |
| 2026-05-09 | P4BFH | - | May 9, 16:10 UTC | May 9, 18:25 UTC | 2h 15m |
| 2026-05-09 | P4BFH | - | May 9, 13:55 UTC | May 9, 14:15 UTC | 20m |
| 2026-05-06 | BFY751P | - | May 6, 18:15 UTC | May 7, 04:30 UTC | 10h 15m |
| 2026-05-06 | BFY748R | - | May 6, 08:30 UTC | May 6, 09:15 UTC | 45m |
| 2026-05-06 | BFY748R | - | May 6, 08:01 UTC | May 6, 08:25 UTC | 25m |
| 2026-05-06 | BFY747R | - | May 6, 06:55 UTC | May 6, 07:15 UTC | 20m |
| 2026-05-03 | BFY714P | - | May 3, 22:49 UTC | May 3, 23:00 UTC | 10m |
| 2026-05-03 | BFY714P | - | May 3, 19:55 UTC | May 3, 20:30 UTC | 35m |
| 2026-05-03 | BFY713R | - | May 3, 05:10 UTC | May 3, 05:40 UTC | 30m |
| 2026-05-01 | BFY713P | - | May 1, 17:00 UTC | May 2, 01:45 UTC | 8h 45m |
| 2026-04-30 | BFY723R | - | Apr 30, 18:10 UTC | Apr 30, 18:35 UTC | 25m |
| 2026-04-30 | BFY722R | - | Apr 30, 06:40 UTC | Apr 30, 07:05 UTC | 25m |
| 2026-04-28 | BFY700R | - | Apr 28, 15:20 UTC | Apr 28, 15:40 UTC | 20m |
| 2026-04-28 | BFY700P | - | Apr 28, 09:50 UTC | Apr 28, 10:20 UTC | 30m |
| 2026-04-28 | BFY692R | - | Apr 28, 07:45 UTC | Apr 28, 08:10 UTC | 25m |
| 2026-04-21 | BFY649R | - | Apr 21, 15:40 UTC | Apr 21, 16:01 UTC | 20m |
| 2026-04-21 | BFY658R | - | Apr 21, 04:35 UTC | Apr 21, 04:50 UTC | 15m |
| 2026-04-20 | BFY638P | - | Apr 20, 11:15 UTC | Apr 20, 16:10 UTC | 4h 55m |
| 2026-04-18 | BFY615R | - | Apr 18, 21:30 UTC | Apr 18, 21:50 UTC | 20m |
| 2026-04-18 | BFY615P | - | Apr 18, 07:30 UTC | Apr 18, 10:05 UTC | 2h 35m |
| 2026-04-16 | BFY617R | - | Apr 16, 11:20 UTC | Apr 16, 11:54 UTC | 35m |
| 2026-04-15 | BFY622P | - | Apr 15, 11:05 UTC | Apr 15, 11:20 UTC | 15m |
| 2026-04-13 | BFY579R | - | Apr 13, 18:10 UTC | Apr 13, 19:30 UTC | 1h 20m |
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-BFH page for operator, model, and routing details .