sensors Mode-S transponder
151D85
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73093 · BOEING 737-800
- Hex
- 151D85
- Octal
- 05216605
- Decimal
- 1,383,813
- Country
- RU
- Tail
- RA-73093
- Type
- B738
- Flights observed
- 232
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 13:25 UTC
Last known position
Country allocation
The ICAO 24-bit address 151D85 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFL814 | - | 31 | 2026-07-13 |
| AFL644 | - | 27 | 2026-07-12 |
| AFL856 | - | 24 | 2026-07-23 |
| AFL851 | Aeroflot Russian Airlines | 22 | 2026-07-25 |
| AFL850 | - | 22 | 2026-07-18 |
| AFL857 | - | 17 | 2026-06-30 |
| AFL645 | - | 16 | 2026-07-13 |
| AFL853 | Aeroflot Russian Airlines | 11 | 2026-07-25 |
| AFL815 | - | 8 | 2026-07-12 |
| AFL852 | Aeroflot Russian Airlines | 6 | 2026-07-26 |
| AFL2124 | - | 5 | 2026-07-03 |
| AFL1460 | Aeroflot Russian Airlines | 4 | 2026-06-04 |
| AFL1869 | Aeroflot Russian Airlines | 3 | 2026-06-15 |
| AFL7779 | - | 2 | 2026-07-14 |
| AFL7775 | Aeroflot Russian Airlines | 2 | 2026-04-28 |
| AFL521 | Aeroflot Russian Airlines | 2 | 2026-06-24 |
| AFL2125 | - | 2 | 2026-07-03 |
| AFL2122 | - | 2 | 2026-07-14 |
| AFL1481 | Aeroflot Russian Airlines | 2 | 2026-04-22 |
| AFL1480 | Aeroflot Russian Airlines | 2 | 2026-04-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL852 | OVB → SYX | Jul 26, 13:00 UTC | Jul 26, 13:25 UTC | 25m |
| 2026-07-25 | AFL853 | SYX → OVB | Jul 25, 14:30 UTC | Jul 26, 02:35 UTC | 12h 5m |
| 2026-07-25 | AFL851 | SYX → KHV | Jul 25, 01:20 UTC | Jul 25, 20:55 UTC | 19h 35m |
| 2026-07-24 | AFL851 | SYX → KHV | Jul 24, 23:25 UTC | Jul 25, 20:55 UTC | 21h 30m |
| 2026-07-24 | AFL851 | SYX → KHV | Jul 24, 15:50 UTC | Jul 25, 14:40 UTC | 22h 50m |
| 2026-07-24 | AFL851 | SYX → KHV | Jul 24, 13:15 UTC | Jul 25, 02:00 UTC | 12h 45m |
| 2026-07-23 | AFL856 | - | Jul 23, 21:25 UTC | Jul 24, 16:05 UTC | 18h 40m |
| 2026-07-23 | AFL856 | - | Jul 23, 17:45 UTC | Jul 24, 16:05 UTC | 22h 20m |
| 2026-07-21 | AFL1752 | SVO → YKS | Jul 21, 19:20 UTC | Jul 21, 19:35 UTC | 15m |
| 2026-07-19 | AFL853 | SYX → OVB | Jul 19, 12:40 UTC | Jul 20, 02:40 UTC | 14h 0m |
| 2026-07-18 | AFL850 | - | Jul 18, 14:45 UTC | Jul 19, 03:00 UTC | 12h 15m |
| 2026-07-18 | AFL850 | - | Jul 18, 01:25 UTC | Jul 18, 17:30 UTC | 16h 6m |
| 2026-07-17 | AFL850 | - | Jul 17, 23:00 UTC | Jul 18, 17:30 UTC | 18h 31m |
| 2026-07-17 | AFL851 | - | Jul 17, 15:44 UTC | Jul 18, 15:05 UTC | 23h 21m |
| 2026-07-17 | AFL856 | - | Jul 17, 13:25 UTC | Jul 18, 01:39 UTC | 12h 15m |
| 2026-07-17 | AFL856 | - | Jul 17, 00:04 UTC | Jul 17, 23:14 UTC | 23h 10m |
| 2026-07-16 | AFL856 | - | Jul 16, 21:45 UTC | Jul 17, 16:00 UTC | 18h 15m |
| 2026-07-16 | AFL852 | - | Jul 16, 12:44 UTC | Jul 17, 00:20 UTC | 11h 35m |
| 2026-07-15 | AFL2123 | - | Jul 15, 15:05 UTC | Jul 15, 16:50 UTC | 1h 45m |
| 2026-07-14 | AFL2122 | - | Jul 14, 20:40 UTC | Jul 15, 13:35 UTC | 16h 54m |
| 2026-07-14 | AFL2122 | - | Jul 14, 17:45 UTC | Jul 15, 13:35 UTC | 19h 49m |
| 2026-07-14 | AFL7779 | - | Jul 14, 01:45 UTC | Jul 14, 21:05 UTC | 19h 20m |
| 2026-07-13 | AFL7779 | - | Jul 13, 20:15 UTC | Jul 14, 18:25 UTC | 22h 10m |
| 2026-07-13 | AFL856 | - | Jul 13, 09:20 UTC | Jul 14, 04:30 UTC | 19h 10m |
| 2026-07-13 | AFL856 | - | Jul 13, 09:10 UTC | Jul 14, 04:30 UTC | 19h 20m |
| 2026-07-13 | AFL645 | - | Jul 13, 08:01 UTC | Jul 13, 08:15 UTC | 15m |
| 2026-07-13 | AFL814 | - | Jul 13, 05:55 UTC | Jul 13, 06:05 UTC | 10m |
| 2026-07-12 | AFL814 | - | Jul 12, 10:15 UTC | Jul 13, 05:10 UTC | 18h 55m |
| 2026-07-12 | AFL815 | - | Jul 12, 09:05 UTC | Jul 12, 09:20 UTC | 15m |
| 2026-07-12 | AFL644 | - | Jul 12, 07:10 UTC | Jul 12, 07:25 UTC | 15m |
| 2026-07-11 | AFL644 | - | Jul 11, 12:45 UTC | Jul 12, 06:05 UTC | 17h 20m |
| 2026-07-11 | AFL644 | - | Jul 11, 09:50 UTC | Jul 12, 06:05 UTC | 20h 15m |
| 2026-07-11 | AFL645 | - | Jul 11, 08:25 UTC | Jul 11, 08:35 UTC | 10m |
| 2026-07-11 | AFL814 | - | Jul 11, 04:45 UTC | Jul 11, 06:10 UTC | 1h 25m |
| 2026-07-10 | AFL814 | - | Jul 10, 09:20 UTC | Jul 11, 06:10 UTC | 20h 50m |
| 2026-07-10 | AFL814 | - | Jul 10, 04:40 UTC | Jul 10, 06:10 UTC | 1h 30m |
| 2026-07-09 | AFL814 | - | Jul 9, 09:20 UTC | Jul 10, 06:10 UTC | 20h 50m |
| 2026-07-09 | AFL644 | - | Jul 9, 02:55 UTC | Jul 9, 07:25 UTC | 4h 30m |
| 2026-07-08 | AFL644 | - | Jul 8, 09:50 UTC | Jul 9, 07:25 UTC | 21h 35m |
| 2026-07-08 | AFL644 | - | Jul 8, 07:20 UTC | Jul 9, 07:15 UTC | 23h 55m |
| 2026-07-08 | AFL645 | - | Jul 8, 05:25 UTC | Jul 9, 03:20 UTC | 21h 55m |
| 2026-07-06 | AFL1477 | - | Jul 6, 18:45 UTC | Jul 7, 01:45 UTC | 7h 0m |
| 2026-07-05 | AFL2169 | - | Jul 5, 17:35 UTC | Jul 5, 19:25 UTC | 1h 50m |
| 2026-07-04 | AFL2168 | SVO → DLM | Jul 4, 23:05 UTC | Jul 5, 15:55 UTC | 16h 50m |
| 2026-07-03 | AFL2125 | - | Jul 3, 13:20 UTC | Jul 3, 15:05 UTC | 1h 45m |
| 2026-07-03 | AFL2124 | - | Jul 3, 11:30 UTC | Jul 3, 11:55 UTC | 25m |
| 2026-07-03 | AFL2124 | - | Jul 3, 10:15 UTC | Jul 3, 10:50 UTC | 35m |
| 2026-07-01 | AFL856 | - | Jul 1, 13:10 UTC | Jul 2, 02:55 UTC | 13h 45m |
| 2026-06-30 | AFL857 | - | Jun 30, 23:05 UTC | Jul 1, 15:55 UTC | 16h 50m |
| 2026-06-30 | AFL857 | - | Jun 30, 16:25 UTC | Jul 1, 13:25 UTC | 21h 0m |
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-73093 page for operator, model, and routing details .