sensors Mode-S transponder
49D5C0
ICAO 24-bit transponder address · allocated to Czech Republic
Currently assigned to OK-EVO · GULFSTREAM G650 · operated by ABS Jets
- Hex
- 49D5C0
- Octal
- 22352700
- Decimal
- 4,838,848
- Country
- CZ
- Tail
- OK-EVO
- Type
- GLF6
- Flights observed
- 48
- Distinct callsigns
- 4
- Country
- CZ
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 49D5C0 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 48
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | ABP962 | OSH → TEB | Jul 17, 14:39 UTC | Jul 17, 16:15 UTC | 1h 35m |
| 2026-07-17 | ABP961 | - | Jul 17, 11:25 UTC | Jul 17, 12:10 UTC | 45m |
| 2026-07-15 | ABP964 | - | Jul 15, 18:00 UTC | Jul 15, 18:45 UTC | 45m |
| 2026-07-15 | ABP963 | - | Jul 15, 05:35 UTC | Jul 15, 06:35 UTC | 1h 0m |
| 2026-07-14 | ABP962 | - | Jul 14, 20:10 UTC | Jul 15, 04:50 UTC | 8h 39m |
| 2026-07-14 | ABP961 | - | Jul 14, 06:05 UTC | Jul 14, 07:20 UTC | 1h 15m |
| 2026-07-10 | ABP963 | - | Jul 10, 15:00 UTC | Jul 10, 16:20 UTC | 1h 20m |
| 2026-07-10 | ABP962 | - | Jul 10, 08:35 UTC | Jul 10, 09:35 UTC | 1h 0m |
| 2026-07-10 | ABP961 | PRG → PED | Jul 10, 05:55 UTC | Jul 10, 06:20 UTC | 25m |
| 2026-07-03 | ABP962 | - | Jul 3, 12:45 UTC | Jul 3, 13:05 UTC | 20m |
| 2026-07-03 | ABP961 | - | Jul 3, 12:00 UTC | Jul 3, 12:25 UTC | 25m |
| 2026-07-02 | ABP961 | - | Jul 2, 16:05 UTC | Jul 2, 16:35 UTC | 30m |
| 2026-07-01 | ABP961 | - | Jul 1, 12:00 UTC | Jul 1, 15:40 UTC | 3h 40m |
| 2026-06-30 | ABP961 | - | Jun 30, 18:15 UTC | Jul 1, 15:40 UTC | 21h 25m |
| 2026-06-30 | ABP961 | - | Jun 30, 16:05 UTC | Jul 1, 15:40 UTC | 23h 35m |
| 2026-06-30 | ABP961 | - | Jun 30, 15:25 UTC | Jul 1, 13:25 UTC | 22h 0m |
| 2026-06-17 | ABP961 | - | Jun 17, 15:50 UTC | Jun 17, 17:00 UTC | 1h 10m |
| 2026-06-15 | ABP961 | PRG → LBG | Jun 15, 05:04 UTC | Jun 15, 06:30 UTC | 1h 25m |
| 2026-06-10 | ABP963 | BTS → PRG | Jun 10, 13:10 UTC | Jun 10, 13:45 UTC | 35m |
| 2026-06-10 | ABP962 | QGY → BTS | Jun 10, 08:55 UTC | Jun 10, 09:10 UTC | 15m |
| 2026-06-10 | ABP961 | - | Jun 10, 04:45 UTC | Jun 10, 05:25 UTC | 40m |
| 2026-06-07 | ABP962 | NCE → PRG | Jun 7, 17:20 UTC | Jun 7, 18:40 UTC | 1h 20m |
| 2026-06-07 | ABP961 | PRG → NCE | Jun 7, 08:05 UTC | Jun 7, 09:30 UTC | 1h 25m |
| 2026-06-04 | ABP961 | - | Jun 4, 12:00 UTC | Jun 4, 13:05 UTC | 1h 5m |
| 2026-06-03 | ABP961 | PRG → LBG | Jun 3, 08:15 UTC | Jun 3, 09:25 UTC | 1h 10m |
| 2026-05-30 | ABP961 | - | May 30, 16:35 UTC | May 30, 22:15 UTC | 5h 40m |
| 2026-05-21 | ABP962 | - | May 21, 21:15 UTC | May 22, 02:50 UTC | 5h 35m |
| 2026-05-21 | ABP961 | - | May 21, 18:55 UTC | May 21, 19:10 UTC | 15m |
| 2026-05-13 | ABP962 | MAD → PRG | May 13, 16:15 UTC | May 13, 18:15 UTC | 2h 0m |
| 2026-05-13 | ABP961 | PRG → MAD | May 13, 08:30 UTC | May 13, 11:00 UTC | 2h 30m |
| 2026-05-10 | ABP961 | - | May 10, 09:00 UTC | May 10, 09:55 UTC | 55m |
| 2026-05-07 | ABP961 | - | May 7, 07:10 UTC | May 7, 08:10 UTC | 1h 0m |
| 2026-04-24 | ABP962 | BEG → PRG | Apr 24, 11:00 UTC | Apr 24, 12:00 UTC | 1h 0m |
| 2026-04-24 | ABP961 | - | Apr 24, 04:40 UTC | Apr 24, 05:40 UTC | 1h 0m |
| 2026-04-22 | ABP961 | - | Apr 22, 15:05 UTC | Apr 22, 16:05 UTC | 1h 0m |
| 2026-04-21 | ABP962 | LIN → BGY | Apr 21, 19:30 UTC | Apr 21, 19:40 UTC | 10m |
| 2026-04-21 | ABP961 | - | Apr 21, 14:55 UTC | Apr 21, 16:20 UTC | 1h 25m |
| 2026-04-17 | ABP963 | - | Apr 17, 15:20 UTC | Apr 17, 15:55 UTC | 35m |
| 2026-04-17 | ABP963 | - | Apr 17, 15:10 UTC | Apr 17, 15:15 UTC | 5m |
| 2026-04-17 | ABP961 | - | Apr 17, 11:35 UTC | Apr 17, 12:10 UTC | 35m |
| 2026-04-17 | ABP962 | PRG → BEG | Apr 17, 07:40 UTC | Apr 17, 08:40 UTC | 1h 0m |
| 2026-04-16 | ABP964 | - | Apr 16, 19:15 UTC | Apr 16, 20:20 UTC | 1h 5m |
| 2026-04-16 | ABP963 | - | Apr 16, 13:15 UTC | Apr 16, 14:05 UTC | 50m |
| 2026-04-16 | ABP963 | - | Apr 16, 11:49 UTC | Apr 16, 13:05 UTC | 1h 15m |
| 2026-04-16 | ABP962 | - | Apr 16, 09:10 UTC | Apr 16, 09:39 UTC | 30m |
| 2026-04-16 | ABP962 | - | Apr 16, 08:50 UTC | Apr 16, 09:05 UTC | 15m |
| 2026-04-16 | ABP961 | - | Apr 16, 05:09 UTC | Apr 16, 05:20 UTC | 10m |
| 2026-04-16 | ABP961 | - | Apr 16, 04:00 UTC | Apr 16, 05:05 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 OK-EVO page for operator, model, and routing details .