sensors Mode-S transponder
00A2E4
ICAO 24-bit transponder address · allocated to South Africa
Currently assigned to ZS-NEX · BOEING 767-300
- Hex
- 00A2E4
- Octal
- 00121344
- Decimal
- 41,700
- Country
- ZA
- Tail
- ZS-NEX
- Type
- B763
- Flights observed
- 49
- Distinct callsigns
- 2
- Country
- ZA
- Last broadcast
- 3d ago
Last known position
Country allocation
The ICAO 24-bit address 00A2E4 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 2 distinct
Recent flights last 49
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | ARN767 | - | Jul 26, 09:10 UTC | Jul 26, 12:10 UTC | 3h 0m |
| 2026-07-26 | ARN767 | - | Jul 26, 05:15 UTC | Jul 26, 05:40 UTC | 25m |
| 2026-07-26 | ARN767 | - | Jul 26, 03:00 UTC | Jul 26, 03:25 UTC | 25m |
| 2026-07-23 | ARN767 | - | Jul 23, 11:05 UTC | Jul 24, 05:15 UTC | 18h 10m |
| 2026-07-23 | ARN767 | - | Jul 23, 09:05 UTC | Jul 24, 05:15 UTC | 20h 10m |
| 2026-07-23 | ARN767 | - | Jul 23, 08:20 UTC | Jul 24, 05:15 UTC | 20h 55m |
| 2026-07-20 | 767 | - | Jul 20, 12:05 UTC | Jul 20, 12:35 UTC | 30m |
| 2026-07-19 | ARN767 | - | Jul 19, 02:50 UTC | Jul 19, 11:05 UTC | 8h 15m |
| 2026-07-17 | ARN767 | - | Jul 17, 20:55 UTC | Jul 17, 23:45 UTC | 2h 50m |
| 2026-07-16 | ARN767 | - | Jul 16, 00:40 UTC | Jul 16, 02:05 UTC | 1h 25m |
| 2026-07-14 | ARN767 | - | Jul 14, 19:45 UTC | Jul 14, 21:30 UTC | 1h 45m |
| 2026-07-12 | ARN767 | - | Jul 12, 03:01 UTC | Jul 12, 05:35 UTC | 2h 35m |
| 2026-07-10 | ARN767 | - | Jul 10, 15:45 UTC | Jul 10, 18:25 UTC | 2h 40m |
| 2026-07-06 | ARN767 | - | Jul 6, 08:25 UTC | Jul 6, 11:25 UTC | 3h 0m |
| 2026-07-03 | ARN767 | - | Jul 3, 20:45 UTC | Jul 3, 23:40 UTC | 2h 55m |
| 2026-06-30 | ARN767 | - | Jun 30, 08:05 UTC | Jun 30, 16:55 UTC | 8h 50m |
| 2026-06-29 | ARN767 | - | Jun 29, 00:29 UTC | Jun 29, 11:04 UTC | 10h 35m |
| 2026-06-28 | ARN767 | - | Jun 28, 13:10 UTC | Jun 29, 11:04 UTC | 21h 55m |
| 2026-06-28 | ARN767 | SYD → STN | Jun 28, 11:55 UTC | Jun 29, 10:59 UTC | 23h 5m |
| 2026-06-22 | ARN767 | - | Jun 22, 18:30 UTC | Jun 22, 20:14 UTC | 1h 45m |
| 2026-06-21 | ARN767 | - | Jun 21, 20:45 UTC | Jun 22, 07:34 UTC | 10h 50m |
| 2026-06-18 | ARN767 | - | Jun 18, 09:55 UTC | Jun 18, 17:10 UTC | 7h 15m |
| 2026-06-17 | ARN767 | - | Jun 17, 18:00 UTC | Jun 18, 17:00 UTC | 23h 0m |
| 2026-06-17 | ARN767 | - | Jun 17, 15:05 UTC | Jun 18, 15:00 UTC | 23h 55m |
| 2026-06-17 | ARN767 | - | Jun 17, 13:05 UTC | Jun 18, 12:45 UTC | 23h 40m |
| 2026-06-17 | ARN767 | - | Jun 17, 12:15 UTC | Jun 18, 10:10 UTC | 21h 55m |
| 2026-06-17 | ARN767 | TRN → LYS | Jun 17, 08:45 UTC | Jun 17, 09:15 UTC | 30m |
| 2026-06-13 | ARN767 | LYS → TRN | Jun 13, 16:10 UTC | Jun 13, 16:45 UTC | 35m |
| 2026-06-13 | ARN767 | - | Jun 13, 09:15 UTC | Jun 13, 13:30 UTC | 4h 15m |
| 2026-06-11 | ARN767 | - | Jun 11, 17:40 UTC | Jun 12, 01:05 UTC | 7h 25m |
| 2026-06-07 | ARN767 | - | Jun 7, 23:20 UTC | Jun 8, 05:05 UTC | 5h 45m |
| 2026-06-06 | ARN767 | - | Jun 6, 11:19 UTC | Jun 6, 19:34 UTC | 8h 15m |
| 2026-06-06 | ARN767 | - | Jun 6, 06:35 UTC | Jun 6, 07:35 UTC | 1h 0m |
| 2026-06-03 | ARN767 | EWR → CWL | Jun 3, 11:20 UTC | Jun 3, 17:55 UTC | 6h 35m |
| 2026-06-02 | ARN767 | - | Jun 2, 02:05 UTC | Jun 2, 11:45 UTC | 9h 40m |
| 2026-05-30 | ARN767 | - | May 30, 20:20 UTC | May 31, 00:00 UTC | 3h 40m |
| 2026-05-29 | ARN767 | - | May 29, 10:30 UTC | May 29, 14:40 UTC | 4h 10m |
| 2026-05-27 | ARN767 | - | May 27, 03:14 UTC | May 27, 07:55 UTC | 4h 40m |
| 2026-05-21 | - | - | May 21, 05:40 UTC | May 21, 05:50 UTC | 10m |
| 2026-05-16 | ARN767 | - | May 16, 14:51 UTC | May 16, 15:05 UTC | 15m |
| 2026-05-16 | ARN767 | - | May 16, 06:31 UTC | May 16, 12:05 UTC | 5h 35m |
| 2026-05-13 | ARN767 | - | May 13, 09:10 UTC | May 13, 13:00 UTC | 3h 50m |
| 2026-05-01 | ARN767 | - | May 1, 11:30 UTC | May 2, 05:10 UTC | 17h 40m |
| 2026-05-01 | ARN767 | - | May 1, 05:05 UTC | May 2, 05:00 UTC | 23h 55m |
| 2026-05-01 | ARN767 | - | May 1, 04:50 UTC | May 2, 00:45 UTC | 19h 55m |
| 2026-04-30 | ARN767 | - | Apr 30, 06:55 UTC | Apr 30, 08:50 UTC | 1h 55m |
| 2026-04-29 | ARN767 | - | Apr 29, 10:40 UTC | Apr 29, 21:05 UTC | 10h 25m |
| 2026-04-20 | ARN767 | NCE → STN | Apr 20, 08:40 UTC | Apr 20, 10:25 UTC | 1h 45m |
| 2026-04-18 | ARN767 | SJC → NCE | Apr 18, 22:30 UTC | Apr 19, 10:10 UTC | 11h 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-NEX page for operator, model, and routing details .