sensors Mode-S transponder
151E83
ICAO 24-bit transponder address · allocated to Russia
Currently assigned to RA-73347 · BOEING 777-200
- Hex
- 151E83
- Octal
- 05217203
- Decimal
- 1,384,067
- Country
- RU
- Tail
- RA-73347
- Type
- B772
- Flights observed
- 116
- Distinct callsigns
- 20
- Country
- RU
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 151E83 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 |
|---|---|---|---|
| KAR3548 | - | 22 | 2026-07-11 |
| KAR3547 | - | 12 | 2026-07-05 |
| KAR3545 | - | 10 | 2026-06-22 |
| KAR3542 | Kar-Air | 9 | 2026-07-06 |
| KAR3434 | Kar-Air | 7 | 2026-06-25 |
| KAR3477 | - | 5 | 2026-07-04 |
| KAR3541 | - | 4 | 2026-07-08 |
| KAR3002 | Kar-Air | 4 | 2026-06-19 |
| KAR3001 | Kar-Air | 4 | 2026-06-18 |
| KAR3659 | Kar-Air | 3 | 2026-06-07 |
| KAR3658 | - | 3 | 2026-07-08 |
| KAR3657 | - | 3 | 2026-07-11 |
| KAR3655 | - | 3 | 2026-07-06 |
| KAR3546 | Kar-Air | 3 | 2026-06-09 |
| KAR3538 | Kar-Air | 3 | 2026-06-24 |
| KAR3520 | Kar-Air | 3 | 2026-06-08 |
| KAR3004 | - | 3 | 2026-06-19 |
| KAR3645 | - | 2 | 2026-07-10 |
| KAR3537 | Kar-Air | 2 | 2026-06-25 |
| KAR3516 | Kar-Air | 2 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-11 | KAR3548 | - | Jul 11, 23:25 UTC | Jul 12, 04:30 UTC | 5h 5m |
| 2026-07-11 | KAR3657 | - | Jul 11, 04:20 UTC | Jul 11, 23:50 UTC | 19h 30m |
| 2026-07-10 | KAR3657 | - | Jul 10, 23:45 UTC | Jul 11, 04:50 UTC | 5h 5m |
| 2026-07-10 | KAR3646 | HKT → OVB | Jul 10, 06:50 UTC | Jul 10, 20:55 UTC | 14h 5m |
| 2026-07-10 | KAR3645 | - | Jul 10, 02:15 UTC | Jul 10, 20:55 UTC | 18h 40m |
| 2026-07-09 | KAR3516 | HKT → OVB | Jul 9, 00:50 UTC | Jul 9, 20:05 UTC | 19h 15m |
| 2026-07-09 | KAR3516 | HKT → OVB | Jul 9, 00:20 UTC | Jul 9, 20:05 UTC | 19h 45m |
| 2026-07-08 | KAR3658 | - | Jul 8, 10:35 UTC | Jul 8, 21:15 UTC | 10h 40m |
| 2026-07-08 | KAR3541 | - | Jul 8, 02:40 UTC | Jul 8, 02:50 UTC | 10m |
| 2026-07-06 | KAR3542 | CXR → LED | Jul 6, 22:55 UTC | Jul 7, 18:20 UTC | 19h 25m |
| 2026-07-06 | KAR3655 | - | Jul 6, 09:15 UTC | Jul 6, 23:25 UTC | 14h 10m |
| 2026-07-06 | KAR3655 | - | Jul 6, 03:00 UTC | Jul 6, 23:25 UTC | 20h 25m |
| 2026-07-05 | KAR3547 | - | Jul 5, 22:55 UTC | Jul 6, 09:45 UTC | 10h 50m |
| 2026-07-04 | KAR3477 | - | Jul 4, 04:50 UTC | Jul 4, 16:05 UTC | 11h 15m |
| 2026-06-26 | KAR3548 | - | Jun 26, 18:34 UTC | Jun 27, 00:00 UTC | 5h 25m |
| 2026-06-26 | KAR3548 | - | Jun 26, 01:54 UTC | Jun 27, 00:00 UTC | 22h 5m |
| 2026-06-25 | KAR3537 | SVX → CXR | Jun 25, 21:25 UTC | Jun 26, 19:14 UTC | 21h 50m |
| 2026-06-25 | KAR3434 | HKT → SVX | Jun 25, 08:45 UTC | Jun 26, 02:34 UTC | 17h 50m |
| 2026-06-25 | KAR3434 | HKT → SVX | Jun 25, 04:49 UTC | Jun 26, 02:34 UTC | 21h 45m |
| 2026-06-25 | KAR3434 | HKT → SVX | Jun 25, 04:40 UTC | Jun 26, 02:34 UTC | 21h 55m |
| 2026-06-24 | KAR3434 | HKT → SVX | Jun 24, 23:14 UTC | Jun 25, 21:55 UTC | 22h 40m |
| 2026-06-24 | KAR3538 | CXR → SVX | Jun 24, 03:40 UTC | Jun 24, 23:40 UTC | 20h 0m |
| 2026-06-23 | KAR3657 | OVB → CXR | Jun 23, 13:24 UTC | Jun 24, 04:10 UTC | 14h 45m |
| 2026-06-23 | KAR3658 | CXR → OVB | Jun 23, 05:00 UTC | Jun 23, 10:24 UTC | 5h 25m |
| 2026-06-22 | KAR3545 | - | Jun 22, 10:49 UTC | Jun 23, 10:24 UTC | 23h 35m |
| 2026-06-22 | KAR3545 | - | Jun 22, 08:50 UTC | Jun 23, 05:29 UTC | 20h 40m |
| 2026-06-22 | KAR3545 | - | Jun 22, 08:44 UTC | Jun 23, 05:29 UTC | 20h 45m |
| 2026-06-22 | KAR3545 | - | Jun 22, 05:24 UTC | Jun 22, 12:44 UTC | 7h 20m |
| 2026-06-22 | KAR3545 | SVO → SVO | Jun 22, 04:19 UTC | Jun 22, 04:40 UTC | 20m |
| 2026-06-21 | KAR3547 | - | Jun 21, 02:55 UTC | Jun 21, 16:54 UTC | 14h 0m |
| 2026-06-19 | KAR3002 | AYT → SVO | Jun 19, 23:49 UTC | Jun 20, 01:24 UTC | 1h 35m |
| 2026-06-19 | KAR3004 | - | Jun 19, 08:40 UTC | Jun 19, 21:44 UTC | 13h 5m |
| 2026-06-18 | KAR3002 | AYT → SVO | Jun 18, 19:25 UTC | Jun 18, 21:05 UTC | 1h 40m |
| 2026-06-18 | KAR3001 | SVO → AYT | Jun 18, 16:05 UTC | Jun 18, 17:25 UTC | 1h 20m |
| 2026-06-15 | KAR3004 | - | Jun 15, 04:40 UTC | Jun 15, 06:24 UTC | 1h 45m |
| 2026-06-15 | KAR3003 | - | Jun 15, 01:55 UTC | Jun 15, 02:39 UTC | 45m |
| 2026-06-14 | KAR3003 | SVO → SVO | Jun 14, 22:00 UTC | Jun 14, 22:50 UTC | 50m |
| 2026-06-14 | KAR3002 | AYT → SVO | Jun 14, 10:20 UTC | Jun 14, 13:45 UTC | 3h 25m |
| 2026-06-14 | KAR3001 | SVO → AYT | Jun 14, 07:15 UTC | Jun 14, 07:45 UTC | 30m |
| 2026-06-14 | KAR3001 | SVO → AYT | Jun 14, 03:25 UTC | Jun 14, 03:55 UTC | 30m |
| 2026-06-13 | KAR3548 | - | Jun 13, 21:05 UTC | Jun 13, 22:05 UTC | 1h 0m |
| 2026-06-13 | KAR3548 | - | Jun 13, 05:00 UTC | Jun 13, 20:15 UTC | 15h 15m |
| 2026-06-12 | KAR3548 | - | Jun 12, 15:25 UTC | Jun 13, 13:10 UTC | 21h 44m |
| 2026-06-12 | KAR3655 | KJA → CXR | Jun 12, 08:50 UTC | Jun 13, 05:35 UTC | 20h 44m |
| 2026-06-12 | KAR3547 | - | Jun 12, 06:50 UTC | Jun 13, 05:35 UTC | 22h 44m |
| 2026-06-12 | KAR3547 | - | Jun 12, 04:40 UTC | Jun 12, 15:55 UTC | 11h 15m |
| 2026-06-11 | KAR3547 | - | Jun 11, 16:10 UTC | Jun 12, 08:50 UTC | 16h 41m |
| 2026-06-11 | KAR3547 | - | Jun 11, 11:15 UTC | Jun 12, 08:50 UTC | 21h 36m |
| 2026-06-11 | KAR3547 | - | Jun 11, 06:50 UTC | Jun 12, 06:45 UTC | 23h 56m |
| 2026-06-11 | KAR3548 | - | Jun 11, 04:50 UTC | Jun 12, 04:45 UTC | 23h 56m |
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-73347 page for operator, model, and routing details .