sensors Mode-S transponder
151E29
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73257 · BOEING 737-800
- Hex
- 151E29
- Octal
- 05217051
- Decimal
- 1,383,977
- Country
- RU
- Tail
- RA-73257
- Type
- B738
- Flights observed
- 87
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 151E29 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 |
|---|---|---|---|
| TYA104 | - | 10 | 2026-06-26 |
| TYA301 | NordStar | 8 | 2026-06-28 |
| TYA102 | NordStar | 8 | 2026-07-03 |
| TYA925 | NordStar | 7 | 2026-05-20 |
| TYA951 | NordStar | 4 | 2026-07-13 |
| TYA4313 | - | 4 | 2026-05-13 |
| TYA406 | NordStar | 4 | 2026-06-06 |
| TYA103 | - | 4 | 2026-06-22 |
| TYA405 | - | 3 | 2026-04-17 |
| TYA401 | NordStar | 3 | 2026-06-19 |
| TYA108 | NordStar | 3 | 2026-05-24 |
| TYA4312 | - | 2 | 2026-05-14 |
| TYA409 | NordStar | 2 | 2026-06-01 |
| TYA322 | - | 2 | 2026-07-12 |
| TYA321 | - | 2 | 2026-07-11 |
| TYA302 | - | 2 | 2026-06-28 |
| TYA208 | - | 2 | 2026-06-01 |
| TYA110 | NordStar | 2 | 2026-06-03 |
| TYA107 | NordStar | 2 | 2026-05-24 |
| TYA101 | NordStar | 2 | 2026-04-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | TYA951 | SVX → VOG | Jul 13, 12:20 UTC | Jul 13, 12:40 UTC | 20m |
| 2026-07-12 | TYA322 | - | Jul 12, 09:15 UTC | Jul 12, 22:40 UTC | 13h 25m |
| 2026-07-11 | TYA321 | - | Jul 11, 12:20 UTC | Jul 12, 09:55 UTC | 21h 35m |
| 2026-07-11 | TYA321 | - | Jul 11, 12:10 UTC | Jul 12, 09:55 UTC | 21h 45m |
| 2026-07-09 | TYA4494 | - | Jul 9, 07:25 UTC | Jul 9, 07:45 UTC | 20m |
| 2026-07-09 | TYA4493 | - | Jul 9, 04:15 UTC | Jul 9, 04:35 UTC | 20m |
| 2026-07-06 | TYA106 | NSK → DME | Jul 6, 14:15 UTC | Jul 6, 21:40 UTC | 7h 25m |
| 2026-07-03 | TYA102 | NSK → DME | Jul 3, 03:25 UTC | Jul 3, 03:55 UTC | 30m |
| 2026-07-01 | TYA322 | - | Jul 1, 20:40 UTC | Jul 1, 21:20 UTC | 40m |
| 2026-06-28 | TYA302 | - | Jun 28, 20:34 UTC | Jun 29, 12:24 UTC | 15h 50m |
| 2026-06-28 | TYA302 | - | Jun 28, 17:00 UTC | Jun 28, 17:10 UTC | 10m |
| 2026-06-28 | TYA301 | KJA → LED | Jun 28, 10:30 UTC | Jun 28, 10:55 UTC | 25m |
| 2026-06-26 | TYA104 | - | Jun 26, 04:30 UTC | Jun 26, 23:19 UTC | 18h 50m |
| 2026-06-25 | TYA104 | - | Jun 25, 22:49 UTC | Jun 26, 22:14 UTC | 23h 25m |
| 2026-06-24 | TYA301 | KJA → LED | Jun 24, 13:05 UTC | Jun 24, 16:19 UTC | 3h 15m |
| 2026-06-22 | TYA103 | - | Jun 22, 04:19 UTC | Jun 22, 23:20 UTC | 19h 0m |
| 2026-06-22 | TYA103 | - | Jun 22, 04:09 UTC | Jun 22, 23:20 UTC | 19h 10m |
| 2026-06-21 | TYA301 | KJA → LED | Jun 21, 10:34 UTC | Jun 22, 04:40 UTC | 18h 5m |
| 2026-06-20 | TYA131 | - | Jun 20, 19:55 UTC | Jun 21, 00:10 UTC | 4h 15m |
| 2026-06-19 | TYA401 | DME → NSK | Jun 19, 23:34 UTC | Jun 20, 13:04 UTC | 13h 30m |
| 2026-06-19 | TYA102 | NSK → DME | Jun 19, 02:29 UTC | Jun 19, 04:50 UTC | 2h 20m |
| 2026-06-14 | TYA301 | KJA → LED | Jun 14, 10:40 UTC | Jun 14, 20:55 UTC | 10h 15m |
| 2026-06-13 | TYA301 | KJA → LED | Jun 13, 12:20 UTC | Jun 14, 11:10 UTC | 22h 51m |
| 2026-06-13 | TYA951 | SVX → VOG | Jun 13, 12:10 UTC | Jun 13, 12:25 UTC | 15m |
| 2026-06-12 | TYA104 | - | Jun 12, 07:00 UTC | Jun 12, 07:10 UTC | 10m |
| 2026-06-11 | TYA104 | - | Jun 11, 22:35 UTC | Jun 12, 06:10 UTC | 7h 36m |
| 2026-06-07 | TYA301 | KJA → LED | Jun 7, 12:40 UTC | Jun 7, 18:15 UTC | 5h 35m |
| 2026-06-06 | TYA301 | KJA → LED | Jun 6, 21:15 UTC | Jun 7, 18:15 UTC | 21h 0m |
| 2026-06-06 | TYA406 | NSK → LED | Jun 6, 12:35 UTC | Jun 6, 21:40 UTC | 9h 5m |
| 2026-06-04 | TYA103 | DME → NSK | Jun 4, 22:00 UTC | Jun 4, 22:30 UTC | 30m |
| 2026-06-04 | TYA1092 | KRO → DME | Jun 4, 02:55 UTC | Jun 4, 22:30 UTC | 19h 35m |
| 2026-06-03 | TYA110 | NSK → DME | Jun 3, 09:00 UTC | Jun 4, 03:35 UTC | 18h 35m |
| 2026-06-01 | TYA409 | DME → NSK | Jun 1, 04:20 UTC | Jun 1, 23:35 UTC | 19h 15m |
| 2026-06-01 | TYA409 | DME → NSK | Jun 1, 04:10 UTC | Jun 1, 23:35 UTC | 19h 25m |
| 2026-06-01 | TYA208 | - | Jun 1, 01:25 UTC | Jun 1, 23:35 UTC | 22h 10m |
| 2026-05-31 | TYA208 | - | May 31, 20:10 UTC | Jun 1, 09:40 UTC | 13h 30m |
| 2026-05-29 | TYA401 | - | May 29, 22:05 UTC | May 29, 23:20 UTC | 1h 15m |
| 2026-05-28 | TYA404 | NSK → DME | May 28, 02:35 UTC | May 28, 04:10 UTC | 1h 35m |
| 2026-05-27 | TYA103 | DME → NSK | May 27, 00:04 UTC | May 27, 01:24 UTC | 1h 20m |
| 2026-05-24 | TYA108 | KJA → DME | May 24, 20:00 UTC | May 25, 04:45 UTC | 8h 45m |
| 2026-05-24 | TYA107 | DME → KJA | May 24, 05:50 UTC | May 25, 04:15 UTC | 22h 25m |
| 2026-05-23 | TYA107 | DME → KJA | May 23, 22:50 UTC | May 24, 20:30 UTC | 21h 40m |
| 2026-05-23 | TYA104 | NSK → DME | May 23, 04:25 UTC | May 23, 23:10 UTC | 18h 45m |
| 2026-05-21 | TYA102 | NSK → DME | May 21, 15:10 UTC | May 22, 03:55 UTC | 12h 45m |
| 2026-05-20 | TYA925 | NSK → GOJ | May 20, 06:50 UTC | May 20, 15:10 UTC | 8h 20m |
| 2026-05-19 | TYA925 | NSK → GOJ | May 19, 14:30 UTC | May 20, 08:15 UTC | 17h 46m |
| 2026-05-19 | TYA4400 | DME → UFA | May 19, 04:35 UTC | May 19, 14:35 UTC | 10h 0m |
| 2026-05-17 | TYA410 | NSK → DME | May 17, 15:05 UTC | May 18, 03:15 UTC | 12h 10m |
| 2026-05-16 | TYA110 | NSK → DME | May 16, 15:05 UTC | May 17, 06:05 UTC | 15h 0m |
| 2026-05-16 | TYA102 | NSK → DME | May 16, 02:25 UTC | May 16, 15:35 UTC | 13h 11m |
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-73257 page for operator, model, and routing details .