sensors Mode-S transponder
00B1FB
ICAO 24-bit transponder address · allocated to South Africa
Currently assigned to ZS-SXM · AIRBUS A-330-300
- Hex
- 00B1FB
- Octal
- 00130773
- Decimal
- 45,563
- Country
- ZA
- Tail
- ZS-SXM
- Type
- A333
- Flights observed
- 69
- Distinct callsigns
- 13
- Country
- ZA
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 00B1FB 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 13 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| SAA056 | South African Airways | 12 | 2026-05-26 |
| SAA057 | South African Airways | 11 | 2026-05-16 |
| SAA060 | South African Airways | 10 | 2026-05-29 |
| SAA061 | South African Airways | 6 | 2026-05-22 |
| SAA053 | South African Airways | 6 | 2026-05-17 |
| SAA052 | South African Airways | 6 | 2026-05-27 |
| SAA227 | South African Airways | 4 | 2026-05-20 |
| SAA317 | South African Airways | 3 | 2026-05-19 |
| SAA314 | South African Airways | 3 | 2026-05-20 |
| SAA226 | South African Airways | 3 | 2026-05-19 |
| SAA223 | South African Airways | 2 | 2026-05-28 |
| SAA222 | South African Airways | 2 | 2026-05-28 |
| SAA190 | South African Airways | 1 | 2026-04-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | SAA060 | JNB → LOS | May 29, 13:20 UTC | May 29, 23:35 UTC | 10h 15m |
| 2026-05-28 | SAA223 | GRU → JNB | May 28, 20:30 UTC | May 29, 04:20 UTC | 7h 50m |
| 2026-05-28 | SAA222 | JNB → GRU | May 28, 08:10 UTC | May 28, 18:50 UTC | 10h 40m |
| 2026-05-27 | SAA052 | JNB → ACC | May 27, 13:15 UTC | May 28, 02:10 UTC | 12h 55m |
| 2026-05-26 | SAA056 | JNB → ACC | May 26, 09:15 UTC | May 27, 03:20 UTC | 18h 5m |
| 2026-05-24 | SAA060 | JNB → LOS | May 24, 13:35 UTC | May 25, 02:50 UTC | 13h 15m |
| 2026-05-23 | SAA056 | JNB → ACC | May 23, 10:20 UTC | May 24, 03:00 UTC | 16h 41m |
| 2026-05-22 | SAA061 | LOS → JNB | May 22, 13:30 UTC | May 23, 02:30 UTC | 13h 0m |
| 2026-05-21 | SAA223 | GRU → JNB | May 21, 20:45 UTC | May 22, 04:50 UTC | 8h 5m |
| 2026-05-21 | SAA222 | JNB → GRU | May 21, 08:00 UTC | May 21, 18:00 UTC | 10h 0m |
| 2026-05-20 | SAA052 | JNB → ACC | May 20, 13:05 UTC | May 21, 01:50 UTC | 12h 45m |
| 2026-05-20 | SAA314 | CPT → JNB | May 20, 09:05 UTC | May 20, 09:20 UTC | 15m |
| 2026-05-20 | SAA314 | CPT → JNB | May 20, 07:45 UTC | May 20, 08:10 UTC | 25m |
| 2026-05-20 | SAA227 | GRU → CPT | May 20, 04:20 UTC | May 20, 04:35 UTC | 15m |
| 2026-05-19 | SAA227 | GRU → CPT | May 19, 21:40 UTC | May 19, 22:30 UTC | 50m |
| 2026-05-19 | SAA226 | CPT → GRU | May 19, 18:25 UTC | May 19, 19:50 UTC | 1h 25m |
| 2026-05-19 | SAA226 | CPT → GRU | May 19, 10:55 UTC | May 19, 11:05 UTC | 10m |
| 2026-05-19 | SAA317 | JNB → CPT | May 19, 07:15 UTC | May 19, 09:15 UTC | 2h 0m |
| 2026-05-17 | SAA053 | ACC → JNB | May 17, 15:45 UTC | May 18, 04:30 UTC | 12h 45m |
| 2026-05-16 | SAA057 | ACC → JNB | May 16, 09:10 UTC | May 17, 01:40 UTC | 16h 30m |
| 2026-05-15 | SAA060 | JNB → LOS | May 15, 13:20 UTC | May 16, 02:20 UTC | 12h 59m |
| 2026-05-14 | SAA057 | ACC → JNB | May 14, 09:15 UTC | May 15, 01:55 UTC | 16h 40m |
| 2026-05-13 | SAA053 | ACC → JNB | May 13, 12:55 UTC | May 14, 02:00 UTC | 13h 5m |
| 2026-05-13 | SAA314 | CPT → JNB | May 13, 06:20 UTC | May 13, 08:00 UTC | 1h 40m |
| 2026-05-13 | SAA227 | GRU → CPT | May 13, 04:30 UTC | May 13, 04:45 UTC | 15m |
| 2026-05-12 | SAA227 | GRU → CPT | May 12, 22:01 UTC | May 12, 22:50 UTC | 50m |
| 2026-05-12 | SAA226 | CPT → GRU | May 12, 11:00 UTC | May 12, 19:50 UTC | 8h 50m |
| 2026-05-12 | SAA317 | JNB → CPT | May 12, 08:30 UTC | May 12, 09:00 UTC | 30m |
| 2026-05-12 | SAA317 | JNB → CPT | May 12, 07:05 UTC | May 12, 07:20 UTC | 15m |
| 2026-05-10 | SAA060 | JNB → LOS | May 10, 13:30 UTC | May 11, 02:55 UTC | 13h 25m |
| 2026-05-09 | SAA056 | JNB → ACC | May 9, 09:10 UTC | May 10, 01:50 UTC | 16h 40m |
| 2026-05-08 | SAA060 | JNB → LOS | May 8, 13:30 UTC | May 9, 02:25 UTC | 12h 55m |
| 2026-05-07 | SAA056 | JNB → ACC | May 7, 09:15 UTC | May 8, 01:55 UTC | 16h 40m |
| 2026-05-06 | SAA053 | ACC → JNB | May 6, 13:05 UTC | May 7, 02:10 UTC | 13h 4m |
| 2026-05-05 | SAA057 | ACC → JNB | May 5, 23:25 UTC | May 6, 02:05 UTC | 2h 40m |
| 2026-05-05 | SAA056 | JNB → ACC | May 5, 09:20 UTC | May 5, 23:20 UTC | 14h 0m |
| 2026-05-03 | SAA061 | LOS → JNB | May 3, 13:35 UTC | May 4, 03:40 UTC | 14h 5m |
| 2026-05-02 | SAA056 | JNB → ACC | May 2, 09:05 UTC | May 3, 02:20 UTC | 17h 15m |
| 2026-05-01 | SAA061 | LOS → JNB | May 1, 13:25 UTC | May 2, 02:35 UTC | 13h 10m |
| 2026-04-30 | SAA057 | ACC → JNB | Apr 30, 09:10 UTC | May 1, 01:40 UTC | 16h 30m |
| 2026-04-29 | SAA052 | JNB → ACC | Apr 29, 13:05 UTC | Apr 30, 02:05 UTC | 12h 59m |
| 2026-04-28 | SAA057 | ACC → JNB | Apr 28, 09:15 UTC | Apr 29, 01:59 UTC | 16h 45m |
| 2026-04-27 | SAA190 | JNB → MRU | Apr 27, 10:50 UTC | Apr 27, 19:40 UTC | 8h 50m |
| 2026-04-26 | SAA060 | JNB → LOS | Apr 26, 13:30 UTC | Apr 27, 02:55 UTC | 13h 25m |
| 2026-04-25 | SAA057 | ACC → JNB | Apr 25, 09:15 UTC | Apr 26, 02:30 UTC | 17h 15m |
| 2026-04-24 | SAA060 | JNB → LOS | Apr 24, 13:30 UTC | Apr 25, 02:40 UTC | 13h 10m |
| 2026-04-23 | SAA056 | JNB → ACC | Apr 23, 09:15 UTC | Apr 24, 02:30 UTC | 17h 15m |
| 2026-04-22 | SAA053 | ACC → JNB | Apr 22, 13:20 UTC | Apr 23, 02:05 UTC | 12h 45m |
| 2026-04-21 | SAA057 | ACC → JNB | Apr 21, 09:10 UTC | Apr 22, 01:50 UTC | 16h 40m |
| 2026-04-19 | SAA052 | JNB → ACC | Apr 19, 13:10 UTC | Apr 20, 01:50 UTC | 12h 40m |
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 ZS-SXM page for operator, model, and routing details .