sensors Mode-S transponder
151DB4
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73140 · BOEING 777-300ER
- Hex
- 151DB4
- Octal
- 05216664
- Decimal
- 1,383,860
- Country
- RU
- Tail
- RA-73140
- Type
- B77W
- Flights observed
- 189
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- Jul 24, 09:30 UTC
Last known position
Country allocation
The ICAO 24-bit address 151DB4 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 | 36 | 2026-07-20 |
| AFL221 | - | 23 | 2026-07-10 |
| AFL204 | Aeroflot Russian Airlines | 20 | 2026-07-23 |
| AFL205 | Aeroflot Russian Airlines | 14 | 2026-07-23 |
| AFL220 | - | 12 | 2026-06-22 |
| AFL208 | - | 12 | 2026-07-18 |
| AFL1739 | - | 6 | 2026-07-14 |
| AFL576 | - | 4 | 2026-05-01 |
| AFL324 | - | 4 | 2026-06-18 |
| AFL233 | - | 4 | 2026-07-04 |
| AFL1731 | Aeroflot Russian Airlines | 4 | 2026-07-23 |
| AFL325 | Aeroflot Russian Airlines | 3 | 2026-05-30 |
| AFL321 | - | 3 | 2026-07-17 |
| AFL273 | - | 3 | 2026-06-17 |
| AFL272 | - | 3 | 2026-06-16 |
| AFL232 | Aeroflot Russian Airlines | 3 | 2026-05-22 |
| AFL1735 | Aeroflot Russian Airlines | 3 | 2026-05-11 |
| AFL1730 | Aeroflot Russian Airlines | 3 | 2026-06-26 |
| AFL1703 | Aeroflot Russian Airlines | 3 | 2026-07-21 |
| AFL577 | Aeroflot Russian Airlines | 2 | 2026-05-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-23 | AFL1731 | PKC → SVO | Jul 23, 17:00 UTC | Jul 24, 09:30 UTC | 16h 30m |
| 2026-07-23 | AFL205 | PKX → SVO | Jul 23, 12:20 UTC | Jul 23, 12:30 UTC | 10m |
| 2026-07-23 | AFL205 | PKX → SVO | Jul 23, 04:30 UTC | Jul 23, 11:00 UTC | 6h 30m |
| 2026-07-23 | AFL204 | SVO → PKX | Jul 23, 01:00 UTC | Jul 23, 01:10 UTC | 10m |
| 2026-07-22 | AFL204 | SVO → PKX | Jul 22, 21:50 UTC | Jul 22, 22:30 UTC | 40m |
| 2026-07-22 | AFL204 | SVO → PKX | Jul 22, 18:35 UTC | Jul 22, 18:50 UTC | 15m |
| 2026-07-21 | AFL1703 | VVO → SVO | Jul 21, 09:35 UTC | Jul 21, 17:40 UTC | 8h 5m |
| 2026-07-20 | AFL1703 | VVO → SVO | Jul 20, 18:05 UTC | Jul 21, 17:00 UTC | 22h 55m |
| 2026-07-20 | AFL1703 | VVO → SVO | Jul 20, 12:05 UTC | Jul 21, 10:35 UTC | 22h 29m |
| 2026-07-20 | AFL209 | PVG → SVO | Jul 20, 09:20 UTC | Jul 20, 18:05 UTC | 8h 45m |
| 2026-07-19 | AFL209 | PVG → SVO | Jul 19, 21:05 UTC | Jul 20, 18:05 UTC | 21h 0m |
| 2026-07-19 | AFL209 | PVG → SVO | Jul 19, 20:50 UTC | Jul 20, 18:05 UTC | 21h 15m |
| 2026-07-19 | AFL209 | PVG → SVO | Jul 19, 12:05 UTC | Jul 20, 10:05 UTC | 22h 0m |
| 2026-07-19 | AFL209 | - | Jul 19, 09:20 UTC | Jul 19, 21:30 UTC | 12h 10m |
| 2026-07-18 | AFL209 | - | Jul 18, 20:25 UTC | Jul 19, 12:25 UTC | 16h 0m |
| 2026-07-18 | AFL208 | - | Jul 18, 17:15 UTC | Jul 18, 17:25 UTC | 10m |
| 2026-07-17 | AFL209 | - | Jul 17, 20:29 UTC | Jul 18, 13:25 UTC | 16h 56m |
| 2026-07-17 | AFL209 | - | Jul 17, 13:25 UTC | Jul 18, 13:00 UTC | 23h 36m |
| 2026-07-17 | AFL321 | - | Jul 17, 03:05 UTC | Jul 17, 21:10 UTC | 18h 5m |
| 2026-07-17 | AFL321 | - | Jul 17, 01:20 UTC | Jul 17, 21:10 UTC | 19h 50m |
| 2026-07-17 | AFL321 | - | Jul 17, 00:20 UTC | Jul 17, 21:10 UTC | 20h 50m |
| 2026-07-14 | AFL1739 | - | Jul 14, 21:05 UTC | Jul 15, 13:30 UTC | 16h 24m |
| 2026-07-14 | AFL1739 | - | Jul 14, 13:05 UTC | Jul 15, 12:50 UTC | 23h 44m |
| 2026-07-14 | AFL1739 | - | Jul 14, 12:40 UTC | Jul 14, 21:05 UTC | 8h 25m |
| 2026-07-13 | AFL1739 | - | Jul 13, 20:40 UTC | Jul 14, 14:10 UTC | 17h 30m |
| 2026-07-13 | AFL209 | - | Jul 13, 09:25 UTC | Jul 13, 21:30 UTC | 12h 5m |
| 2026-07-12 | AFL209 | - | Jul 12, 21:05 UTC | Jul 13, 21:00 UTC | 23h 55m |
| 2026-07-12 | AFL208 | - | Jul 12, 20:45 UTC | Jul 13, 10:10 UTC | 13h 25m |
| 2026-07-12 | AFL1003 | - | Jul 12, 11:25 UTC | Jul 12, 12:30 UTC | 1h 5m |
| 2026-07-12 | AFL1002 | - | Jul 12, 08:35 UTC | Jul 12, 09:10 UTC | 35m |
| 2026-07-11 | AFL209 | - | Jul 11, 12:15 UTC | Jul 11, 12:45 UTC | 30m |
| 2026-07-10 | AFL209 | - | Jul 10, 20:35 UTC | Jul 11, 09:15 UTC | 12h 40m |
| 2026-07-10 | AFL208 | - | Jul 10, 09:05 UTC | Jul 11, 09:00 UTC | 23h 55m |
| 2026-07-10 | AFL221 | - | Jul 10, 08:20 UTC | Jul 10, 21:10 UTC | 12h 50m |
| 2026-07-09 | AFL221 | - | Jul 9, 20:00 UTC | Jul 10, 09:05 UTC | 13h 5m |
| 2026-07-09 | AFL1731 | - | Jul 9, 07:15 UTC | Jul 9, 20:35 UTC | 13h 20m |
| 2026-07-08 | AFL1731 | - | Jul 8, 15:45 UTC | Jul 9, 08:15 UTC | 16h 30m |
| 2026-07-08 | AFL1731 | - | Jul 8, 09:10 UTC | Jul 9, 08:15 UTC | 23h 5m |
| 2026-07-04 | AFL233 | - | Jul 4, 02:30 UTC | Jul 4, 07:10 UTC | 4h 40m |
| 2026-07-03 | AFL205 | - | Jul 3, 07:10 UTC | Jul 4, 00:05 UTC | 16h 55m |
| 2026-07-03 | AFL205 | - | Jul 3, 04:05 UTC | Jul 4, 00:05 UTC | 20h 0m |
| 2026-07-03 | AFL204 | - | Jul 3, 00:45 UTC | Jul 3, 01:00 UTC | 15m |
| 2026-07-02 | AFL1739 | - | Jul 2, 12:15 UTC | Jul 2, 22:20 UTC | 10h 5m |
| 2026-07-01 | AFL1739 | - | Jul 1, 20:30 UTC | Jul 2, 13:45 UTC | 17h 15m |
| 2026-07-01 | AFL1738 | - | Jul 1, 11:35 UTC | Jul 1, 21:25 UTC | 9h 50m |
| 2026-06-30 | AFL221 | - | Jun 30, 21:45 UTC | Jul 1, 21:00 UTC | 23h 15m |
| 2026-06-30 | AFL209 | - | Jun 30, 07:05 UTC | Jun 30, 22:20 UTC | 15h 15m |
| 2026-06-29 | AFL209 | - | Jun 29, 20:49 UTC | Jun 30, 10:35 UTC | 13h 46m |
| 2026-06-29 | AFL208 | - | Jun 29, 09:05 UTC | Jun 30, 07:10 UTC | 22h 6m |
| 2026-06-29 | AFL209 | - | Jun 29, 08:39 UTC | Jun 29, 21:30 UTC | 12h 50m |
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-73140 page for operator, model, and routing details .