sensors Mode-S transponder
151DB5
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73141 · BOEING 777-300ER
- Hex
- 151DB5
- Octal
- 05216665
- Decimal
- 1,383,861
- Country
- RU
- Tail
- RA-73141
- Type
- B77W
- Flights observed
- 232
- Distinct callsigns
- 15
- Country
- RU
- Last broadcast
- Jul 26, 14:20 UTC
Current position
Country allocation
The ICAO 24-bit address 151DB5 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 15 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFL285 | Aeroflot Russian Airlines | 78 | 2026-07-23 |
| AFL284 | Aeroflot Russian Airlines | 72 | 2026-07-21 |
| AFL272 | Aeroflot Russian Airlines | 42 | 2026-07-25 |
| AFL273 | Aeroflot Russian Airlines | 25 | 2026-07-26 |
| AFL1734 | Aeroflot Russian Airlines | 3 | 2026-06-24 |
| AFL1712 | Aeroflot Russian Airlines | 2 | 2026-06-12 |
| AFL1002 | Aeroflot Russian Airlines | 2 | 2026-06-16 |
| AFL1745 | - | 1 | 2026-06-29 |
| AFL1739 | Aeroflot Russian Airlines | 1 | 2026-07-24 |
| AFL1737 | - | 1 | 2026-07-17 |
| AFL1735 | - | 1 | 2026-06-24 |
| AFL1731 | Aeroflot Russian Airlines | 1 | 2026-04-13 |
| AFL1713 | Aeroflot Russian Airlines | 1 | 2026-06-13 |
| AFL1017 | - | 1 | 2026-07-02 |
| AFL1016 | - | 1 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFL273 | BKK → SVO | Jul 26, 06:30 UTC | Jul 26, 14:20 UTC | 7h 51m |
| 2026-07-25 | AFL272 | SVO → BKK | Jul 25, 12:10 UTC | Jul 26, 04:25 UTC | 16h 15m |
| 2026-07-24 | AFL1739 | PKC → SVO | Jul 24, 20:40 UTC | Jul 25, 13:40 UTC | 17h 0m |
| 2026-07-24 | AFL273 | BKK → SVO | Jul 24, 07:40 UTC | Jul 24, 21:25 UTC | 13h 45m |
| 2026-07-23 | AFL272 | SVO → BKK | Jul 23, 11:30 UTC | Jul 24, 05:40 UTC | 18h 10m |
| 2026-07-23 | AFL272 | SVO → BKK | Jul 23, 07:20 UTC | Jul 24, 05:40 UTC | 22h 20m |
| 2026-07-23 | AFL272 | SVO → BKK | Jul 23, 05:20 UTC | Jul 24, 05:15 UTC | 23h 55m |
| 2026-07-23 | AFL285 | SVO → MXP | Jul 23, 04:50 UTC | Jul 24, 03:15 UTC | 22h 25m |
| 2026-07-22 | AFL285 | SVO → MXP | Jul 22, 21:05 UTC | Jul 23, 11:45 UTC | 14h 40m |
| 2026-07-22 | AFL285 | SVO → MXP | Jul 22, 11:50 UTC | Jul 23, 07:50 UTC | 20h 0m |
| 2026-07-21 | AFL284 | FCO → SVO | Jul 21, 23:20 UTC | Jul 22, 23:15 UTC | 23h 55m |
| 2026-07-21 | AFL284 | FCO → SVO | Jul 21, 21:20 UTC | Jul 22, 21:15 UTC | 23h 55m |
| 2026-07-21 | AFL284 | FCO → SVO | Jul 21, 21:05 UTC | Jul 22, 12:25 UTC | 15h 20m |
| 2026-07-21 | AFL284 | FCO → SVO | Jul 21, 16:40 UTC | Jul 21, 17:30 UTC | 50m |
| 2026-07-20 | AFL284 | - | Jul 20, 18:05 UTC | Jul 21, 07:55 UTC | 13h 50m |
| 2026-07-20 | AFL284 | - | Jul 20, 16:55 UTC | Jul 20, 17:10 UTC | 15m |
| 2026-07-19 | AFL273 | BKK → SVO | Jul 19, 06:45 UTC | Jul 19, 14:15 UTC | 7h 30m |
| 2026-07-18 | AFL272 | SVO → BKK | Jul 18, 14:30 UTC | Jul 19, 04:30 UTC | 14h 0m |
| 2026-07-17 | AFL1737 | - | Jul 17, 22:45 UTC | Jul 18, 15:30 UTC | 16h 46m |
| 2026-07-17 | AFL273 | - | Jul 17, 08:59 UTC | Jul 17, 23:10 UTC | 14h 10m |
| 2026-07-17 | AFL272 | SVO → BKK | Jul 17, 02:34 UTC | Jul 17, 06:45 UTC | 4h 10m |
| 2026-07-12 | AFL273 | - | Jul 12, 15:45 UTC | Jul 12, 16:15 UTC | 30m |
| 2026-07-12 | AFL273 | - | Jul 12, 06:45 UTC | Jul 12, 10:30 UTC | 3h 45m |
| 2026-07-12 | AFL272 | - | Jul 12, 00:45 UTC | Jul 12, 04:45 UTC | 4h 0m |
| 2026-07-11 | AFL272 | - | Jul 11, 07:20 UTC | Jul 12, 04:45 UTC | 21h 25m |
| 2026-07-11 | AFL272 | - | Jul 11, 05:55 UTC | Jul 12, 03:15 UTC | 21h 20m |
| 2026-07-10 | AFL284 | - | Jul 10, 21:00 UTC | Jul 11, 08:01 UTC | 11h 1m |
| 2026-07-10 | AFL284 | - | Jul 10, 07:20 UTC | Jul 11, 07:15 UTC | 23h 55m |
| 2026-07-10 | AFL284 | - | Jul 10, 05:50 UTC | Jul 10, 23:35 UTC | 17h 45m |
| 2026-07-09 | AFL284 | - | Jul 9, 23:20 UTC | Jul 10, 23:15 UTC | 23h 55m |
| 2026-07-09 | AFL284 | - | Jul 9, 21:20 UTC | Jul 10, 08:00 UTC | 10h 40m |
| 2026-07-08 | AFL273 | - | Jul 8, 08:50 UTC | Jul 8, 12:55 UTC | 4h 5m |
| 2026-07-08 | AFL272 | - | Jul 8, 02:35 UTC | Jul 8, 06:40 UTC | 4h 5m |
| 2026-07-07 | AFL272 | - | Jul 7, 07:20 UTC | Jul 8, 06:40 UTC | 23h 20m |
| 2026-07-07 | AFL272 | - | Jul 7, 05:45 UTC | Jul 8, 05:10 UTC | 23h 25m |
| 2026-07-06 | AFL284 | - | Jul 6, 17:50 UTC | Jul 7, 07:55 UTC | 14h 5m |
| 2026-07-06 | AFL285 | - | Jul 6, 11:25 UTC | Jul 7, 07:55 UTC | 20h 30m |
| 2026-07-06 | AFL285 | - | Jul 6, 07:20 UTC | Jul 7, 07:15 UTC | 23h 55m |
| 2026-07-06 | AFL285 | - | Jul 6, 05:45 UTC | Jul 6, 23:25 UTC | 17h 40m |
| 2026-07-05 | AFL284 | - | Jul 5, 23:20 UTC | Jul 6, 23:15 UTC | 23h 55m |
| 2026-07-05 | AFL284 | - | Jul 5, 21:25 UTC | Jul 6, 21:15 UTC | 23h 50m |
| 2026-07-05 | AFL284 | SVO → SVO | Jul 5, 16:45 UTC | Jul 5, 17:15 UTC | 30m |
| 2026-07-04 | AFL284 | - | Jul 4, 21:05 UTC | Jul 5, 08:30 UTC | 11h 25m |
| 2026-07-03 | AFL284 | - | Jul 3, 21:55 UTC | Jul 4, 08:30 UTC | 10h 35m |
| 2026-07-03 | AFL284 | - | Jul 3, 11:55 UTC | Jul 4, 08:30 UTC | 20h 35m |
| 2026-07-03 | AFL284 | - | Jul 3, 07:20 UTC | Jul 4, 06:40 UTC | 23h 20m |
| 2026-07-03 | AFL284 | - | Jul 3, 06:15 UTC | Jul 4, 02:00 UTC | 19h 45m |
| 2026-07-02 | AFL284 | - | Jul 2, 23:20 UTC | Jul 3, 23:00 UTC | 23h 40m |
| 2026-07-02 | AFL284 | - | Jul 2, 21:20 UTC | Jul 3, 12:15 UTC | 14h 55m |
| 2026-07-02 | AFL1017 | - | Jul 2, 12:15 UTC | Jul 2, 13:50 UTC | 1h 35m |
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-73141 page for operator, model, and routing details .