sensors Mode-S transponder
49D39D
ICAO 24-bit transponder address · allocated to Czech Republic
Currently assigned to OK-JMD · GULFSTREAM 5
- Hex
- 49D39D
- Octal
- 22351635
- Decimal
- 4,838,301
- Country
- CZ
- Tail
- OK-JMD
- Type
- GLF5
- Flights observed
- 52
- Distinct callsigns
- 4
- Country
- CZ
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 49D39D falls within the block assigned to Czech Republic (CZ) by ICAO Annex 10, Volume III. Every aircraft registered in Czech Republic 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-16 | ABP931 | - | Jul 16, 10:40 UTC | Jul 16, 12:09 UTC | 1h 30m |
| 2026-07-11 | ABP932 | - | Jul 11, 13:30 UTC | Jul 11, 15:10 UTC | 1h 40m |
| 2026-07-11 | ABP931 | - | Jul 11, 11:30 UTC | Jul 11, 12:35 UTC | 1h 5m |
| 2026-07-10 | ABP932 | - | Jul 10, 12:30 UTC | Jul 10, 14:40 UTC | 2h 10m |
| 2026-07-10 | ABP931 | - | Jul 10, 08:20 UTC | Jul 10, 10:50 UTC | 2h 30m |
| 2026-07-03 | ABP931 | - | Jul 3, 09:35 UTC | Jul 3, 10:30 UTC | 55m |
| 2026-07-03 | ABP932 | - | Jul 3, 06:55 UTC | Jul 3, 08:30 UTC | 1h 35m |
| 2026-07-01 | ABP931 | - | Jul 1, 10:00 UTC | Jul 1, 11:35 UTC | 1h 35m |
| 2026-06-26 | ABP931 | - | Jun 26, 11:09 UTC | Jun 26, 12:39 UTC | 1h 30m |
| 2026-06-23 | ABP932 | MLA → PRG | Jun 23, 18:25 UTC | Jun 23, 20:24 UTC | 2h 0m |
| 2026-06-23 | ABP931 | PRG → MLA | Jun 23, 08:59 UTC | Jun 23, 11:10 UTC | 2h 10m |
| 2026-06-22 | ABP931 | - | Jun 22, 17:15 UTC | Jun 22, 18:49 UTC | 1h 35m |
| 2026-06-21 | ABP932 | - | Jun 21, 18:35 UTC | Jun 21, 19:05 UTC | 30m |
| 2026-06-21 | ABP931 | - | Jun 21, 15:25 UTC | Jun 21, 16:44 UTC | 1h 20m |
| 2026-06-19 | ABP932 | SOF → PRG | Jun 19, 13:24 UTC | Jun 19, 14:59 UTC | 1h 35m |
| 2026-06-19 | ABP931 | PRG → SOF | Jun 19, 10:35 UTC | Jun 19, 11:59 UTC | 1h 25m |
| 2026-06-18 | ABP933 | - | Jun 18, 18:55 UTC | Jun 18, 19:30 UTC | 35m |
| 2026-06-18 | ABP932 | MUC → OBF | Jun 18, 18:15 UTC | Jun 18, 18:30 UTC | 15m |
| 2026-06-18 | ABP931 | PRG → MUC | Jun 18, 16:15 UTC | Jun 18, 16:50 UTC | 35m |
| 2026-06-14 | ABP932 | - | Jun 14, 17:25 UTC | Jun 14, 19:00 UTC | 1h 35m |
| 2026-06-14 | ABP931 | - | Jun 14, 15:25 UTC | Jun 14, 16:35 UTC | 1h 10m |
| 2026-06-12 | ABP932 | SOF → PRG | Jun 12, 13:20 UTC | Jun 12, 14:45 UTC | 1h 25m |
| 2026-06-12 | ABP931 | PRG → SOF | Jun 12, 10:45 UTC | Jun 12, 12:15 UTC | 1h 30m |
| 2026-06-07 | ABP932 | SOF → PRG | Jun 7, 19:05 UTC | Jun 7, 20:30 UTC | 1h 25m |
| 2026-06-07 | ABP931 | PRG → SOF | Jun 7, 16:25 UTC | Jun 7, 17:45 UTC | 1h 20m |
| 2026-06-05 | ABP932 | SOF → PRG | Jun 5, 13:25 UTC | Jun 5, 14:55 UTC | 1h 30m |
| 2026-06-05 | ABP931 | PRG → SOF | Jun 5, 10:20 UTC | Jun 5, 11:45 UTC | 1h 25m |
| 2026-06-02 | ABP932 | - | Jun 2, 19:00 UTC | Jun 2, 20:30 UTC | 1h 30m |
| 2026-06-02 | ABP931 | - | Jun 2, 16:30 UTC | Jun 2, 17:45 UTC | 1h 15m |
| 2026-05-29 | ABP932 | - | May 29, 13:20 UTC | May 29, 14:45 UTC | 1h 25m |
| 2026-05-29 | ABP931 | - | May 29, 11:00 UTC | May 29, 12:15 UTC | 1h 15m |
| 2026-05-26 | OKJMD | - | May 26, 21:09 UTC | May 27, 08:50 UTC | 11h 41m |
| 2026-05-23 | OKJMD | - | May 23, 06:25 UTC | May 23, 19:15 UTC | 12h 51m |
| 2026-05-17 | ABP931 | - | May 17, 06:55 UTC | May 17, 08:30 UTC | 1h 35m |
| 2026-05-15 | ABP932 | - | May 15, 13:20 UTC | May 15, 13:45 UTC | 25m |
| 2026-05-15 | ABP931 | - | May 15, 10:40 UTC | May 15, 11:55 UTC | 1h 15m |
| 2026-05-14 | ABP932 | RIX → PRG | May 14, 15:20 UTC | May 14, 16:50 UTC | 1h 30m |
| 2026-05-14 | ABP931 | - | May 14, 07:45 UTC | May 14, 09:05 UTC | 1h 20m |
| 2026-05-12 | ABP931 | - | May 12, 12:20 UTC | May 12, 13:55 UTC | 1h 35m |
| 2026-05-08 | ABP931 | - | May 8, 07:04 UTC | May 8, 08:34 UTC | 1h 30m |
| 2026-05-03 | ABP932 | - | May 3, 19:10 UTC | May 3, 20:35 UTC | 1h 25m |
| 2026-05-03 | ABP931 | - | May 3, 16:50 UTC | May 3, 18:00 UTC | 1h 10m |
| 2026-05-01 | ABP932 | - | May 1, 10:30 UTC | May 1, 11:55 UTC | 1h 25m |
| 2026-05-01 | ABP931 | - | May 1, 08:10 UTC | May 1, 09:20 UTC | 1h 10m |
| 2026-04-30 | OKJMD | - | Apr 30, 21:30 UTC | May 1, 07:00 UTC | 9h 30m |
| 2026-04-26 | OKJMD | - | Apr 26, 11:50 UTC | Apr 26, 21:20 UTC | 9h 30m |
| 2026-04-21 | OKJMD | - | Apr 21, 22:45 UTC | Apr 22, 03:55 UTC | 5h 10m |
| 2026-04-20 | OKJMD | - | Apr 20, 11:15 UTC | Apr 20, 16:15 UTC | 5h 0m |
| 2026-04-17 | OKJMD | - | Apr 17, 17:35 UTC | Apr 17, 18:20 UTC | 45m |
| 2026-04-17 | OKJMD | - | Apr 17, 11:45 UTC | Apr 17, 12:20 UTC | 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 OK-JMD page for operator, model, and routing details .