sensors Mode-S transponder
505C53
ICAO 24-bit transponder address · allocated to Slovakia
Currently assigned to OM-BLS · CESSNA 560XL Citation XLS
- Hex
- 505C53
- Octal
- 24056123
- Decimal
- 5,266,515
- Country
- SK
- Tail
- OM-BLS
- Type
- C56X
- Flights observed
- 71
- Distinct callsigns
- 1
- Country
- SK
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 505C53 falls within the block assigned to Slovakia (SK) by ICAO Annex 10, Volume III. Every aircraft registered in Slovakia 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 |
|---|---|---|---|
| TTJ600 | - | 71 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-18 | TTJ600 | OLB → BTS | Jul 18, 10:40 UTC | Jul 18, 12:10 UTC | 1h 30m |
| 2026-07-17 | TTJ600 | - | Jul 17, 17:55 UTC | Jul 17, 19:05 UTC | 1h 10m |
| 2026-07-17 | TTJ600 | - | Jul 17, 15:05 UTC | Jul 17, 15:55 UTC | 50m |
| 2026-07-17 | TTJ600 | - | Jul 17, 11:55 UTC | Jul 17, 12:04 UTC | 10m |
| 2026-07-15 | TTJ600 | - | Jul 15, 12:45 UTC | Jul 15, 13:25 UTC | 40m |
| 2026-07-15 | TTJ600 | - | Jul 15, 06:40 UTC | Jul 15, 07:10 UTC | 30m |
| 2026-07-15 | TTJ600 | LIN → BTS | Jul 15, 05:00 UTC | Jul 15, 06:00 UTC | 1h 0m |
| 2026-07-13 | TTJ600 | BTS → LIN | Jul 13, 08:20 UTC | Jul 13, 09:35 UTC | 1h 15m |
| 2026-07-08 | TTJ600 | - | Jul 8, 14:55 UTC | Jul 8, 16:20 UTC | 1h 25m |
| 2026-07-08 | TTJ600 | - | Jul 8, 12:15 UTC | Jul 8, 13:30 UTC | 1h 15m |
| 2026-07-02 | TTJ600 | - | Jul 2, 06:15 UTC | Jul 2, 07:25 UTC | 1h 10m |
| 2026-07-01 | TTJ600 | - | Jul 1, 12:15 UTC | Jul 1, 13:30 UTC | 1h 15m |
| 2026-06-30 | TTJ600 | - | Jun 30, 14:25 UTC | Jun 30, 14:50 UTC | 25m |
| 2026-06-30 | TTJ600 | - | Jun 30, 13:00 UTC | Jun 30, 13:40 UTC | 40m |
| 2026-06-30 | TTJ600 | - | Jun 30, 07:45 UTC | Jun 30, 08:15 UTC | 30m |
| 2026-06-29 | TTJ600 | ZRH → BTS | Jun 29, 12:29 UTC | Jun 29, 13:34 UTC | 1h 5m |
| 2026-06-29 | TTJ600 | - | Jun 29, 06:14 UTC | Jun 29, 07:30 UTC | 1h 15m |
| 2026-06-27 | TTJ600 | - | Jun 27, 11:30 UTC | Jun 27, 13:44 UTC | 2h 15m |
| 2026-06-27 | TTJ600 | - | Jun 27, 09:29 UTC | Jun 27, 10:19 UTC | 50m |
| 2026-06-26 | TTJ600 | - | Jun 26, 16:24 UTC | Jun 26, 17:00 UTC | 35m |
| 2026-06-22 | TTJ600 | - | Jun 22, 12:40 UTC | Jun 22, 13:54 UTC | 1h 15m |
| 2026-06-21 | TTJ600 | - | Jun 21, 06:29 UTC | Jun 21, 08:04 UTC | 1h 35m |
| 2026-06-20 | TTJ600 | - | Jun 20, 13:44 UTC | Jun 20, 15:29 UTC | 1h 45m |
| 2026-06-20 | TTJ600 | - | Jun 20, 10:29 UTC | Jun 20, 12:39 UTC | 2h 10m |
| 2026-06-20 | TTJ600 | BTS → BOD | Jun 20, 05:49 UTC | Jun 20, 08:19 UTC | 2h 30m |
| 2026-06-17 | TTJ600 | BOD → BTS | Jun 17, 10:10 UTC | Jun 17, 12:15 UTC | 2h 5m |
| 2026-06-17 | TTJ600 | BTS → BOD | Jun 17, 06:40 UTC | Jun 17, 08:50 UTC | 2h 10m |
| 2026-06-16 | TTJ600 | - | Jun 16, 12:14 UTC | Jun 16, 12:50 UTC | 35m |
| 2026-06-16 | TTJ600 | - | Jun 16, 07:20 UTC | Jun 16, 07:50 UTC | 30m |
| 2026-06-14 | TTJ600 | PRG → BTS | Jun 14, 14:55 UTC | Jun 14, 15:30 UTC | 35m |
| 2026-06-14 | TTJ600 | - | Jun 14, 12:55 UTC | Jun 14, 14:00 UTC | 1h 5m |
| 2026-06-12 | TTJ600 | PRG → AMS | Jun 12, 07:45 UTC | Jun 12, 09:00 UTC | 1h 15m |
| 2026-06-12 | TTJ600 | - | Jun 12, 06:15 UTC | Jun 12, 06:55 UTC | 40m |
| 2026-06-10 | TTJ600 | PRG → BTS | Jun 10, 14:05 UTC | Jun 10, 14:45 UTC | 40m |
| 2026-06-09 | TTJ600 | - | Jun 9, 12:05 UTC | Jun 9, 12:40 UTC | 35m |
| 2026-06-09 | TTJ600 | VIE → BTS | Jun 9, 10:10 UTC | Jun 9, 10:25 UTC | 15m |
| 2026-06-05 | TTJ600 | - | Jun 5, 05:25 UTC | Jun 5, 05:45 UTC | 20m |
| 2026-06-04 | TTJ600 | HAM → BTS | Jun 4, 12:50 UTC | Jun 4, 14:05 UTC | 1h 15m |
| 2026-06-03 | TTJ600 | BTS → HAM | Jun 3, 13:00 UTC | Jun 3, 14:20 UTC | 1h 20m |
| 2026-06-02 | TTJ600 | VIE → BTS | Jun 2, 16:20 UTC | Jun 2, 16:35 UTC | 15m |
| 2026-06-01 | TTJ600 | - | Jun 1, 06:10 UTC | Jun 1, 06:30 UTC | 20m |
| 2026-05-29 | TTJ600 | PRG → BTS | May 29, 14:25 UTC | May 29, 15:05 UTC | 40m |
| 2026-05-28 | TTJ600 | BTS → PRG | May 28, 03:45 UTC | May 28, 04:20 UTC | 35m |
| 2026-05-27 | TTJ600 | VCE → BTS | May 27, 13:30 UTC | May 27, 14:25 UTC | 55m |
| 2026-05-27 | TTJ600 | BTS → VCE | May 27, 10:55 UTC | May 27, 11:50 UTC | 55m |
| 2026-05-26 | TTJ600 | ZRH → BTS | May 26, 16:40 UTC | May 26, 17:39 UTC | 1h 0m |
| 2026-05-25 | TTJ600 | - | May 25, 06:30 UTC | May 25, 07:30 UTC | 1h 0m |
| 2026-05-25 | TTJ600 | BTS → BER | May 25, 04:40 UTC | May 25, 05:35 UTC | 55m |
| 2026-05-24 | TTJ600 | - | May 24, 15:10 UTC | May 24, 17:30 UTC | 2h 20m |
| 2026-05-24 | TTJ600 | - | May 24, 09:40 UTC | May 24, 12:00 UTC | 2h 20m |
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 OM-BLS page for operator, model, and routing details .