sensors Mode-S transponder
151D87
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73095 · BOEING 737-800
- Hex
- 151D87
- Octal
- 05216607
- Decimal
- 1,383,815
- Country
- RU
- Tail
- RA-73095
- Type
- B738
- Flights observed
- 158
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 151D87 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 |
|---|---|---|---|
| AFL850 | - | 20 | 2026-07-07 |
| AFL856 | - | 18 | 2026-07-08 |
| AFL851 | - | 16 | 2026-07-07 |
| AFL644 | - | 13 | 2026-07-04 |
| AFL814 | - | 11 | 2026-07-06 |
| AFL853 | - | 10 | 2026-07-12 |
| AFL857 | - | 9 | 2026-07-07 |
| AFL815 | - | 5 | 2026-07-05 |
| AFL645 | - | 5 | 2026-07-06 |
| AFL852 | - | 4 | 2026-06-27 |
| AFL401 | Aeroflot Russian Airlines | 3 | 2026-05-16 |
| AFL1487 | Aeroflot Russian Airlines | 3 | 2026-06-26 |
| AFL526 | - | 2 | 2026-07-11 |
| AFL521 | Aeroflot Russian Airlines | 2 | 2026-06-09 |
| AFL2132 | Aeroflot Russian Airlines | 2 | 2026-05-17 |
| AFL2126 | Aeroflot Russian Airlines | 2 | 2026-06-05 |
| AFL2123 | Aeroflot Russian Airlines | 2 | 2026-05-18 |
| AFL1995 | Aeroflot Russian Airlines | 2 | 2026-05-16 |
| AFL1967 | Aeroflot Russian Airlines | 2 | 2026-05-03 |
| AFL1865 | Aeroflot Russian Airlines | 2 | 2026-05-22 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AFL1562 | - | Jul 14, 02:20 UTC | Jul 14, 07:35 UTC | 5h 15m |
| 2026-07-12 | AFL853 | - | Jul 12, 13:15 UTC | Jul 13, 02:45 UTC | 13h 30m |
| 2026-07-11 | AFL527 | - | Jul 11, 16:20 UTC | Jul 11, 19:45 UTC | 3h 25m |
| 2026-07-11 | AFL526 | - | Jul 11, 13:45 UTC | Jul 11, 14:15 UTC | 30m |
| 2026-07-11 | AFL526 | SVO → SVO | Jul 11, 08:15 UTC | Jul 11, 09:15 UTC | 1h 0m |
| 2026-07-10 | AFL2169 | - | Jul 10, 17:20 UTC | Jul 10, 19:10 UTC | 1h 50m |
| 2026-07-10 | AFL2168 | SVO → DLM | Jul 10, 15:30 UTC | Jul 10, 15:55 UTC | 25m |
| 2026-07-08 | AFL856 | - | Jul 8, 13:00 UTC | Jul 9, 02:55 UTC | 13h 55m |
| 2026-07-08 | AFL856 | - | Jul 8, 01:50 UTC | Jul 8, 21:15 UTC | 19h 25m |
| 2026-07-07 | AFL857 | - | Jul 7, 23:30 UTC | Jul 8, 21:15 UTC | 21h 45m |
| 2026-07-07 | AFL857 | - | Jul 7, 16:40 UTC | Jul 8, 15:35 UTC | 22h 55m |
| 2026-07-07 | AFL850 | - | Jul 7, 14:05 UTC | Jul 8, 13:15 UTC | 23h 10m |
| 2026-07-07 | AFL850 | - | Jul 7, 05:50 UTC | Jul 8, 02:05 UTC | 20h 15m |
| 2026-07-07 | AFL850 | - | Jul 7, 05:25 UTC | Jul 8, 02:05 UTC | 20h 40m |
| 2026-07-07 | AFL851 | - | Jul 7, 02:35 UTC | Jul 8, 01:45 UTC | 23h 10m |
| 2026-07-06 | AFL851 | - | Jul 6, 20:25 UTC | Jul 7, 16:55 UTC | 20h 30m |
| 2026-07-06 | AFL851 | - | Jul 6, 17:50 UTC | Jul 7, 16:55 UTC | 23h 5m |
| 2026-07-06 | AFL851 | - | Jul 6, 12:10 UTC | Jul 7, 05:50 UTC | 17h 40m |
| 2026-07-06 | AFL645 | - | Jul 6, 08:10 UTC | Jul 7, 05:50 UTC | 21h 40m |
| 2026-07-06 | AFL814 | - | Jul 6, 05:00 UTC | Jul 6, 05:50 UTC | 50m |
| 2026-07-05 | AFL814 | - | Jul 5, 10:25 UTC | Jul 6, 05:50 UTC | 19h 25m |
| 2026-07-05 | AFL815 | - | Jul 5, 09:15 UTC | Jul 6, 05:50 UTC | 20h 35m |
| 2026-07-04 | AFL644 | - | Jul 4, 12:15 UTC | Jul 5, 07:30 UTC | 19h 15m |
| 2026-07-04 | AFL644 | - | Jul 4, 09:50 UTC | Jul 5, 07:30 UTC | 21h 40m |
| 2026-07-04 | AFL644 | - | Jul 4, 08:05 UTC | Jul 5, 07:30 UTC | 23h 25m |
| 2026-07-04 | AFL814 | - | Jul 4, 04:30 UTC | Jul 4, 06:05 UTC | 1h 35m |
| 2026-07-03 | AFL814 | - | Jul 3, 10:25 UTC | Jul 4, 06:05 UTC | 19h 40m |
| 2026-07-03 | AFL814 | - | Jul 3, 09:15 UTC | Jul 4, 06:05 UTC | 20h 50m |
| 2026-07-02 | AFL814 | - | Jul 2, 09:30 UTC | Jul 3, 06:45 UTC | 21h 15m |
| 2026-07-02 | AFL644 | - | Jul 2, 05:45 UTC | Jul 2, 07:40 UTC | 1h 55m |
| 2026-07-01 | AFL644 | - | Jul 1, 09:30 UTC | Jul 2, 07:40 UTC | 22h 10m |
| 2026-07-01 | AFL645 | - | Jul 1, 06:30 UTC | Jul 2, 05:45 UTC | 23h 15m |
| 2026-07-01 | AFL645 | - | Jul 1, 05:25 UTC | Jul 1, 05:40 UTC | 15m |
| 2026-06-30 | AFL814 | - | Jun 30, 18:40 UTC | Jul 1, 03:50 UTC | 9h 10m |
| 2026-06-27 | AFL853 | - | Jun 27, 21:04 UTC | Jun 28, 03:00 UTC | 5h 55m |
| 2026-06-27 | AFL852 | - | Jun 27, 12:34 UTC | Jun 27, 17:59 UTC | 5h 25m |
| 2026-06-26 | AFL1487 | KJA → SVO | Jun 26, 13:40 UTC | Jun 26, 16:49 UTC | 3h 10m |
| 2026-06-25 | AFL1487 | KJA → SVO | Jun 25, 20:30 UTC | Jun 26, 16:49 UTC | 20h 20m |
| 2026-06-23 | AFL815 | - | Jun 23, 09:59 UTC | Jun 24, 00:25 UTC | 14h 25m |
| 2026-06-23 | AFL644 | - | Jun 23, 03:49 UTC | Jun 23, 08:35 UTC | 4h 45m |
| 2026-06-21 | AFL850 | KHV → SYX | Jun 21, 05:54 UTC | Jun 22, 00:10 UTC | 18h 15m |
| 2026-06-21 | AFL850 | KHV → SYX | Jun 21, 03:49 UTC | Jun 22, 00:10 UTC | 20h 20m |
| 2026-06-20 | AFL850 | KHV → SYX | Jun 20, 21:49 UTC | Jun 21, 21:44 UTC | 23h 55m |
| 2026-06-20 | AFL850 | KHV → SYX | Jun 20, 21:34 UTC | Jun 21, 17:35 UTC | 20h 0m |
| 2026-06-20 | AFL851 | - | Jun 20, 09:49 UTC | Jun 21, 06:10 UTC | 20h 20m |
| 2026-06-20 | AFL851 | - | Jun 20, 09:09 UTC | Jun 21, 06:10 UTC | 21h 0m |
| 2026-06-20 | AFL851 | - | Jun 20, 06:39 UTC | Jun 21, 03:49 UTC | 21h 10m |
| 2026-06-18 | AFL852 | OVB → SYX | Jun 18, 15:45 UTC | Jun 19, 03:09 UTC | 11h 24m |
| 2026-06-18 | AFL1460 | SVO → OVB | Jun 18, 10:00 UTC | Jun 18, 10:20 UTC | 20m |
| 2026-06-16 | AFL1481 | - | Jun 16, 10:04 UTC | Jun 17, 03:15 UTC | 17h 11m |
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-73095 page for operator, model, and routing details .