sensors Mode-S transponder
4844B8
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to P4-BFRS · GULFSTREAM 5
- Hex
- 4844B8
- Octal
- 22042270
- Decimal
- 4,736,184
- Country
- NL
- Tail
- P4-BFRS
- Type
- GLF5
- Flights observed
- 42
- Distinct callsigns
- 18
- Country
- NL
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 4844B8 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| P4BFRS | - | 23 | 2026-06-04 |
| BFY663R | - | 2 | 2026-04-29 |
| BFY735R | - | 1 | 2026-05-05 |
| BFY732P | - | 1 | 2026-05-01 |
| BFY719R | - | 1 | 2026-04-30 |
| BFY688R | - | 1 | 2026-05-03 |
| BFY685R | - | 1 | 2026-04-27 |
| BFY664R | - | 1 | 2026-04-30 |
| BFY662R | - | 1 | 2026-04-29 |
| BFY661R | - | 1 | 2026-04-28 |
| BFY658R | - | 1 | 2026-04-21 |
| BFY652R | - | 1 | 2026-04-21 |
| BFY643P | - | 1 | 2026-04-20 |
| BFY642R | - | 1 | 2026-04-20 |
| BFY635R | - | 1 | 2026-04-22 |
| BFY634R | - | 1 | 2026-04-22 |
| BFY581R | - | 1 | 2026-04-19 |
| BFY580R | - | 1 | 2026-04-15 |
Recent flights last 42
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-04 | P4BFRS | - | Jun 4, 13:15 UTC | Jun 4, 13:25 UTC | 10m |
| 2026-06-04 | P4BFRS | - | Jun 4, 10:40 UTC | Jun 4, 11:00 UTC | 20m |
| 2026-06-02 | P4BFRS | - | Jun 2, 16:35 UTC | Jun 2, 17:05 UTC | 30m |
| 2026-05-28 | P4BFRS | - | May 28, 13:00 UTC | May 28, 14:50 UTC | 1h 50m |
| 2026-05-27 | P4BFRS | - | May 27, 10:00 UTC | May 27, 11:35 UTC | 1h 35m |
| 2026-05-27 | P4BFRS | LIN → EMA | May 27, 05:24 UTC | May 27, 07:00 UTC | 1h 36m |
| 2026-05-26 | P4BFRS | - | May 26, 04:00 UTC | May 26, 05:54 UTC | 1h 55m |
| 2026-05-22 | P4BFRS | - | May 22, 11:10 UTC | May 22, 11:20 UTC | 10m |
| 2026-05-22 | P4BFRS | - | May 22, 05:45 UTC | May 22, 06:00 UTC | 15m |
| 2026-05-21 | P4BFRS | - | May 21, 17:55 UTC | May 22, 01:25 UTC | 7h 30m |
| 2026-05-21 | P4BFRS | - | May 21, 15:10 UTC | May 21, 16:30 UTC | 1h 20m |
| 2026-05-16 | P4BFRS | - | May 16, 10:31 UTC | May 16, 21:35 UTC | 11h 4m |
| 2026-05-16 | P4BFRS | - | May 16, 07:25 UTC | May 16, 08:51 UTC | 1h 25m |
| 2026-05-15 | P4BFRS | - | May 15, 08:05 UTC | May 15, 10:55 UTC | 2h 50m |
| 2026-05-14 | P4BFRS | - | May 14, 00:40 UTC | May 14, 01:15 UTC | 35m |
| 2026-05-11 | P4BFRS | - | May 11, 04:35 UTC | May 11, 04:55 UTC | 20m |
| 2026-05-09 | P4BFRS | - | May 9, 11:10 UTC | May 9, 18:20 UTC | 7h 10m |
| 2026-05-08 | P4BFRS | - | May 8, 18:10 UTC | May 8, 22:40 UTC | 4h 30m |
| 2026-05-07 | P4BFRS | - | May 7, 18:35 UTC | May 7, 18:45 UTC | 10m |
| 2026-05-07 | - | - | May 7, 17:20 UTC | May 7, 17:30 UTC | 10m |
| 2026-05-07 | P4BFRS | - | May 7, 12:50 UTC | May 7, 13:10 UTC | 20m |
| 2026-05-06 | P4BFRS | - | May 6, 18:50 UTC | May 6, 20:20 UTC | 1h 30m |
| 2026-05-06 | P4BFRS | - | May 6, 15:20 UTC | May 6, 15:40 UTC | 20m |
| 2026-05-06 | P4BFRS | - | May 6, 13:55 UTC | May 6, 14:10 UTC | 15m |
| 2026-05-05 | BFY735R | - | May 5, 18:10 UTC | May 5, 18:40 UTC | 30m |
| 2026-05-03 | BFY688R | - | May 3, 17:05 UTC | May 3, 17:24 UTC | 20m |
| 2026-05-01 | BFY732P | - | May 1, 17:55 UTC | May 1, 18:15 UTC | 20m |
| 2026-04-30 | BFY719R | - | Apr 30, 17:10 UTC | Apr 30, 17:20 UTC | 10m |
| 2026-04-30 | BFY664R | - | Apr 30, 09:55 UTC | Apr 30, 15:15 UTC | 5h 20m |
| 2026-04-29 | BFY663R | - | Apr 29, 15:05 UTC | Apr 29, 15:25 UTC | 20m |
| 2026-04-29 | BFY663R | - | Apr 29, 13:55 UTC | Apr 29, 14:10 UTC | 15m |
| 2026-04-29 | BFY662R | - | Apr 29, 05:15 UTC | Apr 29, 07:05 UTC | 1h 50m |
| 2026-04-28 | BFY661R | - | Apr 28, 02:05 UTC | Apr 28, 15:10 UTC | 13h 5m |
| 2026-04-27 | BFY685R | - | Apr 27, 04:40 UTC | Apr 27, 05:10 UTC | 30m |
| 2026-04-22 | BFY635R | - | Apr 22, 16:15 UTC | Apr 22, 16:45 UTC | 30m |
| 2026-04-22 | BFY634R | - | Apr 22, 06:50 UTC | Apr 22, 07:15 UTC | 25m |
| 2026-04-21 | BFY658R | - | Apr 21, 17:25 UTC | Apr 21, 19:35 UTC | 2h 10m |
| 2026-04-21 | BFY652R | - | Apr 21, 16:01 UTC | Apr 21, 16:31 UTC | 30m |
| 2026-04-20 | BFY643P | - | Apr 20, 20:15 UTC | Apr 20, 20:50 UTC | 35m |
| 2026-04-20 | BFY642R | - | Apr 20, 18:25 UTC | Apr 20, 19:00 UTC | 35m |
| 2026-04-19 | BFY581R | - | Apr 19, 12:20 UTC | Apr 20, 00:00 UTC | 11h 40m |
| 2026-04-15 | BFY580R | - | Apr 15, 23:40 UTC | Apr 16, 00:45 UTC | 1h 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 P4-BFRS page for operator, model, and routing details .