Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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
No current signal · last broadcast 1d ago
Flights observed
72
Distinct callsigns
2
Country
SK
Last broadcast
1d ago

Last known position

Most recent position reported by Mode-S 505E81.

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 2 distinct

Callsign Airline Flights Last seen
TTJ613 - 66 2026-07-26
TTJ603 - 6 2026-06-23

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 TTJ613 - Jul 26, 14:50 UTCJul 26, 16:45 UTC1h 55m
2026-07-26 TTJ613 BTS → ISL Jul 26, 05:55 UTCJul 26, 07:45 UTC1h 51m
2026-07-13 TTJ613 BER → BTS Jul 13, 21:10 UTCJul 13, 22:05 UTC55m
2026-07-13 TTJ613 - Jul 13, 11:55 UTCJul 13, 12:50 UTC55m
2026-07-12 TTJ613 - Jul 12, 18:15 UTCJul 12, 19:05 UTC50m
2026-07-12 TTJ613 BTS → PUY Jul 12, 16:35 UTCJul 12, 17:20 UTC45m
2026-07-10 TTJ613 - Jul 10, 10:45 UTCJul 10, 11:35 UTC50m
2026-07-10 TTJ613 - Jul 10, 08:05 UTCJul 10, 09:00 UTC55m
2026-07-06 TTJ613 NCE → BTS Jul 6, 16:40 UTCJul 6, 18:00 UTC1h 20m
2026-07-06 TTJ613 - Jul 6, 10:00 UTCJul 6, 10:35 UTC35m
2026-07-06 TTJ613 - Jul 6, 06:00 UTCJul 6, 07:15 UTC1h 15m
2026-07-04 TTJ613 - Jul 4, 11:45 UTCJul 4, 13:15 UTC1h 30m
2026-07-04 TTJ613 BTS → SKG Jul 4, 09:10 UTCJul 4, 10:40 UTC1h 30m
2026-07-03 TTJ613 - Jul 3, 13:15 UTCJul 3, 14:05 UTC50m
2026-07-03 TTJ613 BTS → VCE Jul 3, 11:00 UTCJul 3, 12:00 UTC1h 0m
2026-06-30 TTJ613 VIE → BTS Jun 30, 15:40 UTCJun 30, 15:50 UTC10m
2026-06-30 TTJ613 JER → VIE Jun 30, 12:35 UTCJun 30, 14:30 UTC1h 55m
2026-06-30 TTJ613 - Jun 30, 09:50 UTCJun 30, 10:40 UTC50m
2026-06-29 TTJ613 BOD → BQH Jun 29, 07:20 UTCJun 29, 08:35 UTC1h 15m
2026-06-28 TTJ613 VIE → BOD Jun 28, 10:30 UTCJun 28, 12:35 UTC2h 5m
2026-06-28 TTJ613 BTS → VIE Jun 28, 08:14 UTCJun 28, 08:34 UTC20m
2026-06-25 TTJ613 - Jun 25, 16:09 UTCJun 25, 16:45 UTC35m
2026-06-25 TTJ613 - Jun 25, 07:30 UTCJun 25, 08:04 UTC35m
2026-06-24 TTJ613 - Jun 24, 13:05 UTCJun 24, 15:24 UTC2h 20m
2026-06-24 TTJ613 - Jun 24, 09:29 UTCJun 24, 11:34 UTC2h 5m
2026-06-23 TTJ603 NCE → BTS Jun 23, 18:14 UTCJun 23, 19:39 UTC1h 25m
2026-06-22 TTJ603 BTS → NCE Jun 22, 07:34 UTCJun 22, 09:04 UTC1h 30m
2026-06-21 TTJ603 - Jun 21, 11:24 UTCJun 21, 12:40 UTC1h 15m
2026-06-21 TTJ603 - Jun 21, 07:55 UTCJun 21, 09:40 UTC1h 45m
2026-06-18 TTJ603 - Jun 18, 16:45 UTCJun 18, 18:25 UTC1h 40m
2026-06-18 TTJ603 BTS → GOA Jun 18, 14:35 UTCJun 18, 15:45 UTC1h 10m
2026-06-17 TTJ613 PRG → BTS Jun 17, 14:15 UTCJun 17, 14:55 UTC40m
2026-06-17 TTJ613 BTS → PRG Jun 17, 06:35 UTCJun 17, 07:15 UTC40m
2026-06-14 TTJ613 - Jun 14, 10:10 UTCJun 14, 10:45 UTC35m
2026-06-14 TTJ613 PUY → PED Jun 14, 08:25 UTCJun 14, 09:25 UTC1h 0m
2026-06-11 TTJ613 - Jun 11, 09:45 UTCJun 11, 10:05 UTC20m
2026-06-11 TTJ613 - Jun 11, 07:45 UTCJun 11, 08:35 UTC50m
2026-06-10 TTJ613 - Jun 10, 10:10 UTCJun 10, 10:50 UTC40m
2026-06-10 TTJ613 - Jun 10, 08:10 UTCJun 10, 09:15 UTC1h 5m
2026-06-10 TTJ613 BTS → PED Jun 10, 06:10 UTCJun 10, 06:35 UTC25m
2026-06-09 TTJ613 PRG → BTS Jun 9, 13:35 UTCJun 9, 14:15 UTC40m
2026-06-09 TTJ613 - Jun 9, 06:20 UTCJun 9, 06:55 UTC35m
2026-06-05 TTJ613 BRQ → BTS Jun 5, 20:35 UTCJun 5, 20:50 UTC15m
2026-06-05 TTJ613 LBG → BRQ Jun 5, 18:15 UTCJun 5, 19:40 UTC1h 25m
2026-06-05 TTJ613 BRQ → LBG Jun 5, 07:10 UTCJun 5, 08:50 UTC1h 40m
2026-06-05 TTJ613 VIE → BRQ Jun 5, 05:50 UTCJun 5, 06:10 UTC20m
2026-05-30 TTJ613 - May 30, 10:00 UTCMay 30, 11:55 UTC1h 55m
2026-05-30 TTJ613 - May 30, 07:30 UTCMay 30, 08:25 UTC55m
2026-05-28 TTJ613 - May 28, 18:10 UTCMay 28, 18:55 UTC45m
2026-05-28 TTJ613 - May 28, 15:35 UTCMay 28, 17:25 UTC1h 50m

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 .

Mode-S 505E81 frequently asked

What is Mode-S code 505E81?
505E81 is an ICAO 24-bit transponder address. Allocated to Slovakia. Assigned to OM-TAA.
Where is Mode-S 505E81 registered?
Mode-S code 505E81 is allocated to Slovakia (SK). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 505E81 broadcasting right now?
No active broadcast right now. Last signal was 1d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 505E81, octal 24057201, decimal 5,267,073.
What flights does 505E81 operate?
Mode-S 505E81 has broadcast 2 distinct callsigns, including TTJ613, TTJ603.