sensors Mode-S transponder
101000
ICAO 24-bit transponder address · allocated to Russia
- Hex
- 101000
- Octal
- 04010000
- Decimal
- 1,052,672
- Country
- RU
- Flights observed
- 26
- Distinct callsigns
- 8
- Country
- RU
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 101000 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 8 distinct
Recent flights last 26
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-25 | HALCON5 | - | Jun 25, 13:50 UTC | Jun 25, 14:09 UTC | 20m |
| 2026-06-24 | HALCON6 | - | Jun 24, 18:34 UTC | Jun 24, 18:50 UTC | 15m |
| 2026-06-23 | HALCON5 | - | Jun 23, 18:14 UTC | Jun 23, 18:34 UTC | 20m |
| 2026-06-23 | HALCON6 | - | Jun 23, 15:30 UTC | Jun 23, 16:20 UTC | 50m |
| 2026-06-23 | HALCON6 | - | Jun 23, 13:05 UTC | Jun 23, 13:45 UTC | 40m |
| 2026-06-22 | HALCON7 | - | Jun 22, 18:00 UTC | Jun 22, 18:44 UTC | 45m |
| 2026-06-18 | HALCON7 | - | Jun 18, 14:45 UTC | Jun 18, 14:55 UTC | 10m |
| 2026-06-16 | HALCON7 | - | Jun 16, 15:15 UTC | Jun 16, 15:55 UTC | 40m |
| 2026-06-15 | HALCON7 | - | Jun 15, 17:40 UTC | Jun 15, 18:20 UTC | 40m |
| 2026-06-15 | HALCON7 | - | Jun 15, 14:34 UTC | Jun 15, 15:15 UTC | 40m |
| 2026-06-05 | HALCON3 | - | Jun 5, 14:25 UTC | Jun 5, 14:45 UTC | 20m |
| 2026-06-02 | HALCON2 | - | Jun 2, 19:50 UTC | Jun 2, 20:05 UTC | 15m |
| 2026-05-20 | HALCON7 | - | May 20, 17:55 UTC | May 20, 18:35 UTC | 40m |
| 2026-05-20 | HALCON7 | - | May 20, 12:55 UTC | May 20, 13:40 UTC | 45m |
| 2026-05-19 | HALCON6 | - | May 19, 18:35 UTC | May 19, 19:25 UTC | 50m |
| 2026-05-19 | HALCON7 | - | May 19, 13:40 UTC | May 19, 14:25 UTC | 45m |
| 2026-05-13 | HALCON7 | - | May 13, 19:30 UTC | May 13, 19:45 UTC | 15m |
| 2026-05-13 | HALCON7 | - | May 13, 17:25 UTC | May 13, 18:00 UTC | 35m |
| 2026-05-12 | HALCON4 | - | May 12, 19:20 UTC | May 12, 20:05 UTC | 45m |
| 2026-05-12 | HALCON7 | - | May 12, 17:10 UTC | May 12, 18:15 UTC | 1h 5m |
| 2026-05-11 | HALCON5 | - | May 11, 18:20 UTC | May 11, 19:10 UTC | 50m |
| 2026-05-11 | HALCON5 | - | May 11, 16:20 UTC | May 11, 17:05 UTC | 46m |
| 2026-05-08 | HALCON1 | - | May 8, 15:10 UTC | May 8, 15:45 UTC | 35m |
| 2026-05-08 | HALCON1 | - | May 8, 13:15 UTC | May 8, 14:00 UTC | 45m |
| 2026-05-07 | HALCON7 | - | May 7, 18:05 UTC | May 7, 18:45 UTC | 40m |
| 2026-05-06 | HALCONES | - | May 6, 13:25 UTC | May 6, 14:15 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.