sensors Mode-S transponder
49C4B5
ICAO 24-bit transponder address · allocated to Czech Republic
- Hex
- 49C4B5
- Octal
- 22342265
- Decimal
- 4,834,485
- Country
- CZ
- Flights observed
- 24
- Distinct callsigns
- 1
- Country
- CZ
- Last broadcast
- 10h ago
Last known position
Country allocation
The ICAO 24-bit address 49C4B5 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OKFUG02 | - | 24 | 2026-07-21 |
Recent flights last 24
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-21 | OKFUG02 | - | Jul 21, 08:55 UTC | Jul 21, 09:05 UTC | 10m |
| 2026-07-20 | OKFUG02 | - | Jul 20, 10:00 UTC | Jul 20, 10:50 UTC | 50m |
| 2026-07-20 | OKFUG02 | - | Jul 20, 07:40 UTC | Jul 20, 08:45 UTC | 1h 5m |
| 2026-07-20 | OKFUG02 | - | Jul 20, 05:50 UTC | Jul 20, 06:55 UTC | 1h 5m |
| 2026-07-16 | OKFUG02 | - | Jul 16, 09:55 UTC | Jul 16, 10:40 UTC | 45m |
| 2026-07-02 | OKFUG02 | - | Jul 2, 12:10 UTC | Jul 2, 13:20 UTC | 1h 10m |
| 2026-07-02 | OKFUG02 | - | Jul 2, 11:15 UTC | Jul 2, 11:35 UTC | 20m |
| 2026-07-02 | OKFUG02 | - | Jul 2, 09:10 UTC | Jul 2, 09:35 UTC | 25m |
| 2026-06-25 | OKFUG02 | - | Jun 25, 12:04 UTC | Jun 25, 12:50 UTC | 45m |
| 2026-06-25 | OKFUG02 | - | Jun 25, 09:10 UTC | Jun 25, 09:25 UTC | 15m |
| 2026-06-25 | OKFUG02 | - | Jun 25, 07:54 UTC | Jun 25, 08:40 UTC | 45m |
| 2026-06-25 | OKFUG02 | - | Jun 25, 06:35 UTC | Jun 25, 07:00 UTC | 25m |
| 2026-06-17 | OKFUG02 | - | Jun 17, 11:55 UTC | Jun 17, 12:05 UTC | 10m |
| 2026-06-17 | OKFUG02 | - | Jun 17, 09:15 UTC | Jun 17, 10:05 UTC | 50m |
| 2026-06-17 | OKFUG02 | - | Jun 17, 07:50 UTC | Jun 17, 08:30 UTC | 40m |
| 2026-06-16 | OKFUG02 | - | Jun 16, 08:55 UTC | Jun 16, 09:25 UTC | 30m |
| 2026-06-12 | OKFUG02 | - | Jun 12, 10:40 UTC | Jun 12, 11:25 UTC | 45m |
| 2026-06-12 | OKFUG02 | - | Jun 12, 08:30 UTC | Jun 12, 09:35 UTC | 1h 5m |
| 2026-06-12 | OKFUG02 | - | Jun 12, 06:20 UTC | Jun 12, 07:20 UTC | 1h 0m |
| 2026-06-06 | OKFUG02 | - | Jun 6, 12:10 UTC | Jun 6, 12:24 UTC | 15m |
| 2026-06-06 | OKFUG02 | - | Jun 6, 09:39 UTC | Jun 6, 10:00 UTC | 20m |
| 2026-06-06 | OKFUG02 | - | Jun 6, 07:10 UTC | Jun 6, 08:30 UTC | 1h 20m |
| 2026-06-02 | OKFUG02 | - | Jun 2, 09:40 UTC | Jun 2, 10:20 UTC | 40m |
| 2026-05-27 | OKFUG02 | - | May 27, 03:45 UTC | May 27, 05:59 UTC | 2h 15m |
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.