sensors Mode-S transponder
151D9A
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73114 · BOEING 737-800
- Hex
- 151D9A
- Octal
- 05216632
- Decimal
- 1,383,834
- Country
- RU
- Tail
- RA-73114
- Type
- B738
- Flights observed
- 141
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 18h ago
Last known position
Country allocation
The ICAO 24-bit address 151D9A 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 |
|---|---|---|---|
| AFL400 | - | 11 | 2026-06-24 |
| AFL401 | Aeroflot Russian Airlines | 9 | 2026-06-24 |
| AFL521 | - | 8 | 2026-07-11 |
| AFL2139 | - | 8 | 2026-07-12 |
| AFL2138 | - | 8 | 2026-07-12 |
| AFL526 | - | 7 | 2026-07-08 |
| AFL520 | - | 5 | 2026-07-11 |
| AFL2121 | Aeroflot Russian Airlines | 5 | 2026-06-18 |
| AFL2120 | Aeroflot Russian Airlines | 5 | 2026-06-18 |
| AFL2127 | Aeroflot Russian Airlines | 4 | 2026-07-01 |
| AFL2126 | - | 4 | 2026-07-01 |
| AFL2124 | Aeroflot Russian Airlines | 4 | 2026-04-18 |
| AFL527 | - | 3 | 2026-07-08 |
| AFL2132 | - | 3 | 2026-06-30 |
| AFL2123 | - | 3 | 2026-06-29 |
| AFL2122 | - | 3 | 2026-06-29 |
| AFL1869 | Aeroflot Russian Airlines | 3 | 2026-06-04 |
| AFL1863 | Aeroflot Russian Airlines | 3 | 2026-05-29 |
| AFL1862 | Aeroflot Russian Airlines | 3 | 2026-05-29 |
| AFL438 | Aeroflot Russian Airlines | 2 | 2026-06-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFL2161 | - | Jul 13, 15:55 UTC | Jul 13, 17:40 UTC | 1h 45m |
| 2026-07-13 | AFL2160 | - | Jul 13, 13:50 UTC | Jul 13, 14:25 UTC | 35m |
| 2026-07-12 | AFL2139 | - | Jul 12, 06:15 UTC | Jul 12, 06:45 UTC | 30m |
| 2026-07-12 | AFL2138 | - | Jul 12, 01:20 UTC | Jul 12, 01:30 UTC | 10m |
| 2026-07-11 | AFL521 | - | Jul 11, 18:00 UTC | Jul 11, 18:25 UTC | 25m |
| 2026-07-11 | AFL521 | - | Jul 11, 12:30 UTC | Jul 11, 17:25 UTC | 4h 55m |
| 2026-07-11 | AFL520 | - | Jul 11, 10:05 UTC | Jul 11, 10:30 UTC | 25m |
| 2026-07-10 | AFL520 | - | Jul 10, 09:35 UTC | Jul 10, 10:00 UTC | 25m |
| 2026-07-09 | AFL1518 | SVO → RGK | Jul 9, 06:55 UTC | Jul 9, 07:10 UTC | 15m |
| 2026-07-08 | AFL527 | - | Jul 8, 16:15 UTC | Jul 8, 16:25 UTC | 10m |
| 2026-07-08 | AFL526 | - | Jul 8, 13:35 UTC | Jul 8, 14:05 UTC | 30m |
| 2026-07-07 | AFL526 | - | Jul 7, 16:05 UTC | Jul 8, 14:05 UTC | 22h 0m |
| 2026-07-07 | AFL521 | - | Jul 7, 12:40 UTC | Jul 7, 16:10 UTC | 3h 30m |
| 2026-07-06 | AFL527 | - | Jul 6, 16:00 UTC | Jul 6, 19:35 UTC | 3h 35m |
| 2026-07-05 | AFL526 | - | Jul 5, 19:30 UTC | Jul 6, 14:10 UTC | 18h 40m |
| 2026-07-05 | AFL526 | - | Jul 5, 16:35 UTC | Jul 6, 14:10 UTC | 21h 35m |
| 2026-07-05 | AFL527 | - | Jul 5, 16:05 UTC | Jul 6, 14:10 UTC | 22h 5m |
| 2026-07-05 | AFL526 | - | Jul 5, 13:35 UTC | Jul 5, 14:05 UTC | 30m |
| 2026-07-05 | AFL526 | SVO → SVO | Jul 5, 08:20 UTC | Jul 5, 09:05 UTC | 45m |
| 2026-07-04 | AFL2139 | - | Jul 4, 06:05 UTC | Jul 4, 06:35 UTC | 30m |
| 2026-07-04 | AFL2138 | - | Jul 4, 04:00 UTC | Jul 4, 04:25 UTC | 25m |
| 2026-07-03 | AFL521 | DXB → SVO | Jul 3, 12:40 UTC | Jul 3, 16:10 UTC | 3h 30m |
| 2026-07-02 | AFL520 | - | Jul 2, 16:05 UTC | Jul 3, 09:55 UTC | 17h 50m |
| 2026-07-02 | AFL526 | - | Jul 2, 13:35 UTC | Jul 2, 14:00 UTC | 25m |
| 2026-07-01 | AFL2127 | AYT → SVO | Jul 1, 14:35 UTC | Jul 2, 14:00 UTC | 23h 25m |
| 2026-07-01 | AFL2127 | AYT → SVO | Jul 1, 14:20 UTC | Jul 1, 16:10 UTC | 1h 50m |
| 2026-07-01 | AFL2126 | - | Jul 1, 01:35 UTC | Jul 1, 12:35 UTC | 11h 0m |
| 2026-06-30 | AFL2132 | - | Jun 30, 23:45 UTC | Jun 30, 23:55 UTC | 10m |
| 2026-06-29 | AFL2123 | - | Jun 29, 14:34 UTC | Jun 29, 16:25 UTC | 1h 50m |
| 2026-06-29 | AFL2122 | - | Jun 29, 12:05 UTC | Jun 29, 12:45 UTC | 40m |
| 2026-06-29 | AFL2133 | - | Jun 29, 01:10 UTC | Jun 29, 01:39 UTC | 30m |
| 2026-06-28 | AFL2132 | - | Jun 28, 22:29 UTC | Jun 28, 22:49 UTC | 20m |
| 2026-06-27 | AFL435 | - | Jun 27, 18:15 UTC | Jun 28, 12:25 UTC | 18h 10m |
| 2026-06-27 | AFL1832 | SVO → MSQ | Jun 27, 16:04 UTC | Jun 27, 16:20 UTC | 15m |
| 2026-06-26 | AFL2169 | DLM → SVO | Jun 26, 17:19 UTC | Jun 26, 19:09 UTC | 1h 50m |
| 2026-06-25 | AFL521 | DXB → SVO | Jun 25, 12:19 UTC | Jun 25, 12:44 UTC | 25m |
| 2026-06-24 | AFL401 | CAI → SVO | Jun 24, 14:39 UTC | Jun 25, 10:09 UTC | 19h 30m |
| 2026-06-24 | AFL400 | - | Jun 24, 10:49 UTC | Jun 24, 12:50 UTC | 2h 0m |
| 2026-06-24 | AFL400 | SVO → SVO | Jun 24, 07:30 UTC | Jun 24, 07:50 UTC | 20m |
| 2026-06-21 | AFL521 | DXB → SVO | Jun 21, 12:35 UTC | Jun 21, 12:49 UTC | 15m |
| 2026-06-21 | AFL520 | SVO → DXB | Jun 21, 09:55 UTC | Jun 21, 10:04 UTC | 10m |
| 2026-06-20 | AFL521 | DXB → SVO | Jun 20, 12:24 UTC | Jun 20, 12:39 UTC | 15m |
| 2026-06-20 | AFL520 | SVO → DXB | Jun 20, 09:59 UTC | Jun 20, 10:09 UTC | 10m |
| 2026-06-19 | AFL401 | CAI → SVO | Jun 19, 14:54 UTC | Jun 19, 17:19 UTC | 2h 25m |
| 2026-06-18 | AFL400 | - | Jun 18, 18:35 UTC | Jun 19, 12:44 UTC | 18h 9m |
| 2026-06-18 | AFL2121 | BJV → SVO | Jun 18, 18:10 UTC | Jun 19, 12:44 UTC | 18h 34m |
| 2026-06-18 | AFL2120 | SVO → BJV | Jun 18, 16:15 UTC | Jun 18, 16:45 UTC | 30m |
| 2026-06-18 | AFL2120 | SVO → BJV | Jun 18, 11:30 UTC | Jun 18, 11:45 UTC | 15m |
| 2026-06-14 | AFL2139 | - | Jun 14, 06:20 UTC | Jun 14, 06:50 UTC | 30m |
| 2026-06-14 | AFL2138 | SVO → IST | Jun 14, 01:15 UTC | Jun 14, 01:30 UTC | 15m |
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-73114 page for operator, model, and routing details .