sensors Mode-S transponder
151D94
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73108 · BOEING 737-800
- Hex
- 151D94
- Octal
- 05216624
- Decimal
- 1,383,828
- Country
- RU
- Tail
- RA-73108
- Type
- B738
- Flights observed
- 272
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 12:55 UTC
Last known position
Country allocation
The ICAO 24-bit address 151D94 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 |
|---|---|---|---|
| AFL913 | Aeroflot Russian Airlines | 18 | 2026-07-24 |
| AFL423 | Aeroflot Russian Airlines | 17 | 2026-06-07 |
| AFL909 | Aeroflot Russian Airlines | 16 | 2026-07-23 |
| AFL427 | Aeroflot Russian Airlines | 15 | 2026-06-17 |
| AFL912 | Aeroflot Russian Airlines | 14 | 2026-07-24 |
| AFL802 | - | 10 | 2026-07-14 |
| AFL2149 | - | 10 | 2026-07-11 |
| AFL426 | - | 9 | 2026-06-16 |
| AFL2124 | - | 9 | 2026-07-16 |
| AFL2123 | - | 9 | 2026-07-09 |
| AFL677 | - | 8 | 2026-07-15 |
| AFL2148 | - | 8 | 2026-07-05 |
| AFL2122 | - | 8 | 2026-07-09 |
| AFL803 | - | 7 | 2026-07-15 |
| AFL676 | - | 7 | 2026-07-15 |
| AFL419 | Aeroflot Russian Airlines | 7 | 2026-06-24 |
| AFL2121 | - | 7 | 2026-07-21 |
| AFL917 | - | 5 | 2026-06-23 |
| AFL908 | Aeroflot Russian Airlines | 5 | 2026-06-16 |
| AFL428 | Aeroflot Russian Airlines | 5 | 2026-05-14 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL745 | AYT → KZN | Jul 26, 01:40 UTC | Jul 26, 12:55 UTC | 11h 16m |
| 2026-07-24 | AFL913 | SSH → KZN | Jul 24, 19:05 UTC | Jul 25, 14:30 UTC | 19h 25m |
| 2026-07-24 | AFL913 | SSH → KZN | Jul 24, 18:40 UTC | Jul 25, 14:30 UTC | 19h 50m |
| 2026-07-24 | AFL912 | KZN → SSH | Jul 24, 15:05 UTC | Jul 24, 16:25 UTC | 1h 20m |
| 2026-07-23 | AFL912 | KZN → SSH | Jul 23, 19:05 UTC | Jul 24, 16:25 UTC | 21h 20m |
| 2026-07-23 | AFL909 | HRG → KZN | Jul 23, 17:05 UTC | Jul 24, 16:25 UTC | 23h 20m |
| 2026-07-23 | AFL909 | HRG → KZN | Jul 23, 14:25 UTC | Jul 23, 19:20 UTC | 4h 55m |
| 2026-07-22 | AFL913 | - | Jul 22, 17:05 UTC | Jul 23, 17:00 UTC | 23h 55m |
| 2026-07-22 | AFL913 | - | Jul 22, 15:05 UTC | Jul 23, 14:25 UTC | 23h 20m |
| 2026-07-21 | AFL2121 | - | Jul 21, 11:20 UTC | Jul 21, 12:00 UTC | 40m |
| 2026-07-20 | AFL2120 | SVO → BJV | Jul 20, 16:10 UTC | Jul 21, 09:55 UTC | 17h 45m |
| 2026-07-20 | AFL2129 | AYT → SVO | Jul 20, 03:50 UTC | Jul 20, 14:45 UTC | 10h 55m |
| 2026-07-20 | AFL2128 | SVO → AYT | Jul 20, 02:10 UTC | Jul 20, 02:35 UTC | 25m |
| 2026-07-19 | AFL2159 | - | Jul 19, 14:55 UTC | Jul 19, 15:20 UTC | 25m |
| 2026-07-19 | AFL2158 | SVO → AYT | Jul 19, 11:35 UTC | Jul 19, 12:10 UTC | 35m |
| 2026-07-19 | AFL2158 | SVO → AYT | Jul 19, 08:30 UTC | Jul 19, 09:05 UTC | 35m |
| 2026-07-19 | AFL2133 | IST → SVO | Jul 19, 01:20 UTC | Jul 19, 01:50 UTC | 30m |
| 2026-07-18 | AFL2121 | - | Jul 18, 11:30 UTC | Jul 18, 13:30 UTC | 2h 0m |
| 2026-07-18 | AFL2120 | - | Jul 18, 09:20 UTC | Jul 18, 10:05 UTC | 45m |
| 2026-07-17 | AFL1967 | - | Jul 17, 03:34 UTC | Jul 17, 03:55 UTC | 20m |
| 2026-07-16 | AFL2125 | - | Jul 16, 13:10 UTC | Jul 16, 14:50 UTC | 1h 40m |
| 2026-07-16 | AFL2124 | SVO → AYT | Jul 16, 06:40 UTC | Jul 16, 11:34 UTC | 4h 55m |
| 2026-07-15 | AFL803 | - | Jul 15, 15:45 UTC | Jul 16, 01:55 UTC | 10h 10m |
| 2026-07-15 | AFL676 | - | Jul 15, 13:10 UTC | Jul 15, 13:50 UTC | 40m |
| 2026-07-15 | AFL677 | - | Jul 15, 07:30 UTC | Jul 15, 08:50 UTC | 1h 20m |
| 2026-07-14 | AFL802 | - | Jul 14, 17:30 UTC | Jul 15, 04:00 UTC | 10h 29m |
| 2026-07-14 | AFL802 | - | Jul 14, 06:25 UTC | Jul 15, 04:00 UTC | 21h 34m |
| 2026-07-13 | AFL2125 | - | Jul 13, 13:25 UTC | Jul 14, 05:10 UTC | 15h 45m |
| 2026-07-13 | AFL2124 | - | Jul 13, 09:15 UTC | Jul 13, 11:00 UTC | 1h 45m |
| 2026-07-12 | AFL2124 | - | Jul 12, 13:40 UTC | Jul 13, 11:00 UTC | 21h 20m |
| 2026-07-12 | AFL676 | - | Jul 12, 11:45 UTC | Jul 12, 12:10 UTC | 25m |
| 2026-07-12 | AFL677 | - | Jul 12, 06:20 UTC | Jul 12, 06:50 UTC | 30m |
| 2026-07-12 | AFL802 | - | Jul 12, 03:45 UTC | Jul 12, 04:20 UTC | 35m |
| 2026-07-11 | AFL2149 | - | Jul 11, 06:05 UTC | Jul 11, 07:45 UTC | 1h 40m |
| 2026-07-10 | AFL2161 | - | Jul 10, 16:05 UTC | Jul 11, 04:30 UTC | 12h 26m |
| 2026-07-10 | AFL2160 | - | Jul 10, 14:15 UTC | Jul 10, 14:45 UTC | 30m |
| 2026-07-09 | AFL2123 | - | Jul 9, 14:35 UTC | Jul 9, 16:25 UTC | 1h 50m |
| 2026-07-09 | AFL2122 | - | Jul 9, 12:45 UTC | Jul 9, 13:05 UTC | 20m |
| 2026-07-09 | AFL2122 | SVO → SVO | Jul 9, 08:20 UTC | Jul 9, 08:55 UTC | 35m |
| 2026-07-08 | AFL431 | - | Jul 8, 18:15 UTC | Jul 8, 21:00 UTC | 2h 45m |
| 2026-07-08 | AFL430 | - | Jul 8, 14:00 UTC | Jul 8, 15:30 UTC | 1h 30m |
| 2026-07-07 | AFL803 | - | Jul 7, 13:45 UTC | Jul 7, 14:05 UTC | 20m |
| 2026-07-07 | AFL676 | - | Jul 7, 06:10 UTC | Jul 7, 12:20 UTC | 6h 10m |
| 2026-07-06 | AFL803 | - | Jul 6, 13:35 UTC | Jul 7, 03:30 UTC | 13h 55m |
| 2026-07-06 | AFL676 | - | Jul 6, 11:00 UTC | Jul 6, 12:05 UTC | 1h 5m |
| 2026-07-06 | AFL677 | - | Jul 6, 06:35 UTC | Jul 6, 08:00 UTC | 1h 25m |
| 2026-07-06 | AFL802 | - | Jul 6, 02:50 UTC | Jul 6, 03:35 UTC | 45m |
| 2026-07-05 | AFL2149 | - | Jul 5, 05:40 UTC | Jul 6, 03:00 UTC | 21h 20m |
| 2026-07-05 | AFL2148 | - | Jul 5, 03:40 UTC | Jul 5, 04:00 UTC | 20m |
| 2026-07-04 | AFL2129 | AYT → SVO | Jul 4, 13:35 UTC | Jul 4, 15:20 UTC | 1h 45m |
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-73108 page for operator, model, and routing details .