sensors Mode-S transponder
151DBE
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73150 · BOEING 777-300ER
- Hex
- 151DBE
- Octal
- 05216676
- Decimal
- 1,383,870
- Country
- RU
- Tail
- RA-73150
- Type
- B77W
- Flights observed
- 162
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 151DBE 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 |
|---|---|---|---|
| AFL320 | - | 22 | 2026-07-02 |
| AFL1727 | - | 17 | 2026-07-06 |
| AFL1745 | - | 10 | 2026-06-28 |
| AFL643 | Aeroflot Russian Airlines | 9 | 2026-04-22 |
| AFL273 | Aeroflot Russian Airlines | 9 | 2026-04-27 |
| AFL272 | Aeroflot Russian Airlines | 8 | 2026-04-27 |
| AFL1715 | - | 8 | 2026-07-07 |
| AFL639 | Aeroflot Russian Airlines | 7 | 2026-06-09 |
| AFL1731 | - | 5 | 2026-07-12 |
| AFL1722 | - | 5 | 2026-06-18 |
| AFL1714 | - | 5 | 2026-07-07 |
| AFL638 | Aeroflot Russian Airlines | 4 | 2026-06-08 |
| AFL324 | - | 4 | 2026-07-03 |
| AFL1730 | Aeroflot Russian Airlines | 4 | 2026-06-06 |
| AFL1703 | - | 4 | 2026-07-13 |
| AFL1701 | Aeroflot Russian Airlines | 4 | 2026-06-02 |
| AFL634 | Aeroflot Russian Airlines | 3 | 2026-04-20 |
| AFL585 | Aeroflot Russian Airlines | 3 | 2026-04-29 |
| AFL642 | Aeroflot Russian Airlines | 2 | 2026-04-19 |
| AFL637 | Aeroflot Russian Airlines | 2 | 2026-04-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AFL1719 | - | Jul 14, 06:40 UTC | Jul 14, 15:15 UTC | 8h 35m |
| 2026-07-13 | AFL1719 | - | Jul 13, 16:50 UTC | Jul 14, 15:15 UTC | 22h 25m |
| 2026-07-13 | AFL1703 | - | Jul 13, 11:40 UTC | Jul 13, 11:50 UTC | 10m |
| 2026-07-13 | AFL1703 | - | Jul 13, 09:50 UTC | Jul 13, 10:50 UTC | 1h 0m |
| 2026-07-12 | AFL1731 | - | Jul 12, 07:45 UTC | Jul 12, 09:10 UTC | 1h 25m |
| 2026-07-07 | AFL1715 | - | Jul 7, 20:30 UTC | Jul 8, 10:40 UTC | 14h 10m |
| 2026-07-07 | AFL1714 | - | Jul 7, 18:55 UTC | Jul 7, 19:05 UTC | 10m |
| 2026-07-07 | AFL1739 | - | Jul 7, 12:20 UTC | Jul 7, 13:50 UTC | 1h 30m |
| 2026-07-06 | AFL1739 | - | Jul 6, 13:35 UTC | Jul 7, 13:30 UTC | 23h 55m |
| 2026-07-06 | AFL1727 | - | Jul 6, 12:50 UTC | Jul 6, 14:00 UTC | 1h 10m |
| 2026-07-05 | AFL1726 | SVO → SVO | Jul 5, 20:35 UTC | Jul 5, 20:55 UTC | 20m |
| 2026-07-05 | AFL1747 | - | Jul 5, 13:05 UTC | Jul 5, 14:20 UTC | 1h 15m |
| 2026-07-04 | AFL1746 | SVO → SVO | Jul 4, 21:00 UTC | Jul 4, 21:10 UTC | 10m |
| 2026-07-03 | AFL324 | - | Jul 3, 15:55 UTC | Jul 4, 11:30 UTC | 19h 35m |
| 2026-07-02 | AFL1708 | - | Jul 2, 22:45 UTC | Jul 2, 22:55 UTC | 10m |
| 2026-07-02 | AFL320 | - | Jul 2, 01:20 UTC | Jul 2, 17:35 UTC | 16h 15m |
| 2026-07-01 | AFL320 | - | Jul 1, 13:45 UTC | Jul 2, 13:00 UTC | 23h 15m |
| 2026-07-01 | AFL320 | - | Jul 1, 10:10 UTC | Jul 2, 03:55 UTC | 17h 45m |
| 2026-07-01 | AFL320 | - | Jul 1, 08:20 UTC | Jul 2, 03:55 UTC | 19h 35m |
| 2026-07-01 | AFL320 | - | Jul 1, 06:55 UTC | Jul 2, 03:55 UTC | 21h 0m |
| 2026-07-01 | AFL320 | - | Jul 1, 03:35 UTC | Jul 2, 02:20 UTC | 22h 45m |
| 2026-07-01 | AFL320 | - | Jul 1, 01:35 UTC | Jul 2, 01:30 UTC | 23h 55m |
| 2026-07-01 | AFL320 | - | Jul 1, 00:20 UTC | Jul 1, 13:50 UTC | 13h 30m |
| 2026-06-30 | AFL320 | - | Jun 30, 13:35 UTC | Jul 1, 10:10 UTC | 20h 35m |
| 2026-06-30 | AFL320 | - | Jun 30, 10:05 UTC | Jul 1, 09:15 UTC | 23h 10m |
| 2026-06-30 | AFL320 | - | Jun 30, 08:25 UTC | Jul 1, 07:00 UTC | 22h 35m |
| 2026-06-30 | AFL320 | - | Jun 30, 03:35 UTC | Jul 1, 03:30 UTC | 23h 55m |
| 2026-06-30 | AFL320 | - | Jun 30, 01:35 UTC | Jul 1, 01:30 UTC | 23h 55m |
| 2026-06-30 | AFL320 | - | Jun 30, 01:09 UTC | Jun 30, 13:45 UTC | 12h 36m |
| 2026-06-29 | AFL320 | - | Jun 29, 19:54 UTC | Jun 29, 20:19 UTC | 25m |
| 2026-06-28 | AFL1745 | - | Jun 28, 07:20 UTC | Jun 28, 07:34 UTC | 15m |
| 2026-06-27 | AFL1715 | - | Jun 27, 10:05 UTC | Jun 28, 07:34 UTC | 21h 30m |
| 2026-06-26 | AFL1714 | - | Jun 26, 19:50 UTC | Jun 27, 10:40 UTC | 14h 50m |
| 2026-06-26 | AFL1714 | - | Jun 26, 18:39 UTC | Jun 26, 19:00 UTC | 20m |
| 2026-06-26 | AFL1727 | - | Jun 26, 12:00 UTC | Jun 26, 13:10 UTC | 1h 10m |
| 2026-06-24 | AFL1715 | - | Jun 24, 20:40 UTC | Jun 25, 11:25 UTC | 14h 45m |
| 2026-06-23 | AFL1727 | - | Jun 23, 12:20 UTC | Jun 23, 13:15 UTC | 55m |
| 2026-06-22 | AFL1703 | VVO → SVO | Jun 22, 10:00 UTC | Jun 22, 11:04 UTC | 1h 5m |
| 2026-06-21 | AFL1727 | - | Jun 21, 11:59 UTC | Jun 22, 11:04 UTC | 23h 5m |
| 2026-06-20 | AFL1727 | - | Jun 20, 13:59 UTC | Jun 21, 13:09 UTC | 23h 10m |
| 2026-06-18 | AFL1722 | - | Jun 18, 14:55 UTC | Jun 19, 05:09 UTC | 14h 14m |
| 2026-06-18 | AFL1722 | - | Jun 18, 08:35 UTC | Jun 19, 05:09 UTC | 20h 34m |
| 2026-06-18 | AFL1745 | - | Jun 18, 07:00 UTC | Jun 19, 05:09 UTC | 22h 9m |
| 2026-06-17 | AFL1745 | - | Jun 17, 07:45 UTC | Jun 18, 07:20 UTC | 23h 35m |
| 2026-06-16 | AFL1745 | - | Jun 16, 15:35 UTC | Jun 17, 08:20 UTC | 16h 46m |
| 2026-06-14 | AFL1713 | KHV → SVO | Jun 14, 21:40 UTC | Jun 15, 13:54 UTC | 16h 15m |
| 2026-06-14 | AFL1712 | SVO → KHV | Jun 14, 13:40 UTC | Jun 15, 13:30 UTC | 23h 50m |
| 2026-06-13 | AFL1727 | - | Jun 13, 21:40 UTC | Jun 14, 14:40 UTC | 17h 1m |
| 2026-06-12 | AFL1727 | VVO → SVO | Jun 12, 20:55 UTC | Jun 13, 13:10 UTC | 16h 14m |
| 2026-06-12 | AFL1727 | VVO → SVO | Jun 12, 13:35 UTC | Jun 13, 13:10 UTC | 23h 34m |
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-73150 page for operator, model, and routing details .