sensors Mode-S transponder
0800A0
ICAO 24-bit transponder address · allocated to Tanzania
Currently assigned to 5H-TCQ · BOEING 737 MAX 9
- Hex
- 0800A0
- Octal
- 02000240
- Decimal
- 524,448
- Country
- TZ
- Tail
- 5H-TCQ
- Type
- B39M
- Flights observed
- 76
- Distinct callsigns
- 5
- Country
- TZ
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address 0800A0 falls within the block assigned to Tanzania (TZ) by ICAO Annex 10, Volume III. Every aircraft registered in Tanzania 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 5 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ATC400 | - | 36 | 2026-07-13 |
| ATC217 | Air Tanzania | 15 | 2026-05-24 |
| ATC235 | - | 12 | 2026-07-08 |
| ATC401 | - | 11 | 2026-07-14 |
| ATC208 | Air Tanzania | 2 | 2026-06-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ATC401 | - | Jul 14, 01:05 UTC | Jul 14, 01:45 UTC | 40m |
| 2026-07-13 | ATC400 | - | Jul 13, 22:55 UTC | Jul 13, 23:50 UTC | 55m |
| 2026-07-13 | ATC400 | - | Jul 13, 01:05 UTC | Jul 13, 23:50 UTC | 22h 45m |
| 2026-07-12 | ATC400 | - | Jul 12, 22:30 UTC | Jul 12, 23:20 UTC | 50m |
| 2026-07-12 | ATC400 | - | Jul 12, 00:40 UTC | Jul 12, 23:20 UTC | 22h 40m |
| 2026-07-11 | ATC400 | - | Jul 11, 22:10 UTC | Jul 11, 23:00 UTC | 50m |
| 2026-07-11 | ATC400 | - | Jul 11, 01:10 UTC | Jul 11, 23:00 UTC | 21h 50m |
| 2026-07-10 | ATC400 | - | Jul 10, 13:20 UTC | Jul 10, 23:40 UTC | 10h 20m |
| 2026-07-10 | ATC401 | - | Jul 10, 01:15 UTC | Jul 10, 12:05 UTC | 10h 50m |
| 2026-07-09 | ATC400 | - | Jul 9, 22:35 UTC | Jul 9, 23:30 UTC | 55m |
| 2026-07-08 | ATC235 | - | Jul 8, 13:05 UTC | Jul 8, 19:45 UTC | 6h 40m |
| 2026-07-07 | ATC401 | - | Jul 7, 01:40 UTC | Jul 7, 02:15 UTC | 35m |
| 2026-07-06 | ATC400 | - | Jul 6, 22:55 UTC | Jul 7, 00:00 UTC | 1h 5m |
| 2026-07-06 | ATC400 | - | Jul 6, 02:05 UTC | Jul 7, 00:00 UTC | 21h 55m |
| 2026-07-06 | ATC400 | - | Jul 6, 01:55 UTC | Jul 7, 00:00 UTC | 22h 5m |
| 2026-07-05 | ATC400 | - | Jul 5, 23:10 UTC | Jul 6, 00:00 UTC | 50m |
| 2026-07-05 | ATC400 | - | Jul 5, 02:05 UTC | Jul 6, 00:00 UTC | 21h 55m |
| 2026-07-05 | ATC400 | - | Jul 5, 01:50 UTC | Jul 6, 00:00 UTC | 22h 10m |
| 2026-07-04 | ATC400 | - | Jul 4, 23:20 UTC | Jul 5, 00:10 UTC | 50m |
| 2026-07-04 | ATC400 | - | Jul 4, 02:05 UTC | Jul 5, 00:10 UTC | 22h 5m |
| 2026-07-03 | ATC400 | - | Jul 3, 13:40 UTC | Jul 4, 00:20 UTC | 10h 40m |
| 2026-07-03 | ATC401 | - | Jul 3, 01:10 UTC | Jul 3, 12:10 UTC | 11h 0m |
| 2026-07-02 | ATC400 | - | Jul 2, 22:20 UTC | Jul 2, 23:15 UTC | 55m |
| 2026-06-30 | ATC401 | - | Jun 30, 01:40 UTC | Jun 30, 02:15 UTC | 35m |
| 2026-06-29 | ATC400 | - | Jun 29, 22:59 UTC | Jun 29, 23:49 UTC | 50m |
| 2026-06-26 | ATC401 | - | Jun 26, 01:24 UTC | Jun 26, 02:00 UTC | 35m |
| 2026-06-25 | ATC400 | - | Jun 25, 22:45 UTC | Jun 25, 23:30 UTC | 45m |
| 2026-06-24 | ATC401 | BOM → DAR | Jun 24, 01:14 UTC | Jun 24, 13:30 UTC | 12h 15m |
| 2026-06-23 | ATC400 | - | Jun 23, 22:29 UTC | Jun 23, 23:24 UTC | 55m |
| 2026-06-23 | ATC400 | - | Jun 23, 01:15 UTC | Jun 23, 23:24 UTC | 22h 10m |
| 2026-06-22 | ATC400 | DAR → BOM | Jun 22, 22:44 UTC | Jun 22, 23:29 UTC | 45m |
| 2026-06-19 | ATC401 | BOM → DAR | Jun 19, 01:19 UTC | Jun 19, 01:54 UTC | 35m |
| 2026-06-18 | ATC400 | DAR → BOM | Jun 18, 22:40 UTC | Jun 18, 23:30 UTC | 50m |
| 2026-06-16 | ATC401 | BOM → DAR | Jun 16, 02:34 UTC | Jun 16, 03:15 UTC | 40m |
| 2026-06-15 | ATC400 | DAR → BOM | Jun 15, 22:54 UTC | Jun 16, 00:00 UTC | 1h 5m |
| 2026-06-12 | ATC235 | DAR → LOS | Jun 12, 02:05 UTC | Jun 12, 20:10 UTC | 18h 5m |
| 2026-06-12 | ATC235 | DAR → LOS | Jun 12, 01:50 UTC | Jun 12, 20:10 UTC | 18h 20m |
| 2026-06-11 | ATC400 | DAR → BOM | Jun 11, 23:00 UTC | Jun 11, 23:50 UTC | 50m |
| 2026-06-11 | ATC400 | DAR → BOM | Jun 11, 02:25 UTC | Jun 11, 23:50 UTC | 21h 25m |
| 2026-06-10 | ATC400 | DAR → BOM | Jun 10, 23:25 UTC | Jun 11, 00:15 UTC | 50m |
| 2026-06-10 | ATC401 | BOM → DAR | Jun 10, 01:05 UTC | Jun 11, 00:00 UTC | 22h 55m |
| 2026-06-09 | ATC400 | DAR → BOM | Jun 9, 22:30 UTC | Jun 9, 23:30 UTC | 1h 0m |
| 2026-06-09 | ATC400 | DAR → BOM | Jun 9, 02:05 UTC | Jun 9, 23:30 UTC | 21h 25m |
| 2026-06-09 | ATC400 | DAR → BOM | Jun 9, 01:30 UTC | Jun 9, 23:30 UTC | 22h 0m |
| 2026-06-08 | ATC400 | DAR → BOM | Jun 8, 23:10 UTC | Jun 9, 00:00 UTC | 50m |
| 2026-06-08 | ATC400 | DAR → BOM | Jun 8, 02:35 UTC | Jun 9, 00:00 UTC | 21h 25m |
| 2026-06-08 | ATC400 | DAR → BOM | Jun 8, 00:15 UTC | Jun 8, 01:10 UTC | 55m |
| 2026-06-06 | ATC401 | BOM → DAR | Jun 6, 01:55 UTC | Jun 6, 02:35 UTC | 40m |
| 2026-06-05 | ATC400 | DAR → BOM | Jun 5, 13:30 UTC | Jun 6, 00:15 UTC | 10h 45m |
| 2026-06-05 | ATC208 | DAR → JNB | Jun 5, 11:45 UTC | Jun 5, 12:15 UTC | 30m |
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 5H-TCQ page for operator, model, and routing details .