sensors Mode-S transponder
151E00
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73216 · AIRBUS A-319
- Hex
- 151E00
- Octal
- 05217000
- Decimal
- 1,383,936
- Country
- RU
- Tail
- RA-73216
- Type
- A319
- Flights observed
- 80
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 151E00 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 |
|---|---|---|---|
| SDM6134 | Rossiya - Russian Airlines | 7 | 2026-07-16 |
| SDM6450 | - | 5 | 2026-07-06 |
| SDM6111 | Rossiya - Russian Airlines | 4 | 2026-06-14 |
| SDM6044 | Rossiya - Russian Airlines | 4 | 2026-07-23 |
| SDM6875 | - | 3 | 2026-06-18 |
| SDM6403 | - | 3 | 2026-07-17 |
| SDM6238 | Rossiya - Russian Airlines | 3 | 2026-07-09 |
| SDM6986 | Rossiya - Russian Airlines | 2 | 2026-06-21 |
| SDM6925 | - | 2 | 2026-07-01 |
| SDM6924 | - | 2 | 2026-07-03 |
| SDM6859 | Rossiya - Russian Airlines | 2 | 2026-06-10 |
| SDM6721 | - | 2 | 2026-06-25 |
| SDM6572 | - | 2 | 2026-06-28 |
| SDM6569 | Rossiya - Russian Airlines | 2 | 2026-06-11 |
| SDM6561 | - | 2 | 2026-07-14 |
| SDM6467 | - | 2 | 2026-07-14 |
| SDM6442 | - | 2 | 2026-07-02 |
| SDM6418 | - | 2 | 2026-07-10 |
| SDM6323 | - | 2 | 2026-06-30 |
| SDM6988 | - | 1 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | SDM5991 | - | Jul 25, 13:35 UTC | Jul 25, 13:50 UTC | 15m |
| 2026-07-25 | SDM6524 | NQZ → LED | Jul 25, 10:10 UTC | Jul 25, 10:25 UTC | 15m |
| 2026-07-24 | SDM6433 | SVO → ASF | Jul 24, 08:10 UTC | Jul 24, 08:20 UTC | 10m |
| 2026-07-23 | SDM6044 | LED → SVO | Jul 23, 16:00 UTC | Jul 23, 16:30 UTC | 30m |
| 2026-07-23 | SDM6434 | ASF → SVO | Jul 23, 08:55 UTC | Jul 23, 09:20 UTC | 25m |
| 2026-07-23 | SDM6500 | AER → SVO | Jul 23, 01:30 UTC | Jul 23, 02:05 UTC | 35m |
| 2026-07-22 | SDM6044 | LED → SVO | Jul 22, 16:10 UTC | Jul 22, 16:25 UTC | 15m |
| 2026-07-22 | SDM6044 | LED → SVO | Jul 22, 14:50 UTC | Jul 22, 15:30 UTC | 40m |
| 2026-07-20 | SDM6499 | SVO → AER | Jul 20, 20:45 UTC | Jul 20, 21:10 UTC | 25m |
| 2026-07-20 | SDM6044 | LED → SVO | Jul 20, 14:55 UTC | Jul 20, 16:10 UTC | 1h 15m |
| 2026-07-18 | SDM6474 | OMS → LED | Jul 18, 06:00 UTC | Jul 18, 16:00 UTC | 10h 0m |
| 2026-07-17 | SDM6403 | - | Jul 17, 15:15 UTC | Jul 18, 06:15 UTC | 15h 1m |
| 2026-07-16 | SDM6894 | - | Jul 16, 18:25 UTC | Jul 17, 11:00 UTC | 16h 35m |
| 2026-07-16 | SDM6134 | GRV → LED | Jul 16, 12:25 UTC | Jul 16, 13:25 UTC | 1h 0m |
| 2026-07-15 | SDM6134 | GRV → LED | Jul 15, 16:10 UTC | Jul 16, 13:25 UTC | 21h 15m |
| 2026-07-14 | SDM6561 | - | Jul 14, 17:30 UTC | Jul 15, 11:20 UTC | 17h 49m |
| 2026-07-14 | SDM6467 | - | Jul 14, 13:35 UTC | Jul 15, 11:20 UTC | 21h 44m |
| 2026-07-14 | SDM6467 | - | Jul 14, 10:10 UTC | Jul 14, 17:30 UTC | 7h 20m |
| 2026-07-12 | SDM6561 | - | Jul 12, 18:35 UTC | Jul 13, 11:40 UTC | 17h 5m |
| 2026-07-12 | SDM6931 | - | Jul 12, 09:55 UTC | Jul 12, 10:10 UTC | 15m |
| 2026-07-10 | SDM6418 | - | Jul 10, 16:15 UTC | Jul 10, 16:35 UTC | 20m |
| 2026-07-10 | SDM6417 | - | Jul 10, 10:50 UTC | Jul 10, 11:00 UTC | 10m |
| 2026-07-09 | SDM6238 | KUF → LED | Jul 9, 11:45 UTC | Jul 9, 16:30 UTC | 4h 45m |
| 2026-07-08 | SDM6988 | - | Jul 8, 19:25 UTC | Jul 9, 08:10 UTC | 12h 45m |
| 2026-07-08 | SDM6987 | - | Jul 8, 02:20 UTC | Jul 8, 18:05 UTC | 15h 45m |
| 2026-07-07 | SDM6594 | KZN → LED | Jul 7, 11:40 UTC | Jul 7, 11:55 UTC | 15m |
| 2026-07-07 | SDM6593 | - | Jul 7, 07:10 UTC | Jul 7, 07:25 UTC | 15m |
| 2026-07-07 | SDM6470 | - | Jul 7, 04:50 UTC | Jul 7, 05:15 UTC | 25m |
| 2026-07-06 | SDM6450 | - | Jul 6, 20:20 UTC | Jul 6, 20:35 UTC | 15m |
| 2026-07-05 | SDM6403 | - | Jul 5, 15:55 UTC | Jul 5, 16:20 UTC | 25m |
| 2026-07-05 | SDM6450 | - | Jul 5, 11:00 UTC | Jul 5, 11:20 UTC | 20m |
| 2026-07-04 | SDM6559 | - | Jul 4, 10:50 UTC | Jul 5, 05:30 UTC | 18h 40m |
| 2026-07-04 | SDM6190 | - | Jul 4, 08:45 UTC | Jul 4, 09:10 UTC | 25m |
| 2026-07-03 | SDM6924 | - | Jul 3, 16:15 UTC | Jul 3, 16:35 UTC | 20m |
| 2026-07-03 | SDM6924 | - | Jul 3, 12:30 UTC | Jul 3, 13:00 UTC | 30m |
| 2026-07-03 | SDM6923 | - | Jul 3, 07:30 UTC | Jul 3, 10:45 UTC | 3h 15m |
| 2026-07-02 | SDM6442 | - | Jul 2, 20:00 UTC | Jul 3, 03:15 UTC | 7h 15m |
| 2026-07-02 | SDM6238 | KUF → LED | Jul 2, 16:35 UTC | Jul 2, 16:45 UTC | 10m |
| 2026-07-02 | SDM6238 | KUF → LED | Jul 2, 15:40 UTC | Jul 2, 16:00 UTC | 20m |
| 2026-07-02 | SDM6237 | LED → KUF | Jul 2, 11:25 UTC | Jul 2, 12:50 UTC | 1h 25m |
| 2026-07-02 | SDM6341 | - | Jul 2, 03:55 UTC | Jul 2, 04:40 UTC | 45m |
| 2026-07-01 | SDM6926 | - | Jul 1, 18:00 UTC | Jul 1, 18:35 UTC | 35m |
| 2026-07-01 | SDM6925 | - | Jul 1, 15:55 UTC | Jul 1, 16:10 UTC | 15m |
| 2026-06-30 | SDM6925 | - | Jun 30, 20:05 UTC | Jul 1, 16:10 UTC | 20h 5m |
| 2026-06-30 | SDM6418 | SVX → LED | Jun 30, 17:05 UTC | Jun 30, 17:35 UTC | 30m |
| 2026-06-30 | SDM6323 | - | Jun 30, 06:30 UTC | Jun 30, 07:20 UTC | 50m |
| 2026-06-28 | SDM6572 | - | Jun 28, 18:25 UTC | Jun 28, 18:34 UTC | 10m |
| 2026-06-28 | SDM6572 | - | Jun 28, 14:09 UTC | Jun 28, 17:50 UTC | 3h 40m |
| 2026-06-25 | SDM6721 | - | Jun 25, 15:04 UTC | Jun 25, 20:39 UTC | 5h 35m |
| 2026-06-22 | SDM6721 | - | Jun 22, 14:59 UTC | Jun 22, 20:44 UTC | 5h 45m |
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-73216 page for operator, model, and routing details .