sensors Mode-S transponder
151DB6
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73142 · BOEING 777-300ER
- Hex
- 151DB6
- Octal
- 05216666
- Decimal
- 1,383,862
- Country
- RU
- Tail
- RA-73142
- Type
- B77W
- Flights observed
- 252
- Distinct callsigns
- 17
- Country
- RU
- Last broadcast
- Jul 26, 08:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DB6 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFL285 | Aeroflot Russian Airlines | 87 | 2026-07-24 |
| AFL284 | Aeroflot Russian Airlines | 61 | 2026-07-25 |
| AFL272 | Aeroflot Russian Airlines | 50 | 2026-07-22 |
| AFL273 | - | 30 | 2026-07-15 |
| AFL585 | Aeroflot Russian Airlines | 3 | 2026-04-15 |
| AFL584 | Aeroflot Russian Airlines | 3 | 2026-04-15 |
| AFL1735 | - | 3 | 2026-07-06 |
| AFL321 | - | 2 | 2026-07-13 |
| AFL320 | - | 2 | 2026-07-12 |
| AFL1734 | Aeroflot Russian Airlines | 2 | 2026-06-22 |
| AFL1715 | Aeroflot Russian Airlines | 2 | 2026-07-22 |
| AFL1714 | Aeroflot Russian Airlines | 2 | 2026-07-22 |
| AFL1730 | Aeroflot Russian Airlines | 1 | 2026-05-30 |
| AFL1727 | Aeroflot Russian Airlines | 1 | 2026-05-31 |
| AFL1024 | Aeroflot Russian Airlines | 1 | 2026-07-04 |
| AFL1017 | - | 1 | 2026-06-27 |
| AFL1016 | - | 1 | 2026-06-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | AFL284 | FCO → SVO | Jul 25, 22:05 UTC | Jul 26, 08:45 UTC | 10h 41m |
| 2026-07-25 | AFL284 | FCO → SVO | Jul 25, 17:30 UTC | Jul 25, 18:10 UTC | 40m |
| 2026-07-24 | AFL285 | SVO → MXP | Jul 24, 22:55 UTC | Jul 25, 13:35 UTC | 14h 40m |
| 2026-07-24 | AFL285 | SVO → MXP | Jul 24, 14:20 UTC | Jul 25, 13:30 UTC | 23h 10m |
| 2026-07-24 | AFL285 | SVO → MXP | Jul 24, 09:35 UTC | Jul 25, 09:30 UTC | 23h 55m |
| 2026-07-24 | AFL285 | SVO → MXP | Jul 24, 08:15 UTC | Jul 25, 01:15 UTC | 17h 0m |
| 2026-07-24 | AFL284 | FCO → SVO | Jul 24, 01:35 UTC | Jul 25, 01:15 UTC | 23h 40m |
| 2026-07-23 | AFL284 | FCO → SVO | Jul 23, 23:35 UTC | Jul 24, 23:30 UTC | 23h 55m |
| 2026-07-23 | AFL284 | FCO → SVO | Jul 23, 19:50 UTC | Jul 24, 14:25 UTC | 18h 35m |
| 2026-07-23 | AFL284 | FCO → SVO | Jul 23, 09:35 UTC | Jul 24, 09:30 UTC | 23h 55m |
| 2026-07-23 | AFL284 | FCO → SVO | Jul 23, 09:20 UTC | Jul 24, 02:05 UTC | 16h 45m |
| 2026-07-22 | AFL1715 | KHV → SVO | Jul 22, 20:10 UTC | Jul 23, 10:50 UTC | 14h 40m |
| 2026-07-22 | AFL1714 | SVO → KHV | Jul 22, 18:35 UTC | Jul 22, 19:00 UTC | 25m |
| 2026-07-22 | AFL272 | SVO → BKK | Jul 22, 00:40 UTC | Jul 22, 04:40 UTC | 4h 0m |
| 2026-07-19 | AFL285 | SVO → MXP | Jul 19, 20:55 UTC | Jul 20, 08:15 UTC | 11h 20m |
| 2026-07-19 | AFL284 | - | Jul 19, 07:35 UTC | Jul 20, 07:30 UTC | 23h 55m |
| 2026-07-19 | AFL285 | SVO → MXP | Jul 19, 05:35 UTC | Jul 19, 23:15 UTC | 17h 40m |
| 2026-07-18 | AFL284 | - | Jul 18, 21:35 UTC | Jul 19, 21:30 UTC | 23h 55m |
| 2026-07-18 | AFL284 | - | Jul 18, 21:05 UTC | Jul 19, 07:45 UTC | 10h 40m |
| 2026-07-18 | AFL285 | SVO → MXP | Jul 18, 11:35 UTC | Jul 19, 07:45 UTC | 20h 10m |
| 2026-07-18 | AFL285 | SVO → MXP | Jul 18, 11:15 UTC | Jul 19, 07:45 UTC | 20h 30m |
| 2026-07-18 | AFL285 | SVO → MXP | Jul 18, 07:40 UTC | Jul 19, 07:30 UTC | 23h 50m |
| 2026-07-18 | AFL285 | SVO → MXP | Jul 18, 05:40 UTC | Jul 18, 23:30 UTC | 17h 50m |
| 2026-07-17 | AFL285 | SVO → MXP | Jul 17, 23:35 UTC | Jul 18, 23:30 UTC | 23h 56m |
| 2026-07-17 | AFL285 | SVO → MXP | Jul 17, 21:34 UTC | Jul 18, 21:30 UTC | 23h 56m |
| 2026-07-17 | AFL285 | SVO → MXP | Jul 17, 21:15 UTC | Jul 18, 11:50 UTC | 14h 36m |
| 2026-07-17 | AFL284 | - | Jul 17, 16:44 UTC | Jul 17, 17:05 UTC | 20m |
| 2026-07-16 | AFL284 | - | Jul 16, 21:45 UTC | Jul 17, 08:00 UTC | 10h 15m |
| 2026-07-16 | AFL285 | - | Jul 16, 06:55 UTC | Jul 17, 00:04 UTC | 17h 10m |
| 2026-07-15 | AFL284 | - | Jul 15, 23:40 UTC | Jul 16, 23:29 UTC | 23h 50m |
| 2026-07-15 | AFL285 | - | Jul 15, 22:45 UTC | Jul 16, 09:25 UTC | 10h 40m |
| 2026-07-15 | AFL284 | SVO → SVO | Jul 15, 18:15 UTC | Jul 15, 18:50 UTC | 35m |
| 2026-07-15 | AFL273 | - | Jul 15, 06:40 UTC | Jul 15, 14:20 UTC | 7h 40m |
| 2026-07-14 | AFL272 | - | Jul 14, 21:15 UTC | Jul 15, 04:35 UTC | 7h 19m |
| 2026-07-13 | AFL321 | - | Jul 13, 00:30 UTC | Jul 13, 14:20 UTC | 13h 50m |
| 2026-07-12 | AFL320 | - | Jul 12, 07:35 UTC | Jul 13, 02:25 UTC | 18h 50m |
| 2026-07-12 | AFL285 | - | Jul 12, 06:20 UTC | Jul 13, 02:25 UTC | 20h 5m |
| 2026-07-11 | AFL284 | - | Jul 11, 21:25 UTC | Jul 12, 08:30 UTC | 11h 5m |
| 2026-07-11 | AFL284 | SVO → SVO | Jul 11, 17:05 UTC | Jul 11, 17:40 UTC | 35m |
| 2026-07-10 | AFL273 | - | Jul 10, 06:40 UTC | Jul 10, 10:25 UTC | 3h 45m |
| 2026-07-09 | AFL272 | - | Jul 9, 11:25 UTC | Jul 10, 04:30 UTC | 17h 5m |
| 2026-07-09 | AFL272 | - | Jul 9, 07:35 UTC | Jul 10, 04:30 UTC | 20h 55m |
| 2026-07-09 | AFL272 | - | Jul 9, 05:50 UTC | Jul 10, 04:30 UTC | 22h 40m |
| 2026-07-08 | AFL285 | - | Jul 8, 23:35 UTC | Jul 9, 20:55 UTC | 21h 20m |
| 2026-07-08 | AFL285 | - | Jul 8, 21:35 UTC | Jul 9, 20:55 UTC | 23h 20m |
| 2026-07-08 | AFL285 | - | Jul 8, 12:20 UTC | Jul 9, 11:30 UTC | 23h 10m |
| 2026-07-08 | AFL285 | - | Jul 8, 07:35 UTC | Jul 9, 07:30 UTC | 23h 55m |
| 2026-07-08 | AFL285 | - | Jul 8, 06:05 UTC | Jul 8, 23:55 UTC | 17h 50m |
| 2026-07-07 | AFL285 | - | Jul 7, 21:35 UTC | Jul 8, 21:30 UTC | 23h 55m |
| 2026-07-07 | AFL285 | - | Jul 7, 20:55 UTC | Jul 8, 12:25 UTC | 15h 30m |
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-73142 page for operator, model, and routing details .