sensors Mode-S transponder
151FB4
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73652 · BOEING 737-700
- Hex
- 151FB4
- Octal
- 05217664
- Decimal
- 1,384,372
- Country
- RU
- Tail
- RA-73652
- Type
- B737
- Flights observed
- 60
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 11h ago
Last known position
Country allocation
The ICAO 24-bit address 151FB4 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 |
|---|---|---|---|
| AUL504 | - | 10 | 2026-05-24 |
| AUL146 | Aeroflot-Nord | 8 | 2026-05-28 |
| AUL514 | Aeroflot-Nord | 4 | 2026-05-28 |
| AUL513 | Aeroflot-Nord | 4 | 2026-05-28 |
| AUL3308 | Aeroflot-Nord | 4 | 2026-05-26 |
| AUL507 | Aeroflot-Nord | 3 | 2026-05-18 |
| AUL503 | Aeroflot-Nord | 3 | 2026-05-24 |
| AUL217 | Aeroflot-Nord | 3 | 2026-05-26 |
| AUL509 | Aeroflot-Nord | 2 | 2026-05-24 |
| AUL505 | Aeroflot-Nord | 2 | 2026-05-27 |
| AUL3307 | Aeroflot-Nord | 2 | 2026-04-30 |
| AUL218 | - | 2 | 2026-04-16 |
| AUL148 | Aeroflot-Nord | 2 | 2026-04-17 |
| AUL588 | Aeroflot-Nord | 1 | 2026-05-21 |
| AUL587 | - | 1 | 2026-04-13 |
| AUL537 | Aeroflot-Nord | 1 | 2026-05-23 |
| AUL518 | Aeroflot-Nord | 1 | 2026-05-29 |
| AUL517 | Aeroflot-Nord | 1 | 2026-05-24 |
| AUL510 | Aeroflot-Nord | 1 | 2026-05-24 |
| AUL506 | Aeroflot-Nord | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AUL518 | MMK → LED | May 29, 11:20 UTC | May 29, 15:00 UTC | 3h 40m |
| 2026-05-28 | AUL146 | LED → ARH | May 28, 17:20 UTC | May 29, 07:20 UTC | 14h 0m |
| 2026-05-28 | AUL514 | VOZ → LED | May 28, 09:55 UTC | May 28, 11:00 UTC | 1h 5m |
| 2026-05-28 | AUL513 | LED → KGD | May 28, 07:10 UTC | May 28, 07:55 UTC | 45m |
| 2026-05-27 | AUL506 | KGD → LED | May 27, 09:30 UTC | May 27, 10:25 UTC | 55m |
| 2026-05-27 | AUL505 | SVO → SCW | May 27, 06:55 UTC | May 27, 07:40 UTC | 45m |
| 2026-05-26 | AUL217 | SVO → ARH | May 26, 15:29 UTC | May 26, 16:59 UTC | 1h 30m |
| 2026-05-26 | AUL3308 | NNM → ARH | May 26, 11:09 UTC | May 26, 14:14 UTC | 3h 5m |
| 2026-05-26 | AUL146 | LED → ARH | May 26, 07:15 UTC | May 26, 07:24 UTC | 10m |
| 2026-05-25 | AUL514 | VOZ → LED | May 25, 15:20 UTC | May 25, 16:30 UTC | 1h 10m |
| 2026-05-25 | AUL513 | LED → KGD | May 25, 12:45 UTC | May 25, 13:35 UTC | 50m |
| 2026-05-25 | AUL505 | SVO → SCW | May 25, 06:45 UTC | May 25, 07:20 UTC | 35m |
| 2026-05-24 | AUL504 | - | May 24, 21:30 UTC | May 24, 21:40 UTC | 10m |
| 2026-05-24 | AUL504 | - | May 24, 20:00 UTC | May 24, 20:50 UTC | 50m |
| 2026-05-24 | AUL503 | LED → SCW | May 24, 17:15 UTC | May 24, 17:25 UTC | 10m |
| 2026-05-24 | AUL517 | LED → MMK | May 24, 11:00 UTC | May 24, 13:50 UTC | 2h 50m |
| 2026-05-24 | AUL510 | GOJ → LED | May 24, 09:40 UTC | May 24, 09:55 UTC | 15m |
| 2026-05-24 | AUL509 | LED → GOJ | May 24, 06:20 UTC | May 24, 06:40 UTC | 20m |
| 2026-05-23 | AUL537 | LED → KZN | May 23, 16:10 UTC | May 23, 16:50 UTC | 40m |
| 2026-05-23 | AUL514 | VOZ → LED | May 23, 13:45 UTC | May 23, 14:45 UTC | 1h 0m |
| 2026-05-23 | AUL513 | LED → KGD | May 23, 11:40 UTC | May 23, 12:05 UTC | 25m |
| 2026-05-22 | AUL1509 | - | May 22, 16:25 UTC | May 22, 16:45 UTC | 20m |
| 2026-05-21 | AUL588 | REN → LED | May 21, 11:15 UTC | May 22, 03:55 UTC | 16h 40m |
| 2026-05-21 | AUL146 | LED → ARH | May 21, 07:00 UTC | May 21, 07:10 UTC | 10m |
| 2026-05-20 | AUL217 | SVO → ARH | May 20, 13:10 UTC | May 20, 17:15 UTC | 4h 5m |
| 2026-05-19 | AUL504 | - | May 19, 23:30 UTC | May 20, 00:20 UTC | 50m |
| 2026-05-19 | AUL3308 | NNM → ARH | May 19, 09:05 UTC | May 19, 12:05 UTC | 3h 0m |
| 2026-05-18 | AUL507 | LED → MMK | May 18, 07:30 UTC | May 18, 07:40 UTC | 10m |
| 2026-05-17 | AUL308 | NNM → ARH | May 17, 11:10 UTC | May 18, 07:40 UTC | 20h 30m |
| 2026-05-16 | AUL514 | VOZ → LED | May 16, 13:41 UTC | May 16, 14:46 UTC | 1h 5m |
| 2026-05-16 | AUL513 | LED → KGD | May 16, 10:50 UTC | May 16, 12:16 UTC | 1h 25m |
| 2026-05-15 | AUL146 | LED → ARH | May 15, 17:35 UTC | May 16, 07:20 UTC | 13h 46m |
| 2026-05-15 | AUL145 | ARH → LED | May 15, 08:05 UTC | May 15, 12:15 UTC | 4h 10m |
| 2026-05-15 | AUL146 | LED → ARH | May 15, 06:30 UTC | May 15, 07:00 UTC | 30m |
| 2026-05-10 | AUL504 | - | May 10, 19:54 UTC | May 11, 03:30 UTC | 7h 35m |
| 2026-05-08 | AUL504 | - | May 8, 20:10 UTC | May 8, 21:00 UTC | 50m |
| 2026-05-08 | AUL146 | LED → ARH | May 8, 06:54 UTC | May 8, 07:09 UTC | 15m |
| 2026-05-07 | AUL504 | - | May 7, 20:00 UTC | May 7, 20:50 UTC | 50m |
| 2026-05-05 | AUL504 | - | May 5, 20:05 UTC | May 6, 07:55 UTC | 11h 50m |
| 2026-05-02 | AUL504 | - | May 2, 19:55 UTC | May 2, 20:50 UTC | 55m |
| 2026-05-01 | AUL504 | - | May 1, 20:20 UTC | May 2, 14:15 UTC | 17h 55m |
| 2026-05-01 | AUL503 | LED → SCW | May 1, 18:25 UTC | May 1, 18:35 UTC | 10m |
| 2026-04-30 | AUL3308 | NNM → ARH | Apr 30, 12:10 UTC | Apr 30, 14:45 UTC | 2h 35m |
| 2026-04-30 | AUL3307 | ARH → NNM | Apr 30, 09:30 UTC | Apr 30, 10:00 UTC | 30m |
| 2026-04-29 | AUL503 | LED → SCW | Apr 29, 17:15 UTC | Apr 29, 17:30 UTC | 15m |
| 2026-04-25 | AUL507 | LED → MMK | Apr 25, 20:00 UTC | Apr 26, 14:50 UTC | 18h 50m |
| 2026-04-25 | AUL507 | LED → MMK | Apr 25, 03:40 UTC | Apr 25, 20:40 UTC | 17h 0m |
| 2026-04-20 | AUL504 | - | Apr 20, 20:00 UTC | Apr 20, 20:40 UTC | 40m |
| 2026-04-18 | AUL509 | LED → LED | Apr 18, 10:45 UTC | Apr 18, 11:35 UTC | 50m |
| 2026-04-17 | AUL150 | - | Apr 17, 16:05 UTC | Apr 17, 16:45 UTC | 40m |
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-73652 page for operator, model, and routing details .