sensors Mode-S transponder
151D88
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73096 · BOEING 737-800
- Hex
- 151D88
- Octal
- 05216610
- Decimal
- 1,383,816
- Country
- RU
- Tail
- RA-73096
- Type
- B738
- Flights observed
- 178
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 21:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 151D88 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 |
|---|---|---|---|
| AFL856 | - | 34 | 2026-07-22 |
| AFL850 | Aeroflot Russian Airlines | 24 | 2026-07-26 |
| AFL857 | - | 15 | 2026-07-19 |
| AFL851 | Aeroflot Russian Airlines | 13 | 2026-07-25 |
| AFL852 | - | 11 | 2026-07-18 |
| AFL644 | - | 11 | 2026-07-06 |
| AFL814 | - | 6 | 2026-06-28 |
| AFL400 | Aeroflot Russian Airlines | 5 | 2026-05-29 |
| AFL1444 | Aeroflot Russian Airlines | 4 | 2026-05-01 |
| AFL853 | - | 3 | 2026-06-17 |
| AFL815 | - | 3 | 2026-07-07 |
| AFL1480 | - | 3 | 2026-06-23 |
| AFL1460 | - | 3 | 2026-07-02 |
| AFL623 | Aeroflot Russian Airlines | 2 | 2026-04-13 |
| AFL401 | Aeroflot Russian Airlines | 2 | 2026-05-29 |
| AFL2169 | Aeroflot Russian Airlines | 2 | 2026-06-05 |
| AFL2157 | - | 2 | 2026-07-08 |
| AFL2133 | - | 2 | 2026-06-19 |
| AFL1869 | Aeroflot Russian Airlines | 2 | 2026-06-09 |
| AFL1868 | Aeroflot Russian Airlines | 2 | 2026-06-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL850 | KHV → SYX | Jul 26, 00:00 UTC | Jul 26, 21:45 UTC | 21h 46m |
| 2026-07-25 | AFL850 | KHV → SYX | Jul 25, 21:35 UTC | Jul 26, 17:20 UTC | 19h 46m |
| 2026-07-25 | AFL851 | SYX → KHV | Jul 25, 17:55 UTC | Jul 26, 15:00 UTC | 21h 6m |
| 2026-07-25 | AFL851 | SYX → KHV | Jul 25, 13:00 UTC | Jul 26, 00:15 UTC | 11h 15m |
| 2026-07-22 | AFL856 | - | Jul 22, 13:15 UTC | Jul 23, 02:50 UTC | 13h 35m |
| 2026-07-21 | AFL856 | - | Jul 21, 23:15 UTC | Jul 22, 15:55 UTC | 16h 40m |
| 2026-07-21 | AFL856 | - | Jul 21, 16:40 UTC | Jul 22, 15:55 UTC | 23h 15m |
| 2026-07-21 | AFL850 | - | Jul 21, 14:10 UTC | Jul 22, 13:35 UTC | 23h 25m |
| 2026-07-20 | AFL850 | - | Jul 20, 21:35 UTC | Jul 21, 16:55 UTC | 19h 20m |
| 2026-07-20 | AFL850 | - | Jul 20, 19:20 UTC | Jul 21, 16:55 UTC | 21h 34m |
| 2026-07-20 | AFL856 | - | Jul 20, 11:55 UTC | Jul 20, 21:50 UTC | 9h 55m |
| 2026-07-20 | AFL856 | - | Jul 20, 00:05 UTC | Jul 20, 21:50 UTC | 21h 45m |
| 2026-07-19 | AFL856 | - | Jul 19, 23:45 UTC | Jul 20, 21:50 UTC | 22h 5m |
| 2026-07-19 | AFL857 | - | Jul 19, 21:30 UTC | Jul 20, 19:35 UTC | 22h 5m |
| 2026-07-19 | AFL857 | - | Jul 19, 17:05 UTC | Jul 20, 14:40 UTC | 21h 35m |
| 2026-07-19 | AFL850 | - | Jul 19, 14:35 UTC | Jul 20, 12:15 UTC | 21h 40m |
| 2026-07-19 | AFL850 | - | Jul 19, 00:05 UTC | Jul 20, 00:00 UTC | 23h 55m |
| 2026-07-18 | AFL850 | - | Jul 18, 23:50 UTC | Jul 19, 21:45 UTC | 21h 55m |
| 2026-07-18 | AFL851 | - | Jul 18, 21:35 UTC | Jul 19, 17:20 UTC | 19h 45m |
| 2026-07-18 | AFL852 | - | Jul 18, 12:40 UTC | Jul 18, 13:10 UTC | 30m |
| 2026-07-17 | AFL2177 | DLM → SVO | Jul 17, 04:35 UTC | Jul 17, 06:25 UTC | 1h 50m |
| 2026-07-17 | AFL2176 | SVO → DLM | Jul 17, 02:15 UTC | Jul 17, 02:50 UTC | 35m |
| 2026-07-16 | AFL1438 | SVO → SVO | Jul 16, 13:20 UTC | Jul 16, 13:34 UTC | 15m |
| 2026-07-16 | AFL1461 | - | Jul 16, 08:50 UTC | Jul 16, 09:10 UTC | 20m |
| 2026-07-15 | AFL856 | - | Jul 15, 13:35 UTC | Jul 16, 02:25 UTC | 12h 50m |
| 2026-07-15 | AFL856 | - | Jul 15, 02:05 UTC | Jul 16, 02:00 UTC | 23h 55m |
| 2026-07-14 | AFL856 | - | Jul 14, 23:35 UTC | Jul 15, 16:10 UTC | 16h 35m |
| 2026-07-14 | AFL857 | - | Jul 14, 17:15 UTC | Jul 15, 16:00 UTC | 22h 44m |
| 2026-07-14 | AFL850 | - | Jul 14, 14:50 UTC | Jul 15, 13:55 UTC | 23h 4m |
| 2026-07-10 | AFL856 | - | Jul 10, 13:35 UTC | Jul 11, 01:45 UTC | 12h 11m |
| 2026-07-10 | AFL856 | - | Jul 10, 00:05 UTC | Jul 10, 23:20 UTC | 23h 15m |
| 2026-07-09 | AFL856 | - | Jul 9, 23:50 UTC | Jul 10, 16:15 UTC | 16h 25m |
| 2026-07-09 | AFL857 | - | Jul 9, 21:20 UTC | Jul 10, 16:15 UTC | 18h 55m |
| 2026-07-09 | AFL857 | - | Jul 9, 12:45 UTC | Jul 10, 00:10 UTC | 11h 25m |
| 2026-07-08 | AFL2157 | - | Jul 8, 16:30 UTC | Jul 8, 18:15 UTC | 1h 45m |
| 2026-07-07 | AFL1481 | - | Jul 7, 23:50 UTC | Jul 8, 15:10 UTC | 15h 20m |
| 2026-07-07 | AFL815 | - | Jul 7, 10:05 UTC | Jul 8, 00:25 UTC | 14h 20m |
| 2026-07-06 | AFL644 | - | Jul 6, 14:05 UTC | Jul 7, 08:40 UTC | 18h 35m |
| 2026-07-06 | AFL644 | - | Jul 6, 13:45 UTC | Jul 7, 08:40 UTC | 18h 55m |
| 2026-07-05 | AFL850 | - | Jul 5, 14:50 UTC | Jul 5, 15:20 UTC | 30m |
| 2026-07-04 | AFL850 | - | Jul 4, 19:00 UTC | Jul 5, 15:20 UTC | 20h 20m |
| 2026-07-04 | AFL850 | - | Jul 4, 16:30 UTC | Jul 5, 15:20 UTC | 22h 50m |
| 2026-07-04 | AFL851 | - | Jul 4, 00:05 UTC | Jul 4, 19:15 UTC | 19h 10m |
| 2026-07-03 | AFL856 | - | Jul 3, 21:20 UTC | Jul 4, 19:15 UTC | 21h 55m |
| 2026-07-03 | AFL856 | - | Jul 3, 00:05 UTC | Jul 4, 00:00 UTC | 23h 55m |
| 2026-07-02 | AFL857 | - | Jul 2, 23:55 UTC | Jul 3, 21:35 UTC | 21h 40m |
| 2026-07-02 | AFL857 | - | Jul 2, 21:30 UTC | Jul 3, 00:10 UTC | 2h 40m |
| 2026-07-02 | AFL852 | - | Jul 2, 12:40 UTC | Jul 2, 18:10 UTC | 5h 30m |
| 2026-07-02 | AFL1460 | SVO → SVO | Jul 2, 06:25 UTC | Jul 2, 06:41 UTC | 16m |
| 2026-07-01 | AFL2157 | AYT → SVO | Jul 1, 16:30 UTC | Jul 1, 18:20 UTC | 1h 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 RA-73096 page for operator, model, and routing details .