sensors Mode-S transponder
505E81
ICAO 24-bit transponder address · allocated to Slovakia
Currently assigned to OM-TAA · RAYTHEON 390 Premier 1
- Hex
- 505E81
- Octal
- 24057201
- Decimal
- 5,267,073
- Country
- SK
- Tail
- OM-TAA
- Type
- PRM1
- Flights observed
- 37
- Distinct callsigns
- 1
- Country
- SK
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 505E81 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 |
|---|---|---|---|
| TTJ613 | - | 37 | 2026-06-11 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-11 | TTJ613 | - | Jun 11, 09:45 UTC | Jun 11, 10:05 UTC | 20m |
| 2026-06-11 | TTJ613 | - | Jun 11, 07:45 UTC | Jun 11, 08:35 UTC | 50m |
| 2026-06-10 | TTJ613 | - | Jun 10, 10:10 UTC | Jun 10, 10:50 UTC | 40m |
| 2026-06-10 | TTJ613 | - | Jun 10, 08:10 UTC | Jun 10, 09:15 UTC | 1h 5m |
| 2026-06-10 | TTJ613 | BTS → PED | Jun 10, 06:10 UTC | Jun 10, 06:35 UTC | 25m |
| 2026-06-09 | TTJ613 | PRG → BTS | Jun 9, 13:35 UTC | Jun 9, 14:15 UTC | 40m |
| 2026-06-09 | TTJ613 | - | Jun 9, 06:20 UTC | Jun 9, 06:55 UTC | 35m |
| 2026-06-05 | TTJ613 | BRQ → BTS | Jun 5, 20:35 UTC | Jun 5, 20:50 UTC | 15m |
| 2026-06-05 | TTJ613 | LBG → BRQ | Jun 5, 18:15 UTC | Jun 5, 19:40 UTC | 1h 25m |
| 2026-06-05 | TTJ613 | BRQ → LBG | Jun 5, 07:10 UTC | Jun 5, 08:50 UTC | 1h 40m |
| 2026-06-05 | TTJ613 | VIE → BRQ | Jun 5, 05:50 UTC | Jun 5, 06:10 UTC | 20m |
| 2026-05-30 | TTJ613 | - | May 30, 10:00 UTC | May 30, 11:55 UTC | 1h 55m |
| 2026-05-30 | TTJ613 | - | May 30, 07:30 UTC | May 30, 08:25 UTC | 55m |
| 2026-05-28 | TTJ613 | - | May 28, 18:10 UTC | May 28, 18:55 UTC | 45m |
| 2026-05-28 | TTJ613 | - | May 28, 15:35 UTC | May 28, 17:25 UTC | 1h 50m |
| 2026-05-28 | TTJ613 | BTS → VIE | May 28, 13:55 UTC | May 28, 14:15 UTC | 20m |
| 2026-05-25 | TTJ613 | - | May 25, 13:30 UTC | May 25, 14:15 UTC | 45m |
| 2026-05-25 | TTJ613 | - | May 25, 12:05 UTC | May 25, 12:50 UTC | 45m |
| 2026-05-15 | TTJ613 | - | May 15, 12:30 UTC | May 15, 13:10 UTC | 40m |
| 2026-05-15 | TTJ613 | HAM → PRG | May 15, 09:10 UTC | May 15, 10:05 UTC | 55m |
| 2026-05-14 | TTJ613 | BTS → HAM | May 14, 08:25 UTC | May 14, 09:40 UTC | 1h 15m |
| 2026-05-12 | TTJ613 | - | May 12, 14:15 UTC | May 12, 14:55 UTC | 40m |
| 2026-05-12 | TTJ613 | BTS → PRG | May 12, 06:00 UTC | May 12, 06:35 UTC | 35m |
| 2026-05-10 | TTJ613 | - | May 10, 15:15 UTC | May 10, 15:19 UTC | 5m |
| 2026-05-10 | TTJ613 | - | May 10, 13:35 UTC | May 10, 14:54 UTC | 1h 20m |
| 2026-05-08 | TTJ613 | VIE → CIA | May 8, 15:20 UTC | May 8, 16:35 UTC | 1h 15m |
| 2026-05-08 | TTJ613 | INN → VIE | May 8, 05:09 UTC | May 8, 05:54 UTC | 45m |
| 2026-05-07 | TTJ613 | VIE → INN | May 7, 12:30 UTC | May 7, 13:15 UTC | 45m |
| 2026-05-07 | TTJ613 | - | May 7, 11:00 UTC | May 7, 11:15 UTC | 15m |
| 2026-05-03 | TTJ613 | - | May 3, 12:55 UTC | May 3, 13:30 UTC | 35m |
| 2026-05-02 | TTJ613 | - | May 2, 12:00 UTC | May 2, 12:40 UTC | 40m |
| 2026-04-28 | TTJ613 | - | Apr 28, 16:10 UTC | Apr 28, 18:20 UTC | 2h 10m |
| 2026-04-28 | TTJ613 | - | Apr 28, 06:20 UTC | Apr 28, 08:20 UTC | 2h 0m |
| 2026-04-21 | TTJ613 | PRG → BTS | Apr 21, 13:05 UTC | Apr 21, 13:40 UTC | 35m |
| 2026-04-21 | TTJ613 | BTS → PRG | Apr 21, 05:35 UTC | Apr 21, 06:05 UTC | 30m |
| 2026-04-16 | TTJ613 | - | Apr 16, 13:15 UTC | Apr 16, 13:50 UTC | 35m |
| 2026-04-16 | TTJ613 | - | Apr 16, 05:54 UTC | Apr 16, 06:29 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 OM-TAA page for operator, model, and routing details .