sensors Mode-S transponder
00B05E
ICAO 24-bit transponder address · allocated to South Africa
- Hex
- 00B05E
- Octal
- 00130136
- Decimal
- 45,150
- Country
- ZA
- Flights observed
- 53
- Distinct callsigns
- 1
- Country
- ZA
- Last broadcast
- 5h ago
Last known position
Country allocation
The ICAO 24-bit address 00B05E falls within the block assigned to South Africa (ZA) by ICAO Annex 10, Volume III. Every aircraft registered in South Africa 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ZSSHP | - | 53 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | ZSSHP | - | Jul 24, 11:40 UTC | Jul 24, 11:55 UTC | 15m |
| 2026-07-24 | ZSSHP | - | Jul 24, 08:50 UTC | Jul 24, 09:25 UTC | 35m |
| 2026-07-24 | ZSSHP | - | Jul 24, 07:45 UTC | Jul 24, 08:10 UTC | 25m |
| 2026-07-23 | ZSSHP | - | Jul 23, 07:45 UTC | Jul 23, 08:25 UTC | 40m |
| 2026-07-23 | ZSSHP | - | Jul 23, 05:35 UTC | Jul 23, 05:55 UTC | 20m |
| 2026-07-19 | ZSSHP | - | Jul 19, 13:05 UTC | Jul 19, 13:45 UTC | 40m |
| 2026-07-19 | ZSSHP | - | Jul 19, 10:00 UTC | Jul 19, 10:25 UTC | 25m |
| 2026-07-19 | ZSSHP | - | Jul 19, 08:35 UTC | Jul 19, 09:00 UTC | 25m |
| 2026-07-17 | ZSSHP | - | Jul 17, 12:55 UTC | Jul 17, 13:25 UTC | 30m |
| 2026-07-17 | ZSSHP | - | Jul 17, 11:04 UTC | Jul 17, 11:35 UTC | 30m |
| 2026-07-15 | ZSSHP | - | Jul 15, 12:25 UTC | Jul 15, 12:40 UTC | 15m |
| 2026-07-15 | ZSSHP | - | Jul 15, 09:20 UTC | Jul 15, 09:35 UTC | 15m |
| 2026-07-15 | ZSSHP | - | Jul 15, 08:25 UTC | Jul 15, 08:50 UTC | 25m |
| 2026-07-15 | ZSSHP | - | Jul 15, 06:00 UTC | Jul 15, 06:35 UTC | 35m |
| 2026-07-12 | ZSSHP | - | Jul 12, 09:40 UTC | Jul 12, 10:10 UTC | 30m |
| 2026-07-09 | ZSSHP | - | Jul 9, 08:30 UTC | Jul 9, 09:05 UTC | 35m |
| 2026-07-01 | ZSSHP | - | Jul 1, 06:05 UTC | Jul 1, 06:30 UTC | 25m |
| 2026-06-29 | ZSSHP | - | Jun 29, 12:14 UTC | Jun 29, 12:49 UTC | 35m |
| 2026-06-22 | ZSSHP | - | Jun 22, 08:44 UTC | Jun 22, 09:45 UTC | 1h 0m |
| 2026-06-19 | ZSSHP | - | Jun 19, 11:09 UTC | Jun 19, 12:25 UTC | 1h 15m |
| 2026-06-19 | ZSSHP | - | Jun 19, 07:34 UTC | Jun 19, 08:04 UTC | 30m |
| 2026-06-19 | ZSSHP | - | Jun 19, 04:34 UTC | Jun 19, 05:05 UTC | 30m |
| 2026-06-18 | ZSSHP | - | Jun 18, 13:30 UTC | Jun 18, 14:30 UTC | 1h 0m |
| 2026-06-11 | ZSSHP | - | Jun 11, 18:00 UTC | Jun 11, 18:35 UTC | 35m |
| 2026-06-09 | ZSSHP | - | Jun 9, 03:40 UTC | Jun 9, 04:15 UTC | 35m |
| 2026-06-03 | ZSSHP | - | Jun 3, 10:15 UTC | Jun 3, 10:45 UTC | 30m |
| 2026-06-03 | ZSSHP | - | Jun 3, 08:35 UTC | Jun 3, 09:10 UTC | 35m |
| 2026-06-01 | ZSSHP | - | Jun 1, 10:30 UTC | Jun 1, 10:45 UTC | 15m |
| 2026-06-01 | ZSSHP | CPT → CPT | Jun 1, 08:40 UTC | Jun 1, 09:20 UTC | 40m |
| 2026-05-28 | ZSSHP | - | May 28, 14:20 UTC | May 28, 14:45 UTC | 25m |
| 2026-05-28 | ZSSHP | - | May 28, 10:40 UTC | May 28, 11:05 UTC | 25m |
| 2026-05-13 | ZSSHP | - | May 13, 10:50 UTC | May 13, 11:15 UTC | 25m |
| 2026-05-11 | ZSSHP | - | May 11, 07:30 UTC | May 11, 08:00 UTC | 30m |
| 2026-05-10 | ZSSHP | - | May 10, 15:55 UTC | May 10, 16:14 UTC | 20m |
| 2026-05-10 | ZSSHP | - | May 10, 13:35 UTC | May 10, 14:00 UTC | 25m |
| 2026-05-06 | ZSSHP | HLA → CPT | May 6, 11:40 UTC | May 6, 15:05 UTC | 3h 25m |
| 2026-05-06 | ZSSHP | - | May 6, 10:01 UTC | May 6, 10:30 UTC | 30m |
| 2026-05-05 | ZSSHP | - | May 5, 05:20 UTC | May 5, 06:00 UTC | 40m |
| 2026-05-04 | ZSSHP | - | May 4, 15:35 UTC | May 4, 16:00 UTC | 25m |
| 2026-05-04 | ZSSHP | - | May 4, 13:00 UTC | May 4, 13:20 UTC | 20m |
| 2026-05-03 | ZSSHP | - | May 3, 06:10 UTC | May 3, 06:45 UTC | 35m |
| 2026-04-30 | ZSSHP | - | Apr 30, 14:30 UTC | Apr 30, 15:00 UTC | 30m |
| 2026-04-28 | ZSSHP | - | Apr 28, 07:50 UTC | Apr 28, 08:05 UTC | 15m |
| 2026-04-27 | ZSSHP | - | Apr 27, 13:00 UTC | Apr 27, 13:10 UTC | 10m |
| 2026-04-27 | ZSSHP | - | Apr 27, 11:30 UTC | Apr 27, 11:40 UTC | 10m |
| 2026-04-25 | ZSSHP | - | Apr 25, 16:55 UTC | Apr 25, 17:20 UTC | 25m |
| 2026-04-25 | ZSSHP | - | Apr 25, 14:05 UTC | Apr 25, 14:45 UTC | 40m |
| 2026-04-25 | ZSSHP | - | Apr 25, 08:40 UTC | Apr 25, 08:55 UTC | 15m |
| 2026-04-25 | ZSSHP | - | Apr 25, 07:15 UTC | Apr 25, 07:40 UTC | 25m |
| 2026-04-24 | ZSSHP | - | Apr 24, 03:15 UTC | Apr 24, 03:50 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.