sensors Mode-S transponder
040232
ICAO 24-bit transponder address · allocated to Ethiopia
Currently assigned to ET-BAJ · BOEING 737 MAX 8
- Hex
- 040232
- Octal
- 01001062
- Decimal
- 262,706
- Country
- ET
- Tail
- ET-BAJ
- Type
- B38M
- Flights observed
- 34
- Distinct callsigns
- 20
- Country
- ET
- Last broadcast
- 14h ago
Last known position
Country allocation
The ICAO 24-bit address 040232 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 |
|---|---|---|---|
| ETH963 | Ethiopian Airlines | 4 | 2026-05-13 |
| ETH962 | Ethiopian Airlines | 2 | 2026-05-02 |
| ETH815 | Ethiopian Airlines | 2 | 2026-04-29 |
| ETH723 | Ethiopian Airlines | 2 | 2026-05-28 |
| ETH720 | Ethiopian Airlines | 2 | 2026-05-27 |
| ETH415 | Ethiopian Airlines | 2 | 2026-06-02 |
| ETH404 | Ethiopian Airlines | 2 | 2026-06-02 |
| ETH953 | Ethiopian Airlines | 1 | 2026-05-18 |
| ETH952 | Ethiopian Airlines | 1 | 2026-05-18 |
| ETH867 | Ethiopian Airlines | 1 | 2026-05-31 |
| ETH765 | Ethiopian Airlines | 1 | 2026-05-09 |
| ETH764 | Ethiopian Airlines | 1 | 2026-05-09 |
| ETH722 | Ethiopian Airlines | 1 | 2026-05-16 |
| ETH721 | Ethiopian Airlines | 1 | 2026-05-16 |
| ETH693 | Ethiopian Airlines | 1 | 2026-05-21 |
| ETH692 | Ethiopian Airlines | 1 | 2026-05-21 |
| ETH691 | Ethiopian Airlines | 1 | 2026-05-08 |
| ETH690 | Ethiopian Airlines | 1 | 2026-05-08 |
| ETH623 | Ethiopian Airlines | 1 | 2026-04-16 |
| ETH622 | Ethiopian Airlines | 1 | 2026-04-15 |
Recent flights last 34
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | ETH415 | TLV → ADD | Jun 2, 05:15 UTC | Jun 2, 05:45 UTC | 30m |
| 2026-06-02 | ETH404 | ADD → TLV | Jun 2, 01:55 UTC | Jun 2, 02:30 UTC | 35m |
| 2026-05-31 | ETH867 | ADD → JRO | May 31, 15:25 UTC | May 31, 17:40 UTC | 2h 15m |
| 2026-05-28 | ETH723 | IST → ADD | May 28, 05:20 UTC | May 28, 07:15 UTC | 1h 55m |
| 2026-05-27 | ETH720 | ADD → IST | May 27, 10:05 UTC | May 28, 01:35 UTC | 15h 30m |
| 2026-05-21 | - | - | May 21, 20:55 UTC | May 22, 09:25 UTC | 12h 30m |
| 2026-05-21 | ETH693 | MAA → ADD | May 21, 04:55 UTC | May 21, 21:00 UTC | 16h 5m |
| 2026-05-21 | ETH692 | ADD → MAA | May 21, 01:40 UTC | May 21, 02:15 UTC | 35m |
| 2026-05-18 | ETH952 | DLA → ADD | May 18, 12:55 UTC | May 18, 13:25 UTC | 30m |
| 2026-05-18 | ETH953 | ADD → DLA | May 18, 10:45 UTC | May 18, 11:10 UTC | 25m |
| 2026-05-16 | ETH721 | IST → ADD | May 16, 21:35 UTC | May 16, 23:05 UTC | 1h 30m |
| 2026-05-16 | ETH722 | ADD → IST | May 16, 04:30 UTC | May 16, 18:50 UTC | 14h 21m |
| 2026-05-15 | ETH407 | BEY → ADD | May 15, 13:15 UTC | May 16, 02:25 UTC | 13h 9m |
| 2026-05-15 | ETH406 | ADD → BEY | May 15, 10:35 UTC | May 15, 11:30 UTC | 55m |
| 2026-05-13 | ETH963 | ADD → DLA | May 13, 23:30 UTC | May 13, 23:55 UTC | 25m |
| 2026-05-11 | ETH415 | TLV → ADD | May 11, 05:10 UTC | May 11, 05:40 UTC | 30m |
| 2026-05-11 | ETH404 | ADD → TLV | May 11, 02:25 UTC | May 11, 02:55 UTC | 30m |
| 2026-05-09 | ETH765 | ATH → ADD | May 9, 13:00 UTC | May 9, 13:50 UTC | 50m |
| 2026-05-09 | ETH764 | ADD → ATH | May 9, 10:20 UTC | May 9, 11:20 UTC | 1h 0m |
| 2026-05-08 | ETH691 | BLR → ADD | May 8, 11:09 UTC | May 8, 11:40 UTC | 30m |
| 2026-05-08 | ETH690 | ADD → BLR | May 8, 01:35 UTC | May 8, 02:04 UTC | 30m |
| 2026-05-02 | ETH962 | DLA → ADD | May 2, 01:00 UTC | May 2, 01:25 UTC | 25m |
| 2026-05-01 | ETH963 | ADD → DLA | May 1, 23:05 UTC | May 1, 23:35 UTC | 30m |
| 2026-04-29 | ETH815 | ADD → JRO | Apr 29, 09:25 UTC | Apr 29, 14:40 UTC | 5h 15m |
| 2026-04-25 | ETH723 | IST → ADD | Apr 25, 05:40 UTC | Apr 25, 07:05 UTC | 1h 25m |
| 2026-04-24 | ETH720 | ADD → IST | Apr 24, 09:15 UTC | Apr 25, 01:40 UTC | 16h 25m |
| 2026-04-18 | ETH815 | ADD → JRO | Apr 18, 20:50 UTC | Apr 19, 15:35 UTC | 18h 45m |
| 2026-04-18 | ETH962 | DLA → ADD | Apr 18, 01:05 UTC | Apr 18, 20:50 UTC | 19h 45m |
| 2026-04-17 | ETH963 | ADD → DLA | Apr 17, 23:25 UTC | Apr 17, 23:35 UTC | 10m |
| 2026-04-17 | ETH963 | ADD → DLA | Apr 17, 23:10 UTC | Apr 17, 23:20 UTC | 10m |
| 2026-04-16 | ETH623 | SHJ → ADD | Apr 16, 01:10 UTC | Apr 16, 01:30 UTC | 20m |
| 2026-04-15 | ETH622 | ADD → SHJ | Apr 15, 22:35 UTC | Apr 15, 23:00 UTC | 25m |
| 2026-04-15 | ETH615 | AUH → ADD | Apr 15, 00:55 UTC | Apr 15, 01:25 UTC | 30m |
| 2026-04-14 | ETH614 | ADD → AUH | Apr 14, 22:30 UTC | Apr 14, 22:40 UTC | 10m |
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-BAJ page for operator, model, and routing details .