Apparatus

Try JFK, AAL1290, BAW, or N225AN.

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 1d ago
Flights observed
54
Distinct callsigns
6
Country
ZA
Last broadcast
1d ago

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 28 2026-05-25
SAA281 South African Airways 21 2026-05-26
SAA191 South African Airways 2 2026-04-20
SAA190 - 1 2026-04-13
SAA061 South African Airways 1 2026-05-14
SAA060 South African Airways 1 2026-05-28

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-28 SAA060 JNB → LOS May 28, 13:35 UTCMay 29, 02:35 UTC13h 0m
2026-05-26 SAA281 PER → JNB May 26, 15:49 UTCMay 27, 02:44 UTC10h 55m
2026-05-25 SAA280 JNB → PER May 25, 19:05 UTCMay 26, 04:20 UTC9h 15m
2026-05-24 SAA281 PER → JNB May 24, 15:45 UTCMay 25, 02:45 UTC11h 0m
2026-05-23 SAA280 JNB → PER May 23, 19:20 UTCMay 24, 03:50 UTC8h 30m
2026-05-22 SAA281 PER → JNB May 22, 15:50 UTCMay 23, 03:35 UTC11h 45m
2026-05-22 SAA280 JNB → PER May 22, 03:30 UTCMay 22, 04:10 UTC40m
2026-05-21 SAA280 JNB → PER May 21, 19:15 UTCMay 21, 19:30 UTC15m
2026-05-19 SAA281 PER → JNB May 19, 15:45 UTCMay 20, 02:45 UTC11h 0m
2026-05-18 SAA280 JNB → PER May 18, 19:10 UTCMay 19, 04:10 UTC9h 0m
2026-05-17 SAA281 PER → JNB May 17, 15:50 UTCMay 18, 02:35 UTC10h 45m
2026-05-16 SAA280 JNB → PER May 16, 19:10 UTCMay 17, 04:10 UTC9h 0m
2026-05-14 SAA061 LOS → JNB May 14, 13:20 UTCMay 15, 02:20 UTC13h 0m
2026-05-12 SAA281 PER → JNB May 12, 15:35 UTCMay 13, 02:15 UTC10h 40m
2026-05-11 SAA280 JNB → PER May 11, 20:50 UTCMay 12, 05:40 UTC8h 50m
2026-05-10 SAA281 PER → JNB May 10, 16:40 UTCMay 11, 04:10 UTC11h 30m
2026-05-10 SAA280 JNB → PER May 10, 03:30 UTCMay 10, 04:04 UTC35m
2026-05-09 SAA280 JNB → PER May 9, 19:35 UTCMay 9, 19:49 UTC15m
2026-05-08 SAA281 PER → JNB May 8, 15:50 UTCMay 9, 03:10 UTC11h 20m
2026-05-07 SAA280 JNB → PER May 7, 19:10 UTCMay 8, 04:04 UTC8h 55m
2026-05-05 SAA281 PER → JNB May 5, 15:50 UTCMay 6, 02:15 UTC10h 25m
2026-05-04 SAA280 JNB → PER May 4, 19:05 UTCMay 5, 04:25 UTC9h 20m
2026-05-03 SAA281 PER → JNB May 3, 15:55 UTCMay 4, 02:25 UTC10h 30m
2026-05-03 SAA280 JNB → PER May 3, 03:50 UTCMay 3, 04:30 UTC40m
2026-05-02 SAA280 JNB → PER May 2, 19:10 UTCMay 2, 19:30 UTC20m
2026-05-01 SAA281 PER → JNB May 1, 16:10 UTCMay 2, 02:35 UTC10h 26m
2026-05-01 SAA280 JNB → PER May 1, 03:55 UTCMay 1, 04:30 UTC35m
2026-04-30 SAA280 JNB → PER Apr 30, 19:10 UTCApr 30, 19:30 UTC20m
2026-04-28 SAA281 PER → JNB Apr 28, 16:15 UTCApr 29, 03:30 UTC11h 15m
2026-04-28 SAA280 JNB → PER Apr 28, 03:30 UTCApr 28, 04:10 UTC40m
2026-04-27 SAA280 JNB → PER Apr 27, 19:20 UTCApr 27, 19:35 UTC15m
2026-04-26 SAA281 PER → JNB Apr 26, 16:00 UTCApr 27, 02:50 UTC10h 50m
2026-04-26 SAA280 JNB → PER Apr 26, 03:45 UTCApr 26, 04:20 UTC35m
2026-04-25 SAA280 JNB → PER Apr 25, 19:25 UTCApr 25, 19:45 UTC20m
2026-04-24 SAA281 PER → JNB Apr 24, 16:05 UTCApr 25, 02:35 UTC10h 30m
2026-04-24 SAA280 JNB → PER Apr 24, 04:05 UTCApr 24, 04:40 UTC35m
2026-04-23 SAA280 JNB → PER Apr 23, 19:25 UTCApr 23, 19:45 UTC20m
2026-04-21 SAA281 PER → JNB Apr 21, 16:01 UTCApr 22, 02:35 UTC10h 35m
2026-04-21 SAA280 JNB → PER Apr 21, 03:40 UTCApr 21, 04:20 UTC40m
2026-04-20 SAA280 JNB → PER Apr 20, 19:15 UTCApr 20, 19:30 UTC15m
2026-04-20 SAA191 MRU → JNB Apr 20, 08:20 UTCApr 20, 16:55 UTC8h 35m
2026-04-19 SAA281 PER → JNB Apr 19, 15:50 UTCApr 20, 02:35 UTC10h 45m
2026-04-19 SAA280 JNB → PER Apr 19, 03:35 UTCApr 19, 04:15 UTC40m
2026-04-18 SAA280 JNB → PER Apr 18, 19:10 UTCApr 18, 19:30 UTC20m
2026-04-18 SAA281 PER → JNB Apr 18, 02:25 UTCApr 18, 02:50 UTC25m
2026-04-17 SAA281 PER → JNB Apr 17, 16:25 UTCApr 17, 17:05 UTC40m
2026-04-17 SAA280 JNB → PER Apr 17, 03:50 UTCApr 17, 04:25 UTC35m
2026-04-16 SAA280 JNB → PER Apr 16, 19:15 UTCApr 16, 19:30 UTC15m
2026-04-15 SAA281 PER → JNB Apr 15, 02:05 UTCApr 15, 02:30 UTC25m
2026-04-14 SAA281 PER → JNB Apr 14, 16:10 UTCApr 14, 16:40 UTC30m

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 1d ago.
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, SAA061.