sensors Mode-S transponder
48433D
ICAO 24-bit transponder address · allocated to Netherlands
Currently assigned to P4-JIMI · BOMBARDIER BD-100 Challenger 350
- Hex
- 48433D
- Octal
- 22041475
- Decimal
- 4,735,805
- Country
- NL
- Tail
- P4-JIMI
- Type
- CL35
- Flights observed
- 43
- Distinct callsigns
- 1
- Country
- NL
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 48433D 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| P4JIMI | - | 43 | 2026-07-10 |
Recent flights last 43
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-10 | P4JIMI | - | Jul 10, 15:25 UTC | Jul 10, 19:05 UTC | 3h 40m |
| 2026-07-09 | P4JIMI | MUC → FAB | Jul 9, 18:55 UTC | Jul 9, 20:25 UTC | 1h 30m |
| 2026-07-09 | P4JIMI | ISL → MUC | Jul 9, 15:30 UTC | Jul 9, 18:05 UTC | 2h 35m |
| 2026-07-09 | P4JIMI | BEN → ISL | Jul 9, 11:25 UTC | Jul 9, 13:30 UTC | 2h 5m |
| 2026-07-06 | P4JIMI | - | Jul 6, 17:55 UTC | Jul 6, 18:35 UTC | 40m |
| 2026-07-05 | P4JIMI | - | Jul 5, 15:05 UTC | Jul 5, 15:40 UTC | 35m |
| 2026-07-02 | P4JIMI | - | Jul 2, 18:00 UTC | Jul 2, 18:50 UTC | 50m |
| 2026-07-02 | P4JIMI | DBB → ATH | Jul 2, 15:30 UTC | Jul 2, 16:50 UTC | 1h 20m |
| 2026-07-02 | P4JIMI | - | Jul 2, 13:55 UTC | Jul 2, 14:20 UTC | 25m |
| 2026-06-30 | P4JIMI | - | Jun 30, 11:20 UTC | Jun 30, 14:55 UTC | 3h 35m |
| 2026-06-29 | P4JIMI | - | Jun 29, 10:29 UTC | Jun 29, 14:14 UTC | 3h 45m |
| 2026-06-28 | P4JIMI | - | Jun 28, 06:59 UTC | Jun 28, 10:30 UTC | 3h 30m |
| 2026-06-27 | P4JIMI | - | Jun 27, 10:54 UTC | Jun 27, 15:00 UTC | 4h 5m |
| 2026-06-24 | P4JIMI | - | Jun 24, 15:44 UTC | Jun 24, 15:59 UTC | 15m |
| 2026-06-24 | P4JIMI | - | Jun 24, 11:59 UTC | Jun 24, 12:09 UTC | 10m |
| 2026-06-22 | P4JIMI | - | Jun 22, 12:49 UTC | Jun 22, 14:05 UTC | 1h 15m |
| 2026-06-22 | P4JIMI | - | Jun 22, 09:34 UTC | Jun 22, 10:55 UTC | 1h 20m |
| 2026-06-20 | P4JIMI | - | Jun 20, 20:29 UTC | Jun 20, 20:55 UTC | 25m |
| 2026-06-19 | P4JIMI | - | Jun 19, 10:19 UTC | Jun 19, 12:34 UTC | 2h 15m |
| 2026-06-19 | P4JIMI | - | Jun 19, 06:20 UTC | Jun 19, 08:40 UTC | 2h 20m |
| 2026-06-12 | P4JIMI | - | Jun 12, 09:45 UTC | Jun 12, 10:20 UTC | 35m |
| 2026-06-04 | P4JIMI | MLA → MLA | Jun 4, 06:30 UTC | Jun 4, 06:45 UTC | 15m |
| 2026-06-04 | P4JIMI | MLA → MLA | Jun 4, 06:15 UTC | Jun 4, 06:25 UTC | 10m |
| 2026-06-02 | P4JIMI | MLA → MLA | Jun 2, 03:15 UTC | Jun 2, 03:25 UTC | 10m |
| 2026-06-01 | P4JIMI | MLA → MLA | Jun 1, 12:10 UTC | Jun 1, 12:40 UTC | 30m |
| 2026-06-01 | P4JIMI | MLA → MLA | Jun 1, 09:35 UTC | Jun 1, 10:20 UTC | 45m |
| 2026-05-30 | P4JIMI | - | May 30, 10:00 UTC | May 30, 11:15 UTC | 1h 15m |
| 2026-05-30 | P4JIMI | - | May 30, 07:50 UTC | May 30, 08:40 UTC | 50m |
| 2026-05-26 | P4JIMI | - | May 26, 14:20 UTC | May 26, 15:35 UTC | 1h 15m |
| 2026-05-22 | P4JIMI | - | May 22, 14:40 UTC | May 22, 15:30 UTC | 50m |
| 2026-05-18 | P4JIMI | - | May 18, 09:00 UTC | May 18, 11:25 UTC | 2h 25m |
| 2026-05-18 | P4JIMI | - | May 18, 04:15 UTC | May 18, 06:55 UTC | 2h 40m |
| 2026-05-15 | P4JIMI | - | May 15, 16:50 UTC | May 15, 18:15 UTC | 1h 25m |
| 2026-05-15 | P4JIMI | - | May 15, 14:10 UTC | May 15, 15:10 UTC | 59m |
| 2026-05-07 | P4JIMI | - | May 7, 10:35 UTC | May 7, 13:15 UTC | 2h 40m |
| 2026-05-07 | P4JIMI | - | May 7, 05:20 UTC | May 7, 08:10 UTC | 2h 50m |
| 2026-05-02 | P4JIMI | - | May 2, 11:40 UTC | May 2, 14:10 UTC | 2h 30m |
| 2026-05-01 | P4JIMI | - | May 1, 00:10 UTC | May 1, 07:55 UTC | 7h 45m |
| 2026-04-13 | P4JIMI | - | Apr 13, 06:20 UTC | Apr 13, 06:55 UTC | 35m |
| 2026-04-13 | P4JIMI | - | Apr 13, 02:15 UTC | Apr 13, 02:25 UTC | 10m |
| 2026-04-13 | P4JIMI | - | Apr 13, 00:20 UTC | Apr 13, 00:45 UTC | 25m |
| 2026-04-12 | P4JIMI | - | Apr 12, 23:55 UTC | Apr 13, 00:45 UTC | 50m |
| 2026-04-12 | P4JIMI | - | Apr 12, 19:05 UTC | Apr 12, 20:15 UTC | 1h 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-JIMI page for operator, model, and routing details .