sensors Mode-S transponder
151E2A
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73258 · BOEING 737-800
- Hex
- 151E2A
- Octal
- 05217052
- Decimal
- 1,383,978
- Country
- RU
- Tail
- RA-73258
- Type
- B738
- Flights observed
- 37
- Distinct callsigns
- 19
- Country
- RU
- Last broadcast
- 4h ago
Last known position
Country allocation
The ICAO 24-bit address 151E2A 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 19 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| TYA104 | NordStar | 7 | 2026-05-20 |
| TYA416 | NordStar | 3 | 2026-05-08 |
| TYA404 | NordStar | 3 | 2026-05-14 |
| TYA106 | NordStar | 3 | 2026-04-14 |
| TYA101 | NordStar | 3 | 2026-05-29 |
| TYA927 | NordStar | 2 | 2026-05-04 |
| TYA406 | NordStar | 2 | 2026-04-26 |
| TYA403 | - | 2 | 2026-04-16 |
| TYA401 | NordStar | 2 | 2026-04-29 |
| TYA952 | NordStar | 1 | 2026-05-25 |
| TYA928 | NordStar | 1 | 2026-04-27 |
| TYA925 | NordStar | 1 | 2026-05-26 |
| TYA907 | - | 1 | 2026-04-18 |
| TYA405 | NordStar | 1 | 2026-04-19 |
| TYA402 | NordStar | 1 | 2026-04-29 |
| TYA301 | NordStar | 1 | 2026-05-13 |
| TYA108 | NordStar | 1 | 2026-05-17 |
| TYA103 | NordStar | 1 | 2026-05-16 |
| TY110 | - | 1 | 2026-05-29 |
Recent flights last 37
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TYA101 | DME → NSK | May 29, 19:35 UTC | May 29, 20:55 UTC | 1h 20m |
| 2026-05-29 | TY110 | - | May 29, 14:15 UTC | May 29, 16:30 UTC | 2h 15m |
| 2026-05-26 | TYA925 | NSK → GOJ | May 26, 20:29 UTC | May 27, 09:20 UTC | 12h 50m |
| 2026-05-25 | TYA952 | VOG → SVX | May 25, 16:15 UTC | May 25, 16:35 UTC | 20m |
| 2026-05-20 | TYA104 | NSK → DME | May 20, 04:35 UTC | May 21, 02:40 UTC | 22h 6m |
| 2026-05-19 | TYA104 | NSK → DME | May 19, 10:35 UTC | May 20, 05:40 UTC | 19h 6m |
| 2026-05-19 | TYA104 | NSK → DME | May 19, 09:25 UTC | May 20, 05:40 UTC | 20h 16m |
| 2026-05-17 | TYA108 | KJA → DME | May 17, 22:40 UTC | May 18, 04:51 UTC | 6h 11m |
| 2026-05-16 | TYA103 | DME → NSK | May 16, 21:25 UTC | May 16, 23:25 UTC | 2h 0m |
| 2026-05-15 | TYA104 | NSK → DME | May 15, 22:25 UTC | May 16, 05:20 UTC | 6h 55m |
| 2026-05-14 | TYA404 | NSK → DME | May 14, 02:35 UTC | May 14, 21:10 UTC | 18h 35m |
| 2026-05-13 | TYA301 | KJA → LED | May 13, 13:00 UTC | May 14, 03:05 UTC | 14h 5m |
| 2026-05-08 | TYA416 | NSK → LED | May 8, 04:34 UTC | May 8, 23:05 UTC | 18h 30m |
| 2026-05-08 | TYA416 | NSK → LED | May 8, 03:24 UTC | May 8, 23:05 UTC | 19h 40m |
| 2026-05-07 | TYA416 | NSK → LED | May 7, 21:15 UTC | May 8, 05:35 UTC | 8h 20m |
| 2026-05-06 | TYA104 | NSK → DME | May 6, 10:40 UTC | May 7, 06:10 UTC | 19h 29m |
| 2026-05-06 | TYA104 | NSK → DME | May 6, 07:45 UTC | May 7, 06:10 UTC | 22h 24m |
| 2026-05-04 | TYA927 | PEE → KZN | May 4, 16:50 UTC | May 4, 17:00 UTC | 10m |
| 2026-04-29 | TYA401 | DME → NSK | Apr 29, 14:35 UTC | Apr 29, 14:45 UTC | 10m |
| 2026-04-29 | TYA402 | NSK → DME | Apr 29, 02:24 UTC | Apr 29, 04:44 UTC | 2h 20m |
| 2026-04-27 | TYA928 | KZN → PEE | Apr 27, 17:05 UTC | Apr 27, 17:35 UTC | 30m |
| 2026-04-27 | TYA927 | PEE → KZN | Apr 27, 13:30 UTC | Apr 27, 14:05 UTC | 35m |
| 2026-04-26 | TYA406 | NSK → LED | Apr 26, 04:25 UTC | Apr 26, 20:50 UTC | 16h 25m |
| 2026-04-25 | TYA406 | NSK → LED | Apr 25, 22:35 UTC | Apr 26, 20:50 UTC | 22h 15m |
| 2026-04-23 | TYA104 | NSK → DME | Apr 23, 15:15 UTC | Apr 24, 05:55 UTC | 14h 40m |
| 2026-04-22 | TYA401 | DME → NSK | Apr 22, 21:15 UTC | Apr 23, 15:20 UTC | 18h 5m |
| 2026-04-19 | TYA405 | LED → NSK | Apr 19, 20:45 UTC | Apr 19, 21:45 UTC | 1h 0m |
| 2026-04-18 | TYA907 | - | Apr 18, 12:05 UTC | Apr 18, 12:40 UTC | 35m |
| 2026-04-16 | TYA403 | - | Apr 16, 19:30 UTC | Apr 16, 20:45 UTC | 1h 15m |
| 2026-04-16 | TYA403 | - | Apr 16, 15:50 UTC | Apr 16, 16:00 UTC | 10m |
| 2026-04-16 | TYA404 | NSK → DME | Apr 16, 03:09 UTC | Apr 16, 03:55 UTC | 45m |
| 2026-04-16 | TYA404 | NSK → DME | Apr 16, 02:24 UTC | Apr 16, 03:04 UTC | 40m |
| 2026-04-15 | TYA101 | DME → NSK | Apr 15, 21:10 UTC | Apr 15, 21:50 UTC | 40m |
| 2026-04-15 | TYA101 | DME → NSK | Apr 15, 19:30 UTC | Apr 15, 20:50 UTC | 1h 20m |
| 2026-04-14 | TYA106 | NSK → DME | Apr 14, 08:40 UTC | Apr 14, 08:55 UTC | 15m |
| 2026-04-14 | TYA106 | NSK → DME | Apr 14, 07:15 UTC | Apr 14, 07:50 UTC | 35m |
| 2026-04-14 | TYA106 | NSK → DME | Apr 14, 06:30 UTC | Apr 14, 07:05 UTC | 35m |
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-73258 page for operator, model, and routing details .