sensors Mode-S transponder

00B1F2

ICAO 24-bit transponder address · allocated to South Africa

Currently assigned to ZS-SXD · AIRBUS A-340-300

Hex
00B1F2
Octal
00130762
Decimal
45,554
Country
ZA
Tail
ZS-SXD
Type
A343
No current signal · last broadcast Jul 26, 16:35 UTC
Flights observed
107
Distinct callsigns
6
Country
ZA
Last broadcast
Jul 26, 16:35 UTC

Last known position

Most recent position reported by Mode-S 00B1F2.

Country allocation

The ICAO 24-bit address 00B1F2 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 6 distinct

Callsign Airline Flights Last seen
SAA280 South African Airways 51 2026-07-25
SAA281 South African Airways 41 2026-07-26
SAA191 - 9 2026-07-11
SAA190 - 3 2026-07-18
SAA060 South African Airways 2 2026-06-11
SAA061 South African Airways 1 2026-05-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-26 SAA281 PER → JNB Jul 26, 15:55 UTCJul 26, 16:35 UTC40m
2026-07-25 SAA280 JNB → PER Jul 25, 19:05 UTCJul 26, 04:05 UTC9h 0m
2026-07-24 SAA281 PER → JNB Jul 24, 16:00 UTCJul 25, 02:30 UTC10h 30m
2026-07-24 SAA280 JNB → PER Jul 24, 03:35 UTCJul 24, 04:20 UTC45m
2026-07-23 SAA280 JNB → PER Jul 23, 19:30 UTCJul 23, 19:45 UTC15m
2026-07-22 SAA281 PER → JNB Jul 22, 02:15 UTCJul 22, 02:30 UTC15m
2026-07-21 SAA281 PER → JNB Jul 21, 15:45 UTCJul 21, 16:20 UTC35m
2026-07-20 SAA280 - Jul 20, 20:00 UTCJul 21, 04:40 UTC8h 40m
2026-07-19 SAA281 PER → JNB Jul 19, 16:00 UTCJul 20, 03:05 UTC11h 5m
2026-07-18 SAA280 - Jul 18, 19:15 UTCJul 19, 03:55 UTC8h 40m
2026-07-18 SAA190 - Jul 18, 08:00 UTCJul 18, 16:50 UTC8h 50m
2026-07-17 SAA281 - Jul 17, 16:00 UTCJul 18, 03:00 UTC11h 1m
2026-07-16 SAA280 - Jul 16, 19:35 UTCJul 17, 04:10 UTC8h 35m
2026-07-16 SAA190 JNB → JNB Jul 16, 07:55 UTCJul 16, 17:45 UTC9h 50m
2026-07-14 SAA281 - Jul 14, 15:50 UTCJul 15, 02:35 UTC10h 44m
2026-07-13 SAA280 - Jul 13, 19:10 UTCJul 14, 03:40 UTC8h 30m
2026-07-12 SAA281 PER → JNB Jul 12, 16:01 UTCJul 13, 03:05 UTC11h 5m
2026-07-11 SAA280 - Jul 11, 19:15 UTCJul 12, 04:10 UTC8h 55m
2026-07-11 SAA191 - Jul 11, 08:05 UTCJul 11, 16:55 UTC8h 50m
2026-07-10 SAA191 - Jul 10, 07:55 UTCJul 10, 16:55 UTC9h 0m
2026-07-07 SAA281 - Jul 7, 15:55 UTCJul 8, 02:55 UTC11h 0m
2026-07-06 SAA280 JNB → PER Jul 6, 19:10 UTCJul 7, 04:00 UTC8h 50m
2026-07-06 SAA191 - Jul 6, 08:10 UTCJul 6, 17:05 UTC8h 55m
2026-07-05 SAA281 - Jul 5, 15:50 UTCJul 6, 02:50 UTC11h 0m
2026-07-05 SAA280 JNB → PER Jul 5, 02:50 UTCJul 5, 03:25 UTC35m
2026-07-04 SAA280 JNB → PER Jul 4, 19:05 UTCJul 4, 19:20 UTC15m
2026-07-04 SAA191 - Jul 4, 08:05 UTCJul 4, 17:05 UTC9h 0m
2026-07-03 SAA191 JNB → JNB Jul 3, 10:30 UTCJul 3, 19:30 UTC9h 0m
2026-06-30 SAA281 - Jun 30, 15:55 UTCJul 1, 02:15 UTC10h 20m
2026-06-30 SAA280 JNB → PER Jun 30, 03:30 UTCJun 30, 04:10 UTC40m
2026-06-29 SAA280 JNB → PER Jun 29, 19:15 UTCJun 29, 19:29 UTC15m
2026-06-28 SAA281 PER → JNB Jun 28, 16:00 UTCJun 29, 02:39 UTC10h 40m
2026-06-27 SAA280 JNB → PER Jun 27, 20:49 UTCJun 28, 05:20 UTC8h 30m
2026-06-27 SAA191 - Jun 27, 07:55 UTCJun 27, 16:49 UTC8h 55m
2026-06-26 SAA281 - Jun 26, 15:54 UTCJun 27, 02:45 UTC10h 50m
2026-06-25 SAA280 JNB → PER Jun 25, 19:20 UTCJun 26, 04:00 UTC8h 40m
2026-06-23 SAA281 PER → JNB Jun 23, 15:50 UTCJun 24, 02:24 UTC10h 35m
2026-06-22 SAA280 JNB → PER Jun 22, 19:00 UTCJun 23, 03:45 UTC8h 45m
2026-06-22 SAA191 - Jun 22, 08:00 UTCJun 22, 17:00 UTC9h 0m
2026-06-21 SAA281 - Jun 21, 15:59 UTCJun 22, 02:34 UTC10h 35m
2026-06-18 SAA280 JNB → PER Jun 18, 19:05 UTCJun 19, 03:49 UTC8h 44m
2026-06-14 SAA281 - Jun 14, 16:05 UTCJun 15, 03:19 UTC11h 15m
2026-06-14 SAA280 JNB → PER Jun 14, 03:20 UTCJun 14, 03:55 UTC35m
2026-06-13 SAA280 JNB → PER Jun 13, 19:05 UTCJun 13, 19:25 UTC20m
2026-06-11 SAA060 JNB → LOS Jun 11, 13:25 UTCJun 12, 02:30 UTC13h 6m
2026-06-07 SAA281 PER → JNB Jun 7, 16:00 UTCJun 8, 02:50 UTC10h 50m
2026-06-06 SAA280 JNB → PER Jun 6, 19:10 UTCJun 7, 04:10 UTC9h 0m
2026-06-05 SAA281 PER → JNB Jun 5, 15:55 UTCJun 6, 02:35 UTC10h 40m
2026-06-04 SAA280 JNB → PER Jun 4, 19:20 UTCJun 5, 04:15 UTC8h 55m
2026-06-03 SAA281 PER → JNB Jun 3, 15:50 UTCJun 4, 02:30 UTC10h 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-SXD page for operator, model, and routing details .

Mode-S 00B1F2 frequently asked

What is Mode-S code 00B1F2?
00B1F2 is an ICAO 24-bit transponder address. Allocated to South Africa. Assigned to ZS-SXD.
Where is Mode-S 00B1F2 registered?
Mode-S code 00B1F2 is allocated to South Africa (ZA). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 00B1F2 broadcasting right now?
No active broadcast right now. Last signal was Jul 26, 16:35 UTC.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 00B1F2, octal 00130762, decimal 45,554.
What flights does 00B1F2 operate?
Mode-S 00B1F2 has broadcast 6 distinct callsigns, including SAA280, SAA281, SAA191, SAA190, SAA060.