sensors Mode-S transponder
151DB2
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73138 · BOEING 777-300ER
- Hex
- 151DB2
- Octal
- 05216662
- Decimal
- 1,383,858
- Country
- RU
- Tail
- RA-73138
- Type
- B77W
- Flights observed
- 185
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 26, 15:15 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DB2 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 |
|---|---|---|---|
| AFL209 | Aeroflot Russian Airlines | 23 | 2026-07-20 |
| AFL221 | Aeroflot Russian Airlines | 19 | 2026-07-24 |
| AFL220 | Aeroflot Russian Airlines | 11 | 2026-07-22 |
| AFL204 | - | 10 | 2026-07-13 |
| AFL1731 | - | 10 | 2026-06-20 |
| AFL205 | - | 9 | 2026-07-13 |
| AFL1730 | Aeroflot Russian Airlines | 9 | 2026-06-19 |
| AFL320 | - | 7 | 2026-07-16 |
| AFL1705 | - | 7 | 2026-07-09 |
| AFL321 | - | 6 | 2026-07-16 |
| AFL232 | Aeroflot Russian Airlines | 5 | 2026-07-25 |
| AFL1715 | Aeroflot Russian Airlines | 5 | 2026-07-24 |
| AFL233 | Aeroflot Russian Airlines | 4 | 2026-07-26 |
| AFL1745 | - | 4 | 2026-06-25 |
| AFL1714 | - | 4 | 2026-07-03 |
| AFL639 | Aeroflot Russian Airlines | 3 | 2026-04-24 |
| AFL275 | Aeroflot Russian Airlines | 3 | 2026-04-18 |
| AFL1727 | - | 3 | 2026-07-18 |
| AFL1722 | - | 3 | 2026-06-14 |
| AFL1718 | Aeroflot Russian Airlines | 3 | 2026-06-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL233 | DEL → SVO | Jul 26, 02:30 UTC | Jul 26, 15:15 UTC | 12h 46m |
| 2026-07-25 | AFL232 | SVO → DEL | Jul 25, 23:15 UTC | Jul 25, 23:55 UTC | 40m |
| 2026-07-25 | AFL232 | SVO → DEL | Jul 25, 18:55 UTC | Jul 25, 19:20 UTC | 25m |
| 2026-07-24 | AFL1715 | KHV → SVO | Jul 24, 20:20 UTC | Jul 25, 10:25 UTC | 14h 5m |
| 2026-07-24 | AFL1715 | KHV → SVO | Jul 24, 13:40 UTC | Jul 25, 10:25 UTC | 20h 45m |
| 2026-07-24 | AFL221 | CAN → SVO | Jul 24, 10:55 UTC | Jul 25, 10:25 UTC | 23h 30m |
| 2026-07-23 | AFL221 | CAN → SVO | Jul 23, 22:35 UTC | Jul 24, 20:45 UTC | 22h 10m |
| 2026-07-23 | AFL221 | CAN → SVO | Jul 23, 22:05 UTC | Jul 24, 20:30 UTC | 22h 25m |
| 2026-07-23 | AFL221 | CAN → SVO | Jul 23, 20:05 UTC | Jul 24, 14:05 UTC | 18h 0m |
| 2026-07-22 | AFL220 | SVO → CAN | Jul 22, 17:40 UTC | Jul 23, 11:50 UTC | 18h 10m |
| 2026-07-22 | AFL220 | SVO → CAN | Jul 22, 16:40 UTC | Jul 22, 17:00 UTC | 20m |
| 2026-07-21 | AFL220 | SVO → CAN | Jul 21, 18:00 UTC | Jul 21, 20:45 UTC | 2h 45m |
| 2026-07-21 | AFL220 | SVO → CAN | Jul 21, 16:50 UTC | Jul 21, 17:05 UTC | 15m |
| 2026-07-20 | AFL209 | PVG → SVO | Jul 20, 20:35 UTC | Jul 21, 12:15 UTC | 15h 40m |
| 2026-07-18 | AFL221 | - | Jul 18, 20:10 UTC | Jul 19, 12:35 UTC | 16h 25m |
| 2026-07-18 | AFL221 | - | Jul 18, 12:35 UTC | Jul 19, 12:30 UTC | 23h 55m |
| 2026-07-18 | AFL1727 | - | Jul 18, 12:15 UTC | Jul 19, 10:15 UTC | 22h 0m |
| 2026-07-17 | AFL1727 | - | Jul 17, 12:35 UTC | Jul 18, 12:30 UTC | 23h 56m |
| 2026-07-16 | AFL1739 | - | Jul 16, 20:45 UTC | Jul 17, 12:35 UTC | 15h 50m |
| 2026-07-16 | AFL321 | - | Jul 16, 02:35 UTC | Jul 16, 20:49 UTC | 18h 15m |
| 2026-07-16 | AFL320 | - | Jul 16, 01:20 UTC | Jul 16, 20:49 UTC | 19h 30m |
| 2026-07-15 | AFL320 | SVO → SVO | Jul 15, 20:00 UTC | Jul 15, 20:40 UTC | 40m |
| 2026-07-15 | AFL320 | - | Jul 15, 00:10 UTC | Jul 15, 13:55 UTC | 13h 45m |
| 2026-07-14 | AFL320 | - | Jul 14, 10:35 UTC | Jul 15, 09:10 UTC | 22h 34m |
| 2026-07-14 | AFL320 | - | Jul 14, 10:05 UTC | Jul 15, 08:30 UTC | 22h 24m |
| 2026-07-13 | AFL1735 | - | Jul 13, 18:35 UTC | Jul 14, 11:35 UTC | 17h 0m |
| 2026-07-13 | AFL205 | - | Jul 13, 04:05 UTC | Jul 13, 11:25 UTC | 7h 20m |
| 2026-07-13 | AFL204 | - | Jul 13, 01:01 UTC | Jul 13, 01:15 UTC | 15m |
| 2026-07-12 | AFL1757 | - | Jul 12, 06:15 UTC | Jul 12, 22:30 UTC | 16h 15m |
| 2026-07-11 | AFL233 | - | Jul 11, 02:50 UTC | Jul 11, 03:30 UTC | 40m |
| 2026-07-10 | AFL232 | - | Jul 10, 07:05 UTC | Jul 11, 00:00 UTC | 16h 55m |
| 2026-07-10 | AFL205 | - | Jul 10, 04:05 UTC | Jul 10, 04:15 UTC | 10m |
| 2026-07-10 | AFL204 | - | Jul 10, 01:05 UTC | Jul 10, 01:20 UTC | 15m |
| 2026-07-09 | AFL1705 | - | Jul 9, 08:10 UTC | Jul 9, 22:25 UTC | 14h 15m |
| 2026-07-08 | AFL205 | - | Jul 8, 04:00 UTC | Jul 8, 07:40 UTC | 3h 40m |
| 2026-07-07 | AFL273 | - | Jul 7, 06:35 UTC | Jul 8, 01:00 UTC | 18h 25m |
| 2026-07-07 | AFL272 | - | Jul 7, 00:25 UTC | Jul 7, 04:20 UTC | 3h 55m |
| 2026-07-06 | AFL272 | - | Jul 6, 19:50 UTC | Jul 6, 20:20 UTC | 30m |
| 2026-07-06 | AFL1017 | - | Jul 6, 13:10 UTC | Jul 6, 14:10 UTC | 1h 0m |
| 2026-07-06 | AFL1016 | - | Jul 6, 09:40 UTC | Jul 6, 10:05 UTC | 25m |
| 2026-07-05 | AFL1010 | - | Jul 5, 16:25 UTC | Jul 5, 16:55 UTC | 30m |
| 2026-07-03 | AFL1714 | - | Jul 3, 20:45 UTC | Jul 4, 11:30 UTC | 14h 45m |
| 2026-07-03 | AFL1714 | - | Jul 3, 05:05 UTC | Jul 3, 21:45 UTC | 16h 40m |
| 2026-07-02 | AFL1723 | - | Jul 2, 15:00 UTC | Jul 3, 05:30 UTC | 14h 30m |
| 2026-07-02 | AFL1705 | - | Jul 2, 08:35 UTC | Jul 3, 05:30 UTC | 20h 55m |
| 2026-07-02 | AFL1705 | - | Jul 2, 08:20 UTC | Jul 3, 05:30 UTC | 21h 10m |
| 2026-07-01 | AFL1017 | - | Jul 1, 10:35 UTC | Jul 2, 09:35 UTC | 23h 0m |
| 2026-07-01 | AFL1016 | - | Jul 1, 07:45 UTC | Jul 1, 08:25 UTC | 40m |
| 2026-06-30 | AFL1713 | - | Jun 30, 13:10 UTC | Jun 30, 14:20 UTC | 1h 10m |
| 2026-06-29 | AFL1713 | - | Jun 29, 15:39 UTC | Jun 30, 14:20 UTC | 22h 41m |
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-73138 page for operator, model, and routing details .