sensors Mode-S transponder
151FB8
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73656 · BOEING 737-800
- Hex
- 151FB8
- Octal
- 05217670
- Decimal
- 1,384,376
- Country
- RU
- Tail
- RA-73656
- Type
- B738
- Flights observed
- 72
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 151FB8 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 |
|---|---|---|---|
| AUL531 | - | 6 | 2026-07-05 |
| AUL507 | - | 4 | 2026-06-29 |
| AUL504 | - | 4 | 2026-07-04 |
| AUL545 | - | 3 | 2026-07-11 |
| AUL541 | - | 3 | 2026-06-13 |
| AUL532 | Aeroflot-Nord | 3 | 2026-07-10 |
| AUL251 | Aeroflot-Nord | 3 | 2026-06-15 |
| AUL596 | - | 2 | 2026-07-02 |
| AUL595 | Aeroflot-Nord | 2 | 2026-07-07 |
| AUL592 | Aeroflot-Nord | 2 | 2026-05-09 |
| AUL546 | Aeroflot-Nord | 2 | 2026-05-28 |
| AUL521 | Aeroflot-Nord | 2 | 2026-06-09 |
| AUL513 | Aeroflot-Nord | 2 | 2026-05-24 |
| AUL509 | Aeroflot-Nord | 2 | 2026-05-25 |
| AUL508 | Aeroflot-Nord | 2 | 2026-05-11 |
| AUL503 | Aeroflot-Nord | 2 | 2026-05-29 |
| AUL152 | Aeroflot-Nord | 2 | 2026-06-07 |
| AUL862 | - | 1 | 2026-07-04 |
| AUL588 | Aeroflot-Nord | 1 | 2026-05-23 |
| AUL586 | Aeroflot-Nord | 1 | 2026-05-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | AUL545 | - | Jul 11, 06:35 UTC | Jul 11, 19:00 UTC | 12h 25m |
| 2026-07-11 | AUL574 | - | Jul 11, 02:40 UTC | Jul 11, 03:55 UTC | 1h 15m |
| 2026-07-10 | AUL532 | KUF → LED | Jul 10, 12:50 UTC | Jul 10, 13:00 UTC | 10m |
| 2026-07-07 | AUL595 | LED → GDZ | Jul 7, 14:40 UTC | Jul 7, 15:25 UTC | 45m |
| 2026-07-07 | AUL595 | LED → GDZ | Jul 7, 07:25 UTC | Jul 7, 07:40 UTC | 15m |
| 2026-07-05 | AUL531 | - | Jul 5, 10:50 UTC | Jul 5, 11:10 UTC | 20m |
| 2026-07-04 | AUL504 | - | Jul 4, 23:00 UTC | Jul 5, 07:00 UTC | 8h 0m |
| 2026-07-04 | AUL862 | - | Jul 4, 08:55 UTC | Jul 4, 09:35 UTC | 40m |
| 2026-07-02 | AUL533 | LED → KGD | Jul 2, 17:45 UTC | Jul 2, 19:10 UTC | 1h 25m |
| 2026-07-02 | AUL596 | - | Jul 2, 16:20 UTC | Jul 2, 16:35 UTC | 15m |
| 2026-06-30 | AUL596 | - | Jun 30, 15:05 UTC | Jun 30, 15:15 UTC | 10m |
| 2026-06-29 | AUL507 | - | Jun 29, 07:40 UTC | Jun 29, 07:50 UTC | 10m |
| 2026-06-28 | AUL504 | - | Jun 28, 01:44 UTC | Jun 28, 06:59 UTC | 5h 15m |
| 2026-06-17 | AUL101 | - | Jun 17, 13:45 UTC | Jun 17, 14:40 UTC | 55m |
| 2026-06-15 | AUL252 | KGD → SVO | Jun 15, 18:29 UTC | Jun 15, 19:39 UTC | 1h 10m |
| 2026-06-15 | AUL251 | SVO → SVO | Jun 15, 15:50 UTC | Jun 15, 16:49 UTC | 1h 0m |
| 2026-06-15 | AUL218 | ARH → SVO | Jun 15, 11:34 UTC | Jun 15, 12:00 UTC | 25m |
| 2026-06-13 | AUL541 | - | Jun 13, 12:35 UTC | Jun 13, 14:50 UTC | 2h 15m |
| 2026-06-11 | AUL109 | - | Jun 11, 21:35 UTC | Jun 11, 21:50 UTC | 15m |
| 2026-06-11 | AUL110 | - | Jun 11, 19:55 UTC | Jun 11, 20:05 UTC | 10m |
| 2026-06-11 | AUL545 | LED → AER | Jun 11, 11:00 UTC | Jun 11, 12:00 UTC | 1h 0m |
| 2026-06-09 | AUL521 | SVO → MMK | Jun 9, 09:35 UTC | Jun 9, 10:00 UTC | 25m |
| 2026-06-08 | AUL251 | SVO → SVO | Jun 8, 15:40 UTC | Jun 8, 16:55 UTC | 1h 15m |
| 2026-06-08 | AUL217 | SVO → ARH | Jun 8, 09:15 UTC | Jun 8, 09:35 UTC | 20m |
| 2026-06-07 | AUL152 | LED → ARH | Jun 7, 11:55 UTC | Jun 7, 13:05 UTC | 1h 10m |
| 2026-06-06 | AUL251 | SVO → SVO | Jun 6, 10:09 UTC | Jun 6, 10:50 UTC | 40m |
| 2026-06-05 | AUL521 | SVO → MMK | Jun 5, 07:35 UTC | Jun 5, 08:05 UTC | 30m |
| 2026-06-04 | AUL228 | - | Jun 4, 21:15 UTC | Jun 4, 21:30 UTC | 15m |
| 2026-06-04 | AUL537 | LED → KZN | Jun 4, 16:20 UTC | Jun 4, 16:50 UTC | 30m |
| 2026-06-03 | AUL531 | LED → KUF | Jun 3, 12:15 UTC | Jun 3, 12:40 UTC | 25m |
| 2026-06-02 | AUL527 | LED → CEK | Jun 2, 23:50 UTC | Jun 3, 00:05 UTC | 15m |
| 2026-05-31 | AUL231 | SVO → SVO | May 31, 22:50 UTC | May 31, 23:15 UTC | 25m |
| 2026-05-31 | AUL227 | SVO → KZN | May 31, 17:15 UTC | May 31, 17:45 UTC | 30m |
| 2026-05-31 | AUL152 | LED → ARH | May 31, 12:40 UTC | May 31, 12:50 UTC | 10m |
| 2026-05-29 | AUL504 | - | May 29, 20:50 UTC | May 29, 21:35 UTC | 45m |
| 2026-05-29 | AUL503 | LED → SCW | May 29, 17:50 UTC | May 29, 18:10 UTC | 20m |
| 2026-05-28 | AUL546 | AER → LED | May 28, 11:35 UTC | May 28, 12:15 UTC | 40m |
| 2026-05-26 | AUL151 | ARH → LED | May 26, 16:30 UTC | May 26, 16:59 UTC | 30m |
| 2026-05-26 | AUL507 | LED → MMK | May 26, 07:15 UTC | May 26, 13:00 UTC | 5h 45m |
| 2026-05-25 | AUL509 | LED → GOJ | May 25, 07:20 UTC | May 25, 21:49 UTC | 14h 29m |
| 2026-05-25 | AUL572 | OVB → LED | May 25, 04:00 UTC | May 25, 04:15 UTC | 15m |
| 2026-05-24 | AUL513 | LED → KGD | May 24, 12:50 UTC | May 24, 14:00 UTC | 1h 10m |
| 2026-05-24 | AUL511 | LED → VOG | May 24, 06:00 UTC | May 24, 07:05 UTC | 1h 5m |
| 2026-05-23 | AUL509 | LED → GOJ | May 23, 13:20 UTC | May 23, 13:45 UTC | 25m |
| 2026-05-23 | AUL588 | REN → LED | May 23, 03:30 UTC | May 23, 09:55 UTC | 6h 25m |
| 2026-05-22 | AUL541 | LED → LED | May 22, 12:35 UTC | May 22, 13:10 UTC | 35m |
| 2026-05-22 | AUL507 | LED → MMK | May 22, 07:10 UTC | May 22, 10:35 UTC | 3h 25m |
| 2026-05-14 | AUL531 | LED → KUF | May 14, 07:55 UTC | May 14, 09:00 UTC | 1h 5m |
| 2026-05-13 | AUL531 | LED → KUF | May 13, 13:10 UTC | May 14, 09:00 UTC | 19h 50m |
| 2026-05-11 | AUL508 | MMK → LED | May 11, 17:30 UTC | May 12, 11:10 UTC | 17h 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-73656 page for operator, model, and routing details .