sensors Mode-S transponder
151E23
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73251 · BOEING 737-800
- Hex
- 151E23
- Octal
- 05217043
- Decimal
- 1,383,971
- Country
- RU
- Tail
- RA-73251
- Type
- B738
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 151E23 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 |
|---|---|---|---|
| TYA416 | NordStar | 5 | 2026-05-21 |
| TYA414 | NordStar | 4 | 2026-06-06 |
| TYA412 | NordStar | 4 | 2026-06-07 |
| TYA102 | NordStar | 4 | 2026-05-29 |
| TYA301 | NordStar | 3 | 2026-05-30 |
| TYA104 | NordStar | 3 | 2026-06-01 |
| TYA927 | NordStar | 2 | 2026-05-25 |
| TYA4520 | NordStar | 2 | 2026-05-14 |
| TYA415 | NordStar | 2 | 2026-05-22 |
| TYA406 | NordStar | 2 | 2026-05-13 |
| TYA131 | NordStar | 2 | 2026-05-23 |
| TYA9611 | - | 1 | 2026-06-02 |
| TYA952 | NordStar | 1 | 2026-06-08 |
| TYA915 | NordStar | 1 | 2026-04-26 |
| TYA912 | NordStar | 1 | 2026-05-24 |
| TYA910 | NordStar | 1 | 2026-06-09 |
| TYA4553 | - | 1 | 2026-05-14 |
| TYA4552 | - | 1 | 2026-05-29 |
| TYA4551 | - | 1 | 2026-04-26 |
| TYA4400 | NordStar | 1 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-10 | TYA101 | DME → NSK | Jun 10, 21:40 UTC | Jun 10, 22:15 UTC | 35m |
| 2026-06-09 | TYA910 | KUF → TJM | Jun 9, 20:25 UTC | Jun 9, 20:45 UTC | 20m |
| 2026-06-08 | TYA952 | VOG → SVX | Jun 8, 16:10 UTC | Jun 8, 16:50 UTC | 40m |
| 2026-06-08 | TYA322 | AER → KJA | Jun 8, 00:25 UTC | Jun 8, 01:05 UTC | 40m |
| 2026-06-07 | TYA412 | NSK → AER | Jun 7, 09:50 UTC | Jun 7, 11:40 UTC | 1h 50m |
| 2026-06-06 | TYA412 | NSK → AER | Jun 6, 10:50 UTC | Jun 7, 10:45 UTC | 23h 55m |
| 2026-06-06 | TYA414 | NSK → MRV | Jun 6, 10:04 UTC | Jun 6, 11:14 UTC | 1h 10m |
| 2026-06-05 | TYA4400 | DME → UFA | Jun 5, 08:25 UTC | Jun 5, 08:50 UTC | 25m |
| 2026-06-04 | TYA1032 | AER → DME | Jun 4, 10:50 UTC | Jun 4, 11:15 UTC | 25m |
| 2026-06-03 | TYA412 | NSK → AER | Jun 3, 17:05 UTC | Jun 4, 09:15 UTC | 16h 10m |
| 2026-06-03 | TYA412 | NSK → AER | Jun 3, 08:55 UTC | Jun 4, 08:45 UTC | 23h 50m |
| 2026-06-02 | TYA9611 | - | Jun 2, 11:40 UTC | Jun 3, 09:10 UTC | 21h 30m |
| 2026-06-01 | TYA4211 | DME → KUF | Jun 1, 18:40 UTC | Jun 2, 11:50 UTC | 17h 10m |
| 2026-06-01 | TYA104 | NSK → DME | Jun 1, 04:30 UTC | Jun 1, 05:55 UTC | 1h 25m |
| 2026-05-30 | TYA301 | KJA → LED | May 30, 00:50 UTC | May 30, 16:45 UTC | 15h 55m |
| 2026-05-29 | TYA4552 | - | May 29, 15:30 UTC | May 30, 13:05 UTC | 21h 35m |
| 2026-05-29 | TYA102 | NSK → DME | May 29, 02:30 UTC | May 29, 13:15 UTC | 10h 45m |
| 2026-05-26 | TYA104 | NSK → DME | May 26, 04:35 UTC | May 26, 21:40 UTC | 17h 5m |
| 2026-05-25 | TYA927 | PEE → KZN | May 25, 16:55 UTC | May 25, 17:20 UTC | 25m |
| 2026-05-24 | TYA912 | UFA → NSK | May 24, 07:00 UTC | May 24, 20:50 UTC | 13h 50m |
| 2026-05-23 | TYA131 | AER → ABA | May 23, 21:05 UTC | May 24, 20:45 UTC | 23h 40m |
| 2026-05-23 | TYA131 | AER → ABA | May 23, 08:50 UTC | May 24, 07:00 UTC | 22h 11m |
| 2026-05-23 | TYA132 | ABA → AER | May 23, 07:50 UTC | May 23, 22:05 UTC | 14h 15m |
| 2026-05-22 | TYA415 | LED → NSK | May 22, 21:15 UTC | May 22, 21:30 UTC | 15m |
| 2026-05-21 | TYA416 | NSK → LED | May 21, 21:45 UTC | May 22, 03:25 UTC | 5h 40m |
| 2026-05-20 | TYA301 | KJA → LED | May 20, 13:25 UTC | May 21, 03:50 UTC | 14h 25m |
| 2026-05-19 | TYA102 | NSK → DME | May 19, 07:30 UTC | May 19, 13:40 UTC | 6h 10m |
| 2026-05-18 | TYA102 | NSK → DME | May 18, 16:25 UTC | May 19, 13:40 UTC | 21h 14m |
| 2026-05-16 | TYA414 | NSK → MRV | May 16, 04:00 UTC | May 16, 21:40 UTC | 17h 40m |
| 2026-05-16 | TYA414 | NSK → MRV | May 16, 00:00 UTC | May 16, 21:40 UTC | 21h 40m |
| 2026-05-15 | TYA414 | NSK → MRV | May 15, 16:00 UTC | May 16, 12:16 UTC | 20h 16m |
| 2026-05-14 | TYA4553 | - | May 14, 17:25 UTC | May 15, 16:30 UTC | 23h 4m |
| 2026-05-14 | TYA4520 | KJA → OVB | May 14, 12:20 UTC | May 14, 17:45 UTC | 5h 25m |
| 2026-05-13 | TYA4520 | KJA → OVB | May 13, 20:50 UTC | May 14, 17:45 UTC | 20h 55m |
| 2026-05-13 | TYA406 | NSK → LED | May 13, 12:50 UTC | May 14, 12:45 UTC | 23h 55m |
| 2026-05-13 | TYA406 | NSK → LED | May 13, 12:40 UTC | May 13, 21:20 UTC | 8h 40m |
| 2026-05-12 | TYA104 | NSK → DME | May 12, 04:30 UTC | May 12, 05:10 UTC | 40m |
| 2026-05-11 | TYA927 | PEE → KZN | May 11, 16:35 UTC | May 11, 16:55 UTC | 20m |
| 2026-05-05 | TYA415 | LED → NSK | May 5, 22:15 UTC | May 6, 05:15 UTC | 7h 0m |
| 2026-05-05 | TYA416 | NSK → LED | May 5, 04:50 UTC | May 6, 04:45 UTC | 23h 55m |
| 2026-05-05 | TYA416 | NSK → LED | May 5, 04:30 UTC | May 5, 23:05 UTC | 18h 35m |
| 2026-05-04 | TYA416 | NSK → LED | May 4, 10:50 UTC | May 5, 06:25 UTC | 19h 36m |
| 2026-05-04 | TYA416 | NSK → LED | May 4, 09:40 UTC | May 5, 06:25 UTC | 20h 46m |
| 2026-05-02 | TYA102 | NSK → DME | May 2, 21:00 UTC | May 3, 03:10 UTC | 6h 10m |
| 2026-04-29 | TYA4212 | - | Apr 29, 07:59 UTC | Apr 29, 08:10 UTC | 10m |
| 2026-04-28 | TYA106 | NSK → DME | Apr 28, 06:45 UTC | Apr 28, 08:15 UTC | 1h 30m |
| 2026-04-26 | TYA4551 | - | Apr 26, 15:45 UTC | Apr 26, 16:20 UTC | 35m |
| 2026-04-26 | TYA915 | NSK → OVB | Apr 26, 06:15 UTC | Apr 26, 06:45 UTC | 30m |
| 2026-04-23 | TYA302 | LED → KJA | Apr 23, 16:50 UTC | Apr 23, 20:55 UTC | 4h 4m |
| 2026-04-23 | TYA301 | KJA → LED | Apr 23, 13:35 UTC | Apr 23, 14:25 UTC | 50m |
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-73251 page for operator, model, and routing details .