Apparatus

Try JFK, AAL1290, BAW, or N225AN.

sensors Mode-S transponder

1505F6

ICAO 24-bit transponder address · allocated to Russia

Currently assigned to RA-67062 · LET L-410 Turbolet

Hex
1505F6
Octal
05202766
Decimal
1,377,782
Country
RU
Tail
RA-67062
Type
L410
No current signal · last broadcast 2d ago
Flights observed
59
Distinct callsigns
8
Country
RU
Last broadcast
2d ago

Last known position

Most recent position reported by Mode-S 1505F6.

Country allocation

The ICAO 24-bit address 1505F6 falls within the block assigned to Russia (RU) by ICAO Annex 10, Volume III. Every aircraft registered in Russia 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 8 distinct

Callsign Airline Flights Last seen
OAO9101 - 31 2026-07-15
OAO9102 - 17 2026-07-15
OAO9103 - 5 2026-06-25
OAO9104 - 2 2026-06-20
OAO9105 - 1 2026-06-05
OAO688 - 1 2026-07-03
OAO687 - 1 2026-07-03
OAO0000 - 1 2026-04-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-15 OAO9102 SVO → SVO Jul 15, 11:45 UTCJul 15, 12:20 UTC35m
2026-07-15 OAO9101 VKV → VKV Jul 15, 06:55 UTCJul 15, 07:40 UTC45m
2026-07-14 OAO9101 - Jul 14, 13:45 UTCJul 14, 14:25 UTC40m
2026-07-10 OAO9101 - Jul 10, 08:20 UTCJul 10, 08:40 UTC20m
2026-07-09 OAO9101 VKV → VKV Jul 9, 06:55 UTCJul 9, 07:40 UTC45m
2026-07-08 OAO9101 VKV → VKV Jul 8, 08:10 UTCJul 8, 08:50 UTC40m
2026-07-06 OAO9102 LED → LED Jul 6, 10:35 UTCJul 6, 11:10 UTC35m
2026-07-06 OAO9101 VKV → VKV Jul 6, 06:55 UTCJul 6, 07:35 UTC40m
2026-07-04 OAO9101 VKV → VKV Jul 4, 08:25 UTCJul 4, 09:05 UTC40m
2026-07-03 OAO9101 VKV → VKV Jul 3, 11:35 UTCJul 3, 12:10 UTC35m
2026-07-03 OAO688 - Jul 3, 09:15 UTCJul 3, 10:00 UTC45m
2026-07-03 OAO687 VKV → VKV Jul 3, 07:35 UTCJul 3, 08:05 UTC30m
2026-07-02 OAO9102 - Jul 2, 18:15 UTCJul 2, 18:55 UTC40m
2026-07-02 OAO9101 - Jul 2, 13:40 UTCJul 2, 14:25 UTC45m
2026-06-26 OAO9101 VKV → VKV Jun 26, 11:45 UTCJun 26, 12:19 UTC35m
2026-06-25 OAO9103 - Jun 25, 13:24 UTCJun 25, 13:45 UTC20m
2026-06-25 OAO9101 - Jun 25, 08:40 UTCJun 25, 09:29 UTC50m
2026-06-24 OAO9102 - Jun 24, 15:39 UTCJun 24, 16:19 UTC40m
2026-06-22 OAO9102 - Jun 22, 12:44 UTCJun 22, 13:29 UTC45m
2026-06-22 OAO9101 VKV → VKV Jun 22, 08:04 UTCJun 22, 08:44 UTC40m
2026-06-20 OAO9104 - Jun 20, 17:34 UTCJun 20, 18:14 UTC40m
2026-06-20 OAO9103 VKV → VKV Jun 20, 12:45 UTCJun 20, 13:24 UTC40m
2026-06-20 OAO9101 VKV → VKV Jun 20, 08:05 UTCJun 20, 08:34 UTC30m
2026-06-18 OAO9101 - Jun 18, 19:15 UTCJun 18, 19:25 UTC10m
2026-06-18 OAO9101 VKV → VKV Jun 18, 17:50 UTCJun 18, 18:25 UTC35m
2026-06-17 OAO9102 LED → LED Jun 17, 09:50 UTCJun 17, 10:30 UTC40m
2026-06-17 OAO9101 - Jun 17, 06:55 UTCJun 17, 07:10 UTC15m
2026-06-15 OAO9102 - Jun 15, 13:25 UTCJun 15, 14:10 UTC45m
2026-06-08 OAO9101 VKV → VKV Jun 8, 09:35 UTCJun 8, 10:00 UTC25m
2026-06-06 OAO9101 VKV → VKV Jun 6, 14:04 UTCJun 6, 14:34 UTC30m
2026-06-05 OAO9105 - Jun 5, 18:15 UTCJun 5, 19:00 UTC45m
2026-06-05 OAO9101 VKV → VKV Jun 5, 08:25 UTCJun 5, 09:00 UTC35m
2026-06-03 OAO9103 - Jun 3, 15:20 UTCJun 3, 16:00 UTC40m
2026-06-03 OAO9101 VKV → VKV Jun 3, 09:10 UTCJun 3, 09:25 UTC15m
2026-06-02 OAO9102 LED → LED Jun 2, 11:25 UTCJun 2, 11:55 UTC30m
2026-05-30 OAO9101 VKV → VKV May 30, 07:15 UTCMay 30, 07:55 UTC40m
2026-05-26 OAO9104 - May 26, 20:05 UTCMay 26, 20:50 UTC45m
2026-05-26 OAO9102 SVO → SVO May 26, 11:20 UTCMay 26, 11:50 UTC30m
2026-05-21 OAO9101 VKV → VKV May 21, 06:50 UTCMay 21, 07:30 UTC40m
2026-05-19 OAO9102 - May 19, 18:15 UTCMay 19, 19:05 UTC50m
2026-05-17 OAO9102 - May 17, 13:50 UTCMay 17, 14:30 UTC40m
2026-05-14 OAO9102 - May 14, 14:05 UTCMay 14, 15:01 UTC55m
2026-05-13 OAO9103 VKV → VKV May 13, 14:20 UTCMay 13, 14:51 UTC30m
2026-05-13 OAO9101 VKV → VKV May 13, 06:50 UTCMay 13, 07:35 UTC45m
2026-05-07 OAO9101 VKV → VKV May 7, 08:40 UTCMay 7, 09:20 UTC40m
2026-05-06 OAO9103 VKV → VKV May 6, 14:30 UTCMay 6, 15:10 UTC40m
2026-05-06 OAO9102 SVO → SVO May 6, 10:35 UTCMay 6, 11:00 UTC25m
2026-05-02 OAO9101 VKV → VKV May 2, 08:35 UTCMay 2, 09:10 UTC35m
2026-04-24 OAO9102 - Apr 24, 17:35 UTCApr 24, 18:30 UTC55m
2026-04-24 OAO9101 VKV → VKV Apr 24, 11:25 UTCApr 24, 12:10 UTC45m

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 RA-67062 page for operator, model, and routing details .

Mode-S 1505F6 frequently asked

What is Mode-S code 1505F6?
1505F6 is an ICAO 24-bit transponder address. Allocated to Russia. Assigned to RA-67062.
Where is Mode-S 1505F6 registered?
Mode-S code 1505F6 is allocated to Russia (RU). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 1505F6 broadcasting right now?
No active broadcast right now. Last signal was 2d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 1505F6, octal 05202766, decimal 1,377,782.
What flights does 1505F6 operate?
Mode-S 1505F6 has broadcast 8 distinct callsigns, including OAO9101, OAO9102, OAO9103, OAO9104, OAO9105.