sensors Mode-S transponder
151DBC
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73148 · AIRBUS A-320
- Hex
- 151DBC
- Octal
- 05216674
- Decimal
- 1,383,868
- Country
- RU
- Tail
- RA-73148
- Type
- A320
- Flights observed
- 140
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 151DBC 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 | - | 14 | 2026-07-03 |
| AFL1731 | - | 14 | 2026-06-19 |
| AFL321 | - | 13 | 2026-06-28 |
| AFL1739 | - | 8 | 2026-07-13 |
| AFL1715 | - | 8 | 2026-06-30 |
| AFL1714 | Aeroflot Russian Airlines | 7 | 2026-05-29 |
| AFL324 | - | 6 | 2026-06-12 |
| AFL1747 | - | 6 | 2026-07-14 |
| AFL639 | - | 5 | 2026-06-23 |
| AFL272 | Aeroflot Russian Airlines | 4 | 2026-05-24 |
| AFL1755 | Aeroflot Russian Airlines | 4 | 2026-06-03 |
| AFL1745 | - | 4 | 2026-06-20 |
| AFL1730 | Aeroflot Russian Airlines | 4 | 2026-06-17 |
| AFL1719 | - | 4 | 2026-07-08 |
| AFL638 | - | 3 | 2026-06-23 |
| AFL273 | Aeroflot Russian Airlines | 3 | 2026-05-25 |
| AFL1701 | - | 3 | 2026-06-21 |
| AFL1024 | Aeroflot Russian Airlines | 3 | 2026-07-01 |
| AFL585 | Aeroflot Russian Airlines | 2 | 2026-04-17 |
| AFL584 | Aeroflot Russian Airlines | 2 | 2026-04-17 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | AFL1747 | - | Jul 14, 10:55 UTC | Jul 14, 12:05 UTC | 1h 10m |
| 2026-07-13 | AFL1747 | - | Jul 13, 13:05 UTC | Jul 14, 12:05 UTC | 23h 0m |
| 2026-07-13 | AFL1739 | - | Jul 13, 12:15 UTC | Jul 14, 11:00 UTC | 22h 45m |
| 2026-07-12 | AFL1739 | - | Jul 12, 13:05 UTC | Jul 13, 12:55 UTC | 23h 50m |
| 2026-07-11 | AFL1739 | - | Jul 11, 20:45 UTC | Jul 12, 13:40 UTC | 16h 55m |
| 2026-07-11 | AFL1739 | - | Jul 11, 13:05 UTC | Jul 12, 12:55 UTC | 23h 50m |
| 2026-07-11 | AFL1739 | - | Jul 11, 12:45 UTC | Jul 11, 20:50 UTC | 8h 5m |
| 2026-07-10 | AFL1739 | - | Jul 10, 21:05 UTC | Jul 11, 20:50 UTC | 23h 45m |
| 2026-07-10 | AFL1738 | - | Jul 10, 20:10 UTC | Jul 11, 13:40 UTC | 17h 30m |
| 2026-07-10 | AFL1747 | - | Jul 10, 10:55 UTC | Jul 10, 21:20 UTC | 10h 26m |
| 2026-07-09 | AFL1747 | - | Jul 9, 13:05 UTC | Jul 10, 12:10 UTC | 23h 5m |
| 2026-07-09 | AFL1739 | - | Jul 9, 12:40 UTC | Jul 10, 11:00 UTC | 22h 20m |
| 2026-07-08 | AFL1739 | - | Jul 8, 20:50 UTC | Jul 9, 14:05 UTC | 17h 15m |
| 2026-07-08 | AFL1738 | SVO → SVO | Jul 8, 19:20 UTC | Jul 8, 19:35 UTC | 15m |
| 2026-07-08 | AFL1719 | - | Jul 8, 06:40 UTC | Jul 8, 07:55 UTC | 1h 15m |
| 2026-07-07 | AFL1719 | - | Jul 7, 09:50 UTC | Jul 8, 07:55 UTC | 22h 5m |
| 2026-07-06 | AFL1703 | - | Jul 6, 18:35 UTC | Jul 7, 10:10 UTC | 15h 35m |
| 2026-07-05 | AFL1718 | SVO → KHV | Jul 5, 16:50 UTC | Jul 5, 17:30 UTC | 40m |
| 2026-07-03 | AFL320 | - | Jul 3, 13:05 UTC | Jul 4, 08:55 UTC | 19h 50m |
| 2026-07-03 | AFL320 | - | Jul 3, 12:50 UTC | Jul 4, 08:55 UTC | 20h 5m |
| 2026-07-02 | AFL1727 | - | Jul 2, 21:05 UTC | Jul 3, 13:20 UTC | 16h 15m |
| 2026-07-02 | AFL1709 | VVO → SVO | Jul 2, 15:45 UTC | Jul 3, 13:20 UTC | 21h 35m |
| 2026-07-01 | AFL1025 | KGD → SVO | Jul 1, 15:50 UTC | Jul 1, 16:40 UTC | 50m |
| 2026-07-01 | AFL1024 | SVO → KGD | Jul 1, 07:25 UTC | Jul 1, 13:45 UTC | 6h 20m |
| 2026-06-30 | AFL1024 | SVO → KGD | Jun 30, 17:05 UTC | Jul 1, 13:45 UTC | 20h 40m |
| 2026-06-30 | AFL1024 | SVO → KGD | Jun 30, 16:35 UTC | Jul 1, 13:45 UTC | 21h 10m |
| 2026-06-30 | AFL1715 | - | Jun 30, 09:15 UTC | Jul 1, 07:50 UTC | 22h 35m |
| 2026-06-29 | AFL1715 | - | Jun 29, 20:35 UTC | Jun 30, 17:00 UTC | 20h 25m |
| 2026-06-29 | AFL1715 | - | Jun 29, 11:14 UTC | Jun 30, 10:30 UTC | 23h 16m |
| 2026-06-28 | AFL1747 | UUS → SVO | Jun 28, 20:14 UTC | Jun 29, 12:24 UTC | 16h 10m |
| 2026-06-28 | AFL1747 | UUS → SVO | Jun 28, 13:59 UTC | Jun 29, 12:24 UTC | 22h 25m |
| 2026-06-28 | AFL321 | - | Jun 28, 02:29 UTC | Jun 28, 20:14 UTC | 17h 45m |
| 2026-06-28 | AFL321 | - | Jun 28, 00:35 UTC | Jun 28, 20:14 UTC | 19h 40m |
| 2026-06-27 | AFL321 | - | Jun 27, 13:24 UTC | Jun 28, 09:30 UTC | 20h 5m |
| 2026-06-27 | AFL321 | - | Jun 27, 09:04 UTC | Jun 28, 08:55 UTC | 23h 50m |
| 2026-06-27 | AFL321 | - | Jun 27, 07:24 UTC | Jun 28, 04:05 UTC | 20h 40m |
| 2026-06-27 | AFL321 | - | Jun 27, 06:44 UTC | Jun 28, 04:05 UTC | 21h 20m |
| 2026-06-27 | AFL321 | - | Jun 27, 03:04 UTC | Jun 28, 02:29 UTC | 23h 25m |
| 2026-06-27 | AFL321 | - | Jun 27, 01:19 UTC | Jun 28, 00:35 UTC | 23h 15m |
| 2026-06-27 | AFL321 | - | Jun 27, 00:20 UTC | Jun 27, 13:49 UTC | 13h 30m |
| 2026-06-25 | AFL321 | - | Jun 25, 01:04 UTC | Jun 25, 10:55 UTC | 9h 50m |
| 2026-06-23 | AFL639 | - | Jun 23, 10:10 UTC | Jun 24, 02:45 UTC | 16h 35m |
| 2026-06-23 | AFL638 | - | Jun 23, 02:20 UTC | Jun 23, 14:44 UTC | 12h 25m |
| 2026-06-21 | AFL1701 | - | Jun 21, 04:54 UTC | Jun 21, 06:04 UTC | 1h 10m |
| 2026-06-20 | AFL1701 | - | Jun 20, 07:04 UTC | Jun 21, 06:04 UTC | 23h 0m |
| 2026-06-20 | AFL1745 | - | Jun 20, 06:19 UTC | Jun 21, 05:00 UTC | 22h 40m |
| 2026-06-19 | AFL1745 | - | Jun 19, 15:19 UTC | Jun 20, 07:34 UTC | 16h 15m |
| 2026-06-19 | AFL1731 | - | Jun 19, 07:04 UTC | Jun 20, 07:00 UTC | 23h 55m |
| 2026-06-19 | AFL1731 | - | Jun 19, 06:44 UTC | Jun 19, 15:44 UTC | 9h 0m |
| 2026-06-18 | AFL1731 | - | Jun 18, 15:00 UTC | Jun 19, 08:09 UTC | 17h 9m |
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-73148 page for operator, model, and routing details .