sensors Mode-S transponder
151DB7
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73143 · BOEING 777-300ER
- Hex
- 151DB7
- Octal
- 05216667
- Decimal
- 1,383,863
- Country
- RU
- Tail
- RA-73143
- Type
- B77W
- Flights observed
- 145
- Distinct callsigns
- 16
- Country
- RU
- Last broadcast
- Jul 26, 19:05 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DB7 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 16 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFL1735 | Aeroflot Russian Airlines | 46 | 2026-07-25 |
| AFL1734 | Aeroflot Russian Airlines | 30 | 2026-07-26 |
| AFL1701 | Aeroflot Russian Airlines | 18 | 2026-05-28 |
| AFL1745 | Aeroflot Russian Airlines | 8 | 2026-05-25 |
| AFL1731 | Aeroflot Russian Airlines | 8 | 2026-05-30 |
| AFL1705 | - | 8 | 2026-06-30 |
| AFL1715 | - | 7 | 2026-07-13 |
| AFL1744 | Aeroflot Russian Airlines | 4 | 2026-05-25 |
| AFL1700 | Aeroflot Russian Airlines | 4 | 2026-05-24 |
| AFL1730 | Aeroflot Russian Airlines | 3 | 2026-05-29 |
| AFL1714 | Aeroflot Russian Airlines | 3 | 2026-07-20 |
| AFL1018 | - | 2 | 2026-07-17 |
| AFL1726 | - | 1 | 2026-07-15 |
| AFL1711 | Aeroflot Russian Airlines | 1 | 2026-04-19 |
| AFL1003 | - | 1 | 2026-07-07 |
| AFL1002 | - | 1 | 2026-07-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL1734 | SVO → PKC | Jul 26, 09:55 UTC | Jul 26, 19:05 UTC | 9h 10m |
| 2026-07-25 | AFL1735 | PKC → SVO | Jul 25, 18:40 UTC | Jul 26, 11:30 UTC | 16h 51m |
| 2026-07-25 | AFL1734 | SVO → PKC | Jul 25, 17:10 UTC | Jul 25, 17:25 UTC | 15m |
| 2026-07-24 | AFL1735 | PKC → SVO | Jul 24, 18:20 UTC | Jul 25, 12:30 UTC | 18h 10m |
| 2026-07-24 | AFL1735 | PKC → SVO | Jul 24, 11:50 UTC | Jul 25, 10:45 UTC | 22h 55m |
| 2026-07-24 | AFL1735 | PKC → SVO | Jul 24, 10:55 UTC | Jul 24, 19:10 UTC | 8h 15m |
| 2026-07-22 | AFL1735 | PKC → SVO | Jul 22, 18:20 UTC | Jul 23, 10:35 UTC | 16h 15m |
| 2026-07-22 | AFL1735 | PKC → SVO | Jul 22, 11:10 UTC | Jul 22, 18:25 UTC | 7h 15m |
| 2026-07-21 | AFL1734 | SVO → PKC | Jul 21, 19:05 UTC | Jul 22, 11:30 UTC | 16h 25m |
| 2026-07-21 | AFL1734 | SVO → PKC | Jul 21, 17:35 UTC | Jul 21, 17:50 UTC | 15m |
| 2026-07-20 | AFL1714 | SVO → KHV | Jul 20, 19:55 UTC | Jul 21, 10:35 UTC | 14h 40m |
| 2026-07-20 | AFL1714 | SVO → KHV | Jul 20, 11:10 UTC | Jul 20, 20:45 UTC | 9h 35m |
| 2026-07-19 | AFL1735 | - | Jul 19, 18:20 UTC | Jul 20, 11:35 UTC | 17h 15m |
| 2026-07-19 | AFL1735 | - | Jul 19, 11:05 UTC | Jul 19, 18:25 UTC | 7h 20m |
| 2026-07-18 | AFL1734 | SVO → PKC | Jul 18, 18:15 UTC | Jul 19, 11:30 UTC | 17h 15m |
| 2026-07-18 | AFL1734 | SVO → PKC | Jul 18, 17:10 UTC | Jul 18, 17:25 UTC | 15m |
| 2026-07-17 | AFL1735 | - | Jul 17, 20:25 UTC | Jul 18, 12:40 UTC | 16h 16m |
| 2026-07-17 | AFL1735 | - | Jul 17, 14:39 UTC | Jul 18, 12:40 UTC | 22h 1m |
| 2026-07-17 | AFL1018 | - | Jul 17, 11:15 UTC | Jul 17, 11:55 UTC | 40m |
| 2026-07-16 | AFL1018 | - | Jul 16, 11:54 UTC | Jul 17, 11:45 UTC | 23h 50m |
| 2026-07-15 | AFL1726 | SVO → SVO | Jul 15, 20:05 UTC | Jul 15, 20:20 UTC | 15m |
| 2026-07-15 | AFL1735 | - | Jul 15, 09:55 UTC | Jul 15, 12:35 UTC | 2h 40m |
| 2026-07-13 | AFL1715 | - | Jul 13, 19:25 UTC | Jul 14, 10:30 UTC | 15h 5m |
| 2026-07-13 | AFL1735 | - | Jul 13, 09:55 UTC | Jul 14, 09:45 UTC | 23h 50m |
| 2026-07-12 | AFL1735 | - | Jul 12, 18:20 UTC | Jul 13, 11:20 UTC | 17h 0m |
| 2026-07-12 | AFL1735 | - | Jul 12, 10:10 UTC | Jul 12, 18:35 UTC | 8h 25m |
| 2026-07-11 | AFL1735 | - | Jul 11, 18:30 UTC | Jul 12, 11:35 UTC | 17h 5m |
| 2026-07-11 | AFL1734 | SVO → SVO | Jul 11, 17:30 UTC | Jul 11, 17:50 UTC | 20m |
| 2026-07-11 | AFL1735 | - | Jul 11, 10:10 UTC | Jul 11, 11:35 UTC | 1h 25m |
| 2026-07-09 | AFL1735 | - | Jul 9, 18:30 UTC | Jul 10, 11:30 UTC | 17h 0m |
| 2026-07-09 | AFL1715 | - | Jul 9, 09:35 UTC | Jul 9, 18:30 UTC | 8h 55m |
| 2026-07-08 | AFL1715 | - | Jul 8, 20:10 UTC | Jul 9, 18:30 UTC | 22h 20m |
| 2026-07-08 | AFL1735 | - | Jul 8, 10:25 UTC | Jul 9, 09:45 UTC | 23h 20m |
| 2026-07-07 | AFL1735 | - | Jul 7, 18:30 UTC | Jul 8, 11:45 UTC | 17h 15m |
| 2026-07-07 | AFL1734 | - | Jul 7, 17:20 UTC | Jul 7, 17:30 UTC | 10m |
| 2026-07-07 | AFL1003 | - | Jul 7, 11:50 UTC | Jul 7, 13:00 UTC | 1h 10m |
| 2026-07-07 | AFL1002 | - | Jul 7, 09:00 UTC | Jul 7, 09:40 UTC | 40m |
| 2026-07-06 | AFL1735 | - | Jul 6, 10:00 UTC | Jul 6, 17:45 UTC | 7h 45m |
| 2026-07-05 | AFL1735 | - | Jul 5, 19:05 UTC | Jul 6, 17:45 UTC | 22h 40m |
| 2026-07-05 | AFL1734 | SVO → SVO | Jul 5, 17:15 UTC | Jul 5, 17:30 UTC | 15m |
| 2026-07-04 | AFL1735 | - | Jul 4, 18:45 UTC | Jul 5, 11:50 UTC | 17h 5m |
| 2026-07-04 | AFL1734 | - | Jul 4, 17:55 UTC | Jul 4, 18:10 UTC | 15m |
| 2026-07-03 | AFL1735 | - | Jul 3, 18:20 UTC | Jul 4, 11:40 UTC | 17h 20m |
| 2026-07-03 | AFL1735 | - | Jul 3, 10:40 UTC | Jul 3, 19:10 UTC | 8h 30m |
| 2026-07-02 | AFL1735 | - | Jul 2, 18:40 UTC | Jul 3, 11:45 UTC | 17h 5m |
| 2026-07-02 | AFL1735 | - | Jul 2, 10:35 UTC | Jul 2, 19:45 UTC | 9h 10m |
| 2026-07-01 | AFL1734 | - | Jul 1, 19:50 UTC | Jul 2, 19:45 UTC | 23h 55m |
| 2026-07-01 | AFL1735 | - | Jul 1, 19:25 UTC | Jul 2, 11:35 UTC | 16h 10m |
| 2026-06-30 | AFL1705 | - | Jun 30, 16:50 UTC | Jul 1, 09:30 UTC | 16h 40m |
| 2026-06-29 | AFL1735 | - | Jun 29, 18:10 UTC | Jun 30, 10:30 UTC | 16h 21m |
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-73143 page for operator, model, and routing details .