sensors Mode-S transponder
08A106
ICAO 24-bit transponder address · allocated to Zambia
Currently assigned to 9J-ZAE
- Hex
- 08A106
- Octal
- 02120406
- Decimal
- 565,510
- Country
- ZM
- Tail
- 9J-ZAE
- Type
- B737
- Flights observed
- 64
- Distinct callsigns
- 4
- Country
- ZM
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 08A106 falls within the block assigned to Zambia (ZM) by ICAO Annex 10, Volume III. Every aircraft registered in Zambia 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 4 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AZB304 | JNB → LUN | May 29, 08:10 UTC | May 29, 08:40 UTC | 30m |
| 2026-05-29 | AZB305 | LUN → JNB | May 29, 06:35 UTC | May 29, 07:05 UTC | 30m |
| 2026-05-27 | AZB304 | JNB → LUN | May 27, 08:05 UTC | May 27, 08:40 UTC | 35m |
| 2026-05-27 | AZB305 | LUN → JNB | May 27, 06:25 UTC | May 27, 06:55 UTC | 30m |
| 2026-05-25 | AZB304 | JNB → LUN | May 25, 08:50 UTC | May 25, 09:20 UTC | 30m |
| 2026-05-25 | AZB305 | LUN → JNB | May 25, 06:30 UTC | May 25, 07:05 UTC | 35m |
| 2026-05-24 | AZB304 | JNB → LUN | May 24, 08:45 UTC | May 24, 09:15 UTC | 30m |
| 2026-05-23 | AZB307 | LUN → JNB | May 23, 17:35 UTC | May 24, 07:10 UTC | 13h 36m |
| 2026-05-23 | AZB307 | LUN → JNB | May 23, 15:40 UTC | May 23, 16:05 UTC | 25m |
| 2026-05-22 | AZB304 | JNB → LUN | May 22, 09:20 UTC | May 22, 09:55 UTC | 35m |
| 2026-05-22 | AZB305 | LUN → JNB | May 22, 07:35 UTC | May 22, 08:05 UTC | 30m |
| 2026-05-20 | AZB304 | JNB → LUN | May 20, 08:10 UTC | May 20, 08:45 UTC | 35m |
| 2026-05-20 | AZB305 | LUN → JNB | May 20, 06:25 UTC | May 20, 06:55 UTC | 30m |
| 2026-05-18 | AZB304 | JNB → LUN | May 18, 08:45 UTC | May 18, 09:15 UTC | 30m |
| 2026-05-18 | AZB305 | LUN → JNB | May 18, 06:40 UTC | May 18, 07:10 UTC | 30m |
| 2026-05-17 | AZB304 | JNB → LUN | May 17, 08:35 UTC | May 18, 07:10 UTC | 22h 35m |
| 2026-05-16 | AZB306 | JNB → LUN | May 16, 17:20 UTC | May 17, 07:05 UTC | 13h 45m |
| 2026-05-16 | AZB307 | LUN → JNB | May 16, 15:35 UTC | May 16, 16:00 UTC | 25m |
| 2026-05-15 | AZB304 | JNB → LUN | May 15, 08:10 UTC | May 15, 08:45 UTC | 35m |
| 2026-05-15 | AZB305 | LUN → JNB | May 15, 06:35 UTC | May 15, 07:05 UTC | 30m |
| 2026-05-13 | AZB304 | JNB → LUN | May 13, 08:30 UTC | May 13, 09:05 UTC | 35m |
| 2026-05-12 | AZB305 | LUN → JNB | May 12, 17:55 UTC | May 13, 07:10 UTC | 13h 15m |
| 2026-05-12 | AZB307 | LUN → JNB | May 12, 15:50 UTC | May 12, 16:30 UTC | 40m |
| 2026-05-11 | AZB304 | JNB → LUN | May 11, 08:25 UTC | May 11, 08:55 UTC | 30m |
| 2026-05-11 | AZB305 | LUN → JNB | May 11, 06:30 UTC | May 11, 07:00 UTC | 30m |
| 2026-05-10 | AZB304 | JNB → LUN | May 10, 08:20 UTC | May 10, 08:54 UTC | 35m |
| 2026-05-09 | AZB306 | JNB → LUN | May 9, 17:20 UTC | May 10, 06:59 UTC | 13h 40m |
| 2026-05-09 | AZB307 | LUN → JNB | May 9, 15:25 UTC | May 9, 15:50 UTC | 25m |
| 2026-05-08 | AZB304 | JNB → LUN | May 8, 08:24 UTC | May 8, 08:59 UTC | 35m |
| 2026-05-08 | AZB305 | LUN → JNB | May 8, 06:39 UTC | May 8, 07:14 UTC | 35m |
| 2026-05-06 | AZB304 | JNB → LUN | May 6, 08:15 UTC | May 6, 08:50 UTC | 35m |
| 2026-05-06 | AZB305 | LUN → JNB | May 6, 06:25 UTC | May 6, 07:05 UTC | 40m |
| 2026-05-04 | AZB304 | JNB → LUN | May 4, 08:20 UTC | May 4, 08:50 UTC | 30m |
| 2026-05-04 | AZB305 | LUN → JNB | May 4, 06:25 UTC | May 4, 06:55 UTC | 30m |
| 2026-05-03 | AZB304 | JNB → LUN | May 3, 08:25 UTC | May 4, 06:55 UTC | 22h 30m |
| 2026-05-02 | AZB306 | JNB → LUN | May 2, 17:30 UTC | May 3, 07:00 UTC | 13h 29m |
| 2026-05-02 | AZB307 | LUN → JNB | May 2, 15:50 UTC | May 2, 16:15 UTC | 25m |
| 2026-05-01 | AZB304 | JNB → LUN | May 1, 08:15 UTC | May 1, 08:50 UTC | 35m |
| 2026-05-01 | AZB305 | LUN → JNB | May 1, 06:25 UTC | May 1, 06:55 UTC | 30m |
| 2026-04-29 | AZB304 | JNB → LUN | Apr 29, 08:25 UTC | Apr 29, 08:55 UTC | 30m |
| 2026-04-29 | AZB305 | LUN → JNB | Apr 29, 06:25 UTC | Apr 29, 06:59 UTC | 35m |
| 2026-04-27 | AZB304 | JNB → LUN | Apr 27, 08:35 UTC | Apr 27, 09:05 UTC | 30m |
| 2026-04-27 | AZB305 | LUN → JNB | Apr 27, 06:30 UTC | Apr 27, 07:00 UTC | 30m |
| 2026-04-26 | AZB304 | JNB → LUN | Apr 26, 08:10 UTC | Apr 26, 08:40 UTC | 30m |
| 2026-04-25 | AZB306 | JNB → LUN | Apr 25, 17:45 UTC | Apr 26, 07:10 UTC | 13h 25m |
| 2026-04-25 | AZB307 | LUN → JNB | Apr 25, 15:40 UTC | Apr 25, 16:10 UTC | 30m |
| 2026-04-24 | AZB304 | JNB → LUN | Apr 24, 08:25 UTC | Apr 24, 08:55 UTC | 30m |
| 2026-04-24 | AZB305 | LUN → JNB | Apr 24, 06:30 UTC | Apr 24, 07:00 UTC | 30m |
| 2026-04-22 | AZB304 | JNB → LUN | Apr 22, 08:20 UTC | Apr 22, 08:55 UTC | 35m |
| 2026-04-21 | AZB306 | JNB → LUN | Apr 21, 18:05 UTC | Apr 22, 07:10 UTC | 13h 5m |
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 9J-ZAE page for operator, model, and routing details .