sensors Mode-S transponder
151E25
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73253 · BOEING 737-800
- Hex
- 151E25
- Octal
- 05217045
- Decimal
- 1,383,973
- Country
- RU
- Tail
- RA-73253
- Type
- B738
- Flights observed
- 65
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 13h ago
Last known position
Country allocation
The ICAO 24-bit address 151E25 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 |
|---|---|---|---|
| TYA6101 | - | 5 | 2026-04-18 |
| TYA401 | - | 5 | 2026-05-29 |
| TYA6102 | - | 4 | 2026-04-16 |
| TYA403 | NordStar | 4 | 2026-05-19 |
| TYA402 | NordStar | 4 | 2026-04-22 |
| TYA7205 | - | 3 | 2026-05-10 |
| TYA416 | NordStar | 3 | 2026-05-01 |
| TYA107 | NordStar | 3 | 2026-05-29 |
| TYA925 | NordStar | 2 | 2026-05-13 |
| TYA7207 | - | 2 | 2026-05-09 |
| TYA7201 | - | 2 | 2026-05-08 |
| TYA414 | NordStar | 2 | 2026-05-19 |
| TYA412 | NordStar | 2 | 2026-05-29 |
| TYA111 | NordStar | 2 | 2026-04-17 |
| TYA106 | NordStar | 2 | 2026-04-26 |
| TYA102 | NordStar | 2 | 2026-04-29 |
| TYA9706 | - | 1 | 2026-04-27 |
| TYA9705 | - | 1 | 2026-04-26 |
| TYA9502 | NordStar | 1 | 2026-05-18 |
| TYA9032 | - | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | TYA107 | DME → KJA | May 29, 13:55 UTC | May 29, 23:00 UTC | 9h 5m |
| 2026-05-29 | TYA401 | - | May 29, 13:40 UTC | May 29, 13:50 UTC | 10m |
| 2026-05-29 | TYA412 | NSK → AER | May 29, 11:30 UTC | May 29, 11:50 UTC | 20m |
| 2026-05-25 | TYA4410 | KJA → UFA | May 25, 01:55 UTC | May 25, 14:35 UTC | 12h 40m |
| 2026-05-22 | TYA107 | DME → KJA | May 22, 07:55 UTC | May 22, 23:30 UTC | 15h 35m |
| 2026-05-19 | TYA403 | MRV → DME | May 19, 20:55 UTC | May 20, 15:05 UTC | 18h 11m |
| 2026-05-19 | TYA414 | NSK → MRV | May 19, 10:25 UTC | May 19, 21:00 UTC | 10h 35m |
| 2026-05-19 | TYA414 | NSK → MRV | May 19, 00:40 UTC | May 19, 21:00 UTC | 20h 20m |
| 2026-05-18 | TYA9502 | SKD → DME | May 18, 04:30 UTC | May 19, 01:10 UTC | 20h 39m |
| 2026-05-17 | TYA4552 | - | May 17, 12:45 UTC | May 18, 05:00 UTC | 16h 15m |
| 2026-05-16 | TYA4520 | KJA → OVB | May 16, 11:51 UTC | May 16, 12:31 UTC | 40m |
| 2026-05-15 | TYA4416 | UFA → NSK | May 15, 00:10 UTC | May 15, 00:20 UTC | 10m |
| 2026-05-13 | TYA925 | NSK → GOJ | May 13, 11:30 UTC | May 14, 00:30 UTC | 13h 0m |
| 2026-05-12 | TYA925 | NSK → GOJ | May 12, 15:40 UTC | May 13, 12:45 UTC | 21h 5m |
| 2026-05-10 | TYA7202 | - | May 10, 17:45 UTC | May 11, 11:25 UTC | 17h 40m |
| 2026-05-10 | TYA7205 | - | May 10, 06:15 UTC | May 10, 15:09 UTC | 8h 55m |
| 2026-05-10 | TYA7205 | - | May 10, 05:25 UTC | May 10, 05:34 UTC | 10m |
| 2026-05-10 | TYA7208 | - | May 10, 03:30 UTC | May 10, 03:50 UTC | 20m |
| 2026-05-09 | TYA7207 | - | May 9, 18:00 UTC | May 10, 02:39 UTC | 8h 40m |
| 2026-05-09 | TYA7207 | - | May 9, 17:00 UTC | May 9, 17:15 UTC | 15m |
| 2026-05-09 | TYA7206 | - | May 9, 15:05 UTC | May 9, 15:30 UTC | 25m |
| 2026-05-09 | TYA7205 | - | May 9, 03:40 UTC | May 9, 14:20 UTC | 10h 40m |
| 2026-05-09 | TYA7204 | - | May 9, 01:00 UTC | May 9, 01:20 UTC | 20m |
| 2026-05-08 | TYA7203 | - | May 8, 14:25 UTC | May 9, 00:15 UTC | 9h 50m |
| 2026-05-08 | TYA7201 | - | May 8, 12:39 UTC | May 8, 12:55 UTC | 15m |
| 2026-05-08 | TYA7201 | - | May 8, 08:49 UTC | May 8, 11:49 UTC | 3h 0m |
| 2026-05-05 | TYA107 | DME → KJA | May 5, 22:40 UTC | May 5, 23:05 UTC | 25m |
| 2026-05-03 | TYA108 | KJA → DME | May 3, 22:34 UTC | May 4, 04:39 UTC | 6h 5m |
| 2026-05-03 | TYA412 | NSK → AER | May 3, 10:35 UTC | May 3, 10:45 UTC | 10m |
| 2026-05-01 | TYA416 | NSK → LED | May 1, 03:20 UTC | May 1, 23:15 UTC | 19h 55m |
| 2026-05-01 | TYA416 | NSK → LED | May 1, 02:50 UTC | May 1, 23:15 UTC | 20h 25m |
| 2026-04-30 | TYA416 | NSK → LED | Apr 30, 20:20 UTC | May 1, 04:55 UTC | 8h 35m |
| 2026-04-29 | TYA102 | NSK → DME | Apr 29, 21:20 UTC | Apr 30, 16:25 UTC | 19h 5m |
| 2026-04-29 | TYA102 | NSK → DME | Apr 29, 20:20 UTC | Apr 30, 16:25 UTC | 20h 5m |
| 2026-04-28 | TYA4214 | KUF → DME | Apr 28, 09:55 UTC | Apr 28, 15:20 UTC | 5h 25m |
| 2026-04-27 | TYA9706 | - | Apr 27, 10:10 UTC | Apr 27, 11:15 UTC | 1h 5m |
| 2026-04-26 | TYA9705 | - | Apr 26, 14:20 UTC | Apr 27, 07:35 UTC | 17h 15m |
| 2026-04-26 | TYA106 | NSK → DME | Apr 26, 05:10 UTC | Apr 26, 14:35 UTC | 9h 25m |
| 2026-04-24 | TYA401 | DME → NSK | Apr 24, 22:10 UTC | Apr 24, 23:20 UTC | 1h 10m |
| 2026-04-24 | TYA401 | DME → NSK | Apr 24, 03:20 UTC | Apr 24, 23:20 UTC | 20h 0m |
| 2026-04-24 | TYA401 | DME → NSK | Apr 24, 02:30 UTC | Apr 24, 23:20 UTC | 20h 50m |
| 2026-04-23 | TYA404 | NSK → DME | Apr 23, 04:30 UTC | Apr 23, 04:45 UTC | 15m |
| 2026-04-22 | TYA101 | DME → NSK | Apr 22, 19:45 UTC | Apr 23, 03:00 UTC | 7h 15m |
| 2026-04-22 | TYA402 | NSK → DME | Apr 22, 04:35 UTC | Apr 22, 04:45 UTC | 10m |
| 2026-04-21 | TYA402 | NSK → DME | Apr 21, 21:05 UTC | Apr 22, 03:50 UTC | 6h 45m |
| 2026-04-21 | TYA403 | MRV → DME | Apr 21, 19:40 UTC | Apr 21, 19:55 UTC | 15m |
| 2026-04-21 | TYA106 | NSK → DME | Apr 21, 06:30 UTC | Apr 21, 07:55 UTC | 1h 25m |
| 2026-04-19 | TYA401 | DME → NSK | Apr 19, 21:25 UTC | Apr 19, 23:20 UTC | 1h 55m |
| 2026-04-18 | TYA6101 | - | Apr 18, 09:40 UTC | Apr 18, 16:30 UTC | 6h 50m |
| 2026-04-17 | TYA112 | - | Apr 17, 13:35 UTC | Apr 17, 15:00 UTC | 1h 24m |
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-73253 page for operator, model, and routing details .