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
- 149
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3d ago
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 | - | 25 | 2026-07-10 |
| AFL850 | - | 15 | 2026-07-05 |
| AFL857 | - | 12 | 2026-07-09 |
| AFL644 | - | 11 | 2026-07-06 |
| AFL852 | - | 10 | 2026-07-02 |
| AFL851 | - | 10 | 2026-07-04 |
| 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-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 |
| 2026-07-01 | AFL2156 | SVO → AYT | Jul 1, 00:05 UTC | Jul 1, 14:45 UTC | 14h 40m |
| 2026-06-30 | AFL815 | - | Jun 30, 09:50 UTC | Jul 1, 00:35 UTC | 14h 45m |
| 2026-06-30 | AFL644 | - | Jun 30, 03:35 UTC | Jun 30, 08:10 UTC | 4h 35m |
| 2026-06-29 | AFL644 | - | Jun 29, 12:24 UTC | Jun 30, 08:10 UTC | 19h 45m |
| 2026-06-29 | AFL644 | - | Jun 29, 10:04 UTC | Jun 30, 08:10 UTC | 22h 5m |
| 2026-06-29 | AFL644 | - | Jun 29, 08:24 UTC | Jun 30, 08:00 UTC | 23h 36m |
| 2026-06-28 | AFL814 | - | Jun 28, 10:04 UTC | Jun 29, 05:59 UTC | 19h 55m |
| 2026-06-28 | AFL814 | - | Jun 28, 09:15 UTC | Jun 29, 05:59 UTC | 20h 45m |
| 2026-06-27 | AFL644 | - | Jun 27, 12:29 UTC | Jun 28, 07:34 UTC | 19h 5m |
| 2026-06-27 | AFL644 | BKK → BKK | Jun 27, 08:14 UTC | Jun 28, 07:34 UTC | 23h 20m |
| 2026-06-27 | AFL814 | - | Jun 27, 05:10 UTC | Jun 27, 06:09 UTC | 1h 0m |
| 2026-06-26 | AFL814 | - | Jun 26, 09:14 UTC | Jun 27, 06:09 UTC | 20h 55m |
| 2026-06-26 | AFL814 | - | Jun 26, 05:30 UTC | Jun 26, 06:04 UTC | 35m |
| 2026-06-25 | AFL814 | - | Jun 25, 10:09 UTC | Jun 26, 06:04 UTC | 19h 55m |
| 2026-06-25 | AFL815 | - | Jun 25, 09:25 UTC | Jun 26, 06:04 UTC | 20h 40m |
| 2026-06-25 | AFL644 | - | Jun 25, 02:45 UTC | Jun 25, 07:09 UTC | 4h 25m |
| 2026-06-24 | AFL644 | - | Jun 24, 09:34 UTC | Jun 25, 07:09 UTC | 21h 35m |
| 2026-06-24 | AFL644 | - | Jun 24, 06:29 UTC | Jun 25, 06:00 UTC | 23h 30m |
| 2026-06-24 | AFL645 | - | Jun 24, 05:24 UTC | Jun 25, 03:10 UTC | 21h 45m |
| 2026-06-23 | AFL1480 | - | Jun 23, 16:29 UTC | Jun 24, 03:44 UTC | 11h 15m |
| 2026-06-23 | AFL1094 | SVO → CEK | Jun 23, 06:34 UTC | Jun 23, 06:59 UTC | 25m |
| 2026-06-19 | AFL2133 | - | Jun 19, 07:14 UTC | Jun 19, 07:49 UTC | 35m |
| 2026-06-17 | AFL853 | - | Jun 17, 15:25 UTC | Jun 18, 02:35 UTC | 11h 10m |
| 2026-06-17 | AFL856 | - | Jun 17, 00:35 UTC | Jun 17, 21:05 UTC | 20h 30m |
| 2026-06-16 | AFL850 | KHV → SYX | Jun 16, 20:35 UTC | Jun 17, 15:40 UTC | 19h 5m |
| 2026-06-15 | AFL850 | KHV → SYX | Jun 15, 22:54 UTC | Jun 16, 20:50 UTC | 21h 56m |
| 2026-06-15 | AFL856 | - | Jun 15, 15:35 UTC | Jun 15, 22:59 UTC | 7h 25m |
| 2026-06-14 | AFL856 | - | Jun 14, 21:30 UTC | Jun 15, 15:59 UTC | 18h 30m |
| 2026-06-14 | AFL856 | - | Jun 14, 17:45 UTC | Jun 15, 15:59 UTC | 22h 14m |
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 .