sensors Mode-S transponder
49D57D
ICAO 24-bit transponder address · allocated to Czech Republic
Currently assigned to OK-TTG · ROBINSON R-66
- Hex
- 49D57D
- Octal
- 22352575
- Decimal
- 4,838,781
- Country
- CZ
- Tail
- OK-TTG
- Type
- R66
- Flights observed
- 75
- Distinct callsigns
- 1
- Country
- CZ
- Last broadcast
- 16d ago
Last known position
Country allocation
The ICAO 24-bit address 49D57D 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 |
|---|---|---|---|
| OKTTG | - | 75 | 2026-06-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-27 | OKTTG | - | Jun 27, 15:00 UTC | Jun 27, 17:14 UTC | 2h 15m |
| 2026-06-27 | OKTTG | - | Jun 27, 07:04 UTC | Jun 27, 08:44 UTC | 1h 40m |
| 2026-06-26 | OKTTG | - | Jun 26, 13:19 UTC | Jun 26, 15:49 UTC | 2h 30m |
| 2026-06-24 | OKTTG | - | Jun 24, 16:34 UTC | Jun 24, 17:40 UTC | 1h 5m |
| 2026-06-24 | OKTTG | - | Jun 24, 14:04 UTC | Jun 24, 15:14 UTC | 1h 10m |
| 2026-06-23 | OKTTG | - | Jun 23, 14:19 UTC | Jun 23, 16:09 UTC | 1h 50m |
| 2026-06-23 | OKTTG | - | Jun 23, 06:04 UTC | Jun 23, 07:15 UTC | 1h 10m |
| 2026-06-20 | OKTTG | - | Jun 20, 08:05 UTC | Jun 20, 09:09 UTC | 1h 5m |
| 2026-06-18 | OKTTG | - | Jun 18, 15:50 UTC | Jun 18, 16:55 UTC | 1h 5m |
| 2026-06-18 | OKTTG | - | Jun 18, 05:30 UTC | Jun 18, 06:40 UTC | 1h 10m |
| 2026-06-15 | OKTTG | - | Jun 15, 08:00 UTC | Jun 15, 08:29 UTC | 30m |
| 2026-06-14 | OKTTG | - | Jun 14, 09:25 UTC | Jun 14, 10:00 UTC | 35m |
| 2026-06-11 | OKTTG | - | Jun 11, 12:45 UTC | Jun 11, 16:25 UTC | 3h 40m |
| 2026-06-09 | OKTTG | - | Jun 9, 16:45 UTC | Jun 9, 17:00 UTC | 15m |
| 2026-06-09 | OKTTG | - | Jun 9, 12:15 UTC | Jun 9, 13:50 UTC | 1h 35m |
| 2026-06-08 | OKTTG | - | Jun 8, 13:05 UTC | Jun 8, 15:55 UTC | 2h 50m |
| 2026-06-05 | OKTTG | - | Jun 5, 16:25 UTC | Jun 5, 18:00 UTC | 1h 35m |
| 2026-06-05 | OKTTG | - | Jun 5, 14:45 UTC | Jun 5, 15:40 UTC | 55m |
| 2026-06-05 | OKTTG | - | Jun 5, 13:30 UTC | Jun 5, 13:45 UTC | 15m |
| 2026-06-04 | OKTTG | - | Jun 4, 15:25 UTC | Jun 4, 17:05 UTC | 1h 40m |
| 2026-06-04 | OKTTG | - | Jun 4, 14:50 UTC | Jun 4, 15:15 UTC | 25m |
| 2026-06-03 | OKTTG | - | Jun 3, 06:25 UTC | Jun 3, 06:50 UTC | 25m |
| 2026-06-03 | OKTTG | - | Jun 3, 05:50 UTC | Jun 3, 06:20 UTC | 30m |
| 2026-06-02 | OKTTG | - | Jun 2, 07:50 UTC | Jun 2, 08:20 UTC | 30m |
| 2026-06-02 | OKTTG | - | Jun 2, 05:50 UTC | Jun 2, 06:20 UTC | 30m |
| 2026-05-30 | OKTTG | - | May 30, 15:10 UTC | May 30, 16:20 UTC | 1h 10m |
| 2026-05-30 | OKTTG | - | May 30, 14:50 UTC | May 30, 15:05 UTC | 15m |
| 2026-05-30 | OKTTG | - | May 30, 06:30 UTC | May 30, 06:55 UTC | 25m |
| 2026-05-30 | OKTTG | - | May 30, 05:40 UTC | May 30, 06:25 UTC | 45m |
| 2026-05-28 | OKTTG | - | May 28, 15:00 UTC | May 28, 15:40 UTC | 40m |
| 2026-05-28 | OKTTG | - | May 28, 13:55 UTC | May 28, 14:55 UTC | 1h 0m |
| 2026-05-28 | OKTTG | - | May 28, 08:40 UTC | May 28, 09:30 UTC | 50m |
| 2026-05-24 | OKTTG | - | May 24, 14:15 UTC | May 24, 15:00 UTC | 45m |
| 2026-05-24 | OKTTG | - | May 24, 06:25 UTC | May 24, 07:20 UTC | 55m |
| 2026-05-23 | OKTTG | - | May 23, 16:35 UTC | May 23, 17:10 UTC | 35m |
| 2026-05-23 | OKTTG | - | May 23, 14:20 UTC | May 23, 14:40 UTC | 20m |
| 2026-05-23 | OKTTG | - | May 23, 13:20 UTC | May 23, 14:15 UTC | 55m |
| 2026-05-22 | OKTTG | - | May 22, 13:25 UTC | May 22, 16:20 UTC | 2h 55m |
| 2026-05-19 | OKTTG | - | May 19, 15:15 UTC | May 19, 16:45 UTC | 1h 30m |
| 2026-05-19 | OKTTG | - | May 19, 14:25 UTC | May 19, 14:40 UTC | 15m |
| 2026-05-19 | OKTTG | - | May 19, 10:00 UTC | May 19, 10:25 UTC | 25m |
| 2026-05-19 | OKTTG | - | May 19, 09:45 UTC | May 19, 09:55 UTC | 10m |
| 2026-05-14 | OKTTG | - | May 14, 14:45 UTC | May 14, 15:30 UTC | 45m |
| 2026-05-14 | OKTTG | - | May 14, 06:55 UTC | May 14, 07:00 UTC | 5m |
| 2026-05-14 | OKTTG | - | May 14, 06:05 UTC | May 14, 06:50 UTC | 45m |
| 2026-05-12 | OKTTG | - | May 12, 17:40 UTC | May 12, 18:15 UTC | 35m |
| 2026-05-12 | OKTTG | - | May 12, 16:25 UTC | May 12, 17:35 UTC | 1h 10m |
| 2026-05-12 | OKTTG | - | May 12, 15:05 UTC | May 12, 15:45 UTC | 40m |
| 2026-05-11 | OKTTG | - | May 11, 04:25 UTC | May 11, 04:55 UTC | 30m |
| 2026-05-10 | OKTTG | - | May 10, 08:15 UTC | May 10, 09:00 UTC | 45m |
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-TTG page for operator, model, and routing details .