sensors Mode-S transponder
04021E
ICAO 24-bit transponder address · allocated to Ethiopia
Currently assigned to ET-AZO · BOEING 737 MAX 8
- Hex
- 04021E
- Octal
- 01001036
- Decimal
- 262,686
- Country
- ET
- Tail
- ET-AZO
- Type
- B38M
- Flights observed
- 69
- Distinct callsigns
- 20
- Country
- ET
- Last broadcast
- 3h ago
Current position
Country allocation
The ICAO 24-bit address 04021E falls within the block assigned to Ethiopia (ET) by ICAO Annex 10, Volume III. Every aircraft registered in Ethiopia 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| ETH682 | - | 8 | 2026-07-06 |
| ETH406 | - | 6 | 2026-07-04 |
| ETH407 | - | 4 | 2026-07-05 |
| ETH849 | - | 3 | 2026-06-19 |
| ETH721 | Ethiopian Airlines | 3 | 2026-04-20 |
| ETH683 | Ethiopian Airlines | 3 | 2026-06-22 |
| ETH622 | - | 3 | 2026-07-12 |
| ETH414 | - | 3 | 2026-07-14 |
| ETH859 | Ethiopian Airlines | 2 | 2026-05-15 |
| ETH858 | Ethiopian Airlines | 2 | 2026-06-19 |
| ETH690 | Ethiopian Airlines | 2 | 2026-06-01 |
| ETH688 | Ethiopian Airlines | 2 | 2026-05-08 |
| ETH623 | - | 2 | 2026-07-13 |
| ETH415 | - | 2 | 2026-07-09 |
| ETH405 | - | 2 | 2026-07-03 |
| ETH404 | - | 2 | 2026-07-08 |
| ETH308 | Ethiopian Airlines | 2 | 2026-04-28 |
| ETH953 | Ethiopian Airlines | 1 | 2026-05-11 |
| ETH952 | Ethiopian Airlines | 1 | 2026-05-11 |
| ETH949 | - | 1 | 2026-07-02 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | ETH414 | - | Jul 14, 19:15 UTC | Jul 14, 19:45 UTC | 30m |
| 2026-07-13 | ETH623 | - | Jul 13, 01:05 UTC | Jul 13, 01:40 UTC | 35m |
| 2026-07-12 | ETH622 | - | Jul 12, 23:05 UTC | Jul 12, 23:45 UTC | 40m |
| 2026-07-11 | - | - | Jul 11, 00:20 UTC | Jul 11, 00:30 UTC | 10m |
| 2026-07-09 | ETH415 | - | Jul 9, 05:10 UTC | Jul 9, 05:40 UTC | 30m |
| 2026-07-08 | ETH404 | TLV → TLV | Jul 8, 13:00 UTC | Jul 9, 02:55 UTC | 13h 55m |
| 2026-07-08 | ETH417 | - | Jul 8, 01:10 UTC | Jul 8, 11:20 UTC | 10h 10m |
| 2026-07-07 | ETH416 | - | Jul 7, 22:55 UTC | Jul 7, 23:50 UTC | 55m |
| 2026-07-06 | ETH682 | - | Jul 6, 08:00 UTC | Jul 6, 23:30 UTC | 15h 30m |
| 2026-07-05 | ETH407 | - | Jul 5, 00:05 UTC | Jul 5, 01:05 UTC | 1h 0m |
| 2026-07-04 | ETH406 | - | Jul 4, 21:40 UTC | Jul 4, 22:35 UTC | 55m |
| 2026-07-03 | ETH405 | - | Jul 3, 22:25 UTC | Jul 3, 22:55 UTC | 30m |
| 2026-07-03 | ETH414 | - | Jul 3, 19:55 UTC | Jul 3, 20:35 UTC | 40m |
| 2026-07-03 | ETH948 | - | Jul 3, 01:20 UTC | Jul 3, 01:35 UTC | 15m |
| 2026-07-02 | ETH949 | - | Jul 2, 23:40 UTC | Jul 3, 00:00 UTC | 20m |
| 2026-07-02 | ETH407 | - | Jul 2, 00:25 UTC | Jul 2, 01:30 UTC | 1h 5m |
| 2026-07-01 | ETH406 | - | Jul 1, 22:00 UTC | Jul 1, 23:05 UTC | 1h 5m |
| 2026-06-28 | ETH405 | TLV → ADD | Jun 28, 22:34 UTC | Jun 28, 22:59 UTC | 25m |
| 2026-06-28 | ETH414 | ADD → TLV | Jun 28, 19:20 UTC | Jun 28, 19:49 UTC | 30m |
| 2026-06-26 | ETH682 | - | Jun 26, 18:24 UTC | Jun 27, 00:25 UTC | 6h 0m |
| 2026-06-26 | ETH682 | - | Jun 26, 01:34 UTC | Jun 27, 00:25 UTC | 22h 50m |
| 2026-06-26 | ETH682 | - | Jun 26, 01:10 UTC | Jun 26, 19:09 UTC | 18h 0m |
| 2026-06-25 | ETH614 | - | Jun 25, 22:34 UTC | Jun 25, 23:05 UTC | 30m |
| 2026-06-22 | ETH683 | HYD → ADD | Jun 22, 22:49 UTC | Jun 23, 16:54 UTC | 18h 5m |
| 2026-06-22 | ETH683 | HYD → ADD | Jun 22, 18:30 UTC | Jun 23, 16:54 UTC | 22h 25m |
| 2026-06-22 | ETH683 | HYD → ADD | Jun 22, 07:45 UTC | Jun 22, 23:35 UTC | 15h 50m |
| 2026-06-19 | ETH858 | JNB → ADD | Jun 19, 21:14 UTC | Jun 19, 21:39 UTC | 25m |
| 2026-06-19 | ETH849 | - | Jun 19, 04:44 UTC | Jun 19, 18:05 UTC | 13h 20m |
| 2026-06-19 | ETH686 | - | Jun 19, 02:14 UTC | Jun 19, 02:54 UTC | 40m |
| 2026-06-18 | ETH407 | BEY → ADD | Jun 18, 00:30 UTC | Jun 18, 01:35 UTC | 1h 5m |
| 2026-06-17 | ETH406 | ADD → BEY | Jun 17, 22:20 UTC | Jun 17, 23:10 UTC | 50m |
| 2026-06-17 | ETH406 | ADD → BEY | Jun 17, 01:35 UTC | Jun 17, 23:10 UTC | 21h 35m |
| 2026-06-17 | ETH406 | ADD → BEY | Jun 17, 01:15 UTC | Jun 17, 23:10 UTC | 21h 55m |
| 2026-06-16 | ETH622 | - | Jun 16, 23:20 UTC | Jun 16, 23:55 UTC | 35m |
| 2026-06-15 | ETH623 | SHJ → SHJ | Jun 15, 00:45 UTC | Jun 15, 01:04 UTC | 20m |
| 2026-06-10 | ETH682 | ADD → HYD | Jun 10, 18:10 UTC | Jun 10, 23:05 UTC | 4h 55m |
| 2026-06-09 | ETH415 | TLV → ADD | Jun 9, 04:40 UTC | Jun 9, 05:05 UTC | 25m |
| 2026-06-09 | ETH404 | ADD → TLV | Jun 9, 02:10 UTC | Jun 9, 02:55 UTC | 45m |
| 2026-06-05 | ETH407 | BEY → ADD | Jun 5, 00:35 UTC | Jun 5, 01:35 UTC | 1h 0m |
| 2026-06-04 | ETH406 | ADD → BEY | Jun 4, 22:20 UTC | Jun 4, 23:10 UTC | 50m |
| 2026-06-01 | ETH622 | ADD → SHJ | Jun 1, 10:45 UTC | Jun 1, 23:20 UTC | 12h 35m |
| 2026-06-01 | ETH690 | ADD → BLR | Jun 1, 01:55 UTC | Jun 1, 02:20 UTC | 25m |
| 2026-05-27 | ETH691 | BLR → ADD | May 27, 10:40 UTC | May 27, 10:55 UTC | 15m |
| 2026-05-27 | ETH690 | ADD → BLR | May 27, 01:44 UTC | May 27, 02:09 UTC | 25m |
| 2026-05-21 | ETH917 | ADD → COO | May 21, 09:55 UTC | May 21, 10:05 UTC | 10m |
| 2026-05-19 | ETH858 | JNB → ADD | May 19, 21:25 UTC | May 19, 21:55 UTC | 30m |
| 2026-05-19 | ETH849 | ADD → JNB | May 19, 17:25 UTC | May 19, 18:00 UTC | 35m |
| 2026-05-18 | ETH849 | ADD → JNB | May 18, 21:35 UTC | May 19, 18:00 UTC | 20h 25m |
| 2026-05-18 | ETH682 | ADD → HYD | May 18, 17:55 UTC | May 19, 17:30 UTC | 23h 34m |
| 2026-05-18 | ETH682 | ADD → HYD | May 18, 08:15 UTC | May 18, 22:10 UTC | 13h 54m |
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 ET-AZO page for operator, model, and routing details .