sensors Mode-S transponder
040263
ICAO 24-bit transponder address · allocated to Ethiopia
Currently assigned to ET-BCF · BOEING 737-700
- Hex
- 040263
- Octal
- 01001143
- Decimal
- 262,755
- Country
- ET
- Tail
- ET-BCF
- Type
- B737
- Flights observed
- 40
- Distinct callsigns
- 4
- Country
- ET
- Last broadcast
- 2h ago
Last known position
Country allocation
The ICAO 24-bit address 040263 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 4 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| MWI024 | Malaysia Wings | 25 | 2026-05-30 |
| MWI025 | Malaysia Wings | 13 | 2026-05-30 |
| MW025 | - | 1 | 2026-05-11 |
| MW024 | - | 1 | 2026-05-09 |
Recent flights last 40
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | MWI025 | JNB → LLW | May 30, 11:55 UTC | May 30, 12:15 UTC | 20m |
| 2026-05-30 | MWI024 | LLW → JNB | May 30, 10:20 UTC | May 30, 10:55 UTC | 35m |
| 2026-05-25 | MWI025 | JNB → LLW | May 25, 12:00 UTC | May 25, 12:25 UTC | 25m |
| 2026-05-25 | MWI024 | LLW → JNB | May 25, 10:15 UTC | May 25, 10:50 UTC | 35m |
| 2026-05-24 | MWI024 | LLW → JNB | May 24, 12:00 UTC | May 25, 10:45 UTC | 22h 45m |
| 2026-05-24 | MWI024 | LLW → JNB | May 24, 10:05 UTC | May 24, 10:40 UTC | 35m |
| 2026-05-23 | MWI025 | JNB → LLW | May 23, 12:00 UTC | May 23, 12:20 UTC | 20m |
| 2026-05-23 | MWI024 | LLW → JNB | May 23, 10:10 UTC | May 23, 10:50 UTC | 40m |
| 2026-05-18 | MWI025 | JNB → LLW | May 18, 12:10 UTC | May 18, 12:35 UTC | 25m |
| 2026-05-18 | MWI024 | LLW → JNB | May 18, 10:35 UTC | May 18, 11:05 UTC | 30m |
| 2026-05-17 | MWI025 | JNB → LLW | May 17, 12:15 UTC | May 18, 10:45 UTC | 22h 30m |
| 2026-05-17 | MWI024 | LLW → JNB | May 17, 10:10 UTC | May 17, 10:50 UTC | 40m |
| 2026-05-16 | MWI024 | LLW → JNB | May 16, 11:55 UTC | May 17, 10:45 UTC | 22h 50m |
| 2026-05-16 | MWI024 | LLW → JNB | May 16, 10:11 UTC | May 16, 10:46 UTC | 35m |
| 2026-05-11 | MW025 | - | May 11, 12:15 UTC | May 11, 12:40 UTC | 25m |
| 2026-05-11 | MWI024 | LLW → JNB | May 11, 10:35 UTC | May 11, 11:05 UTC | 30m |
| 2026-05-10 | MWI025 | JNB → LLW | May 10, 12:10 UTC | May 11, 10:45 UTC | 22h 35m |
| 2026-05-10 | MWI024 | LLW → JNB | May 10, 10:24 UTC | May 10, 10:55 UTC | 30m |
| 2026-05-09 | MWI025 | JNB → LLW | May 9, 11:40 UTC | May 10, 10:45 UTC | 23h 5m |
| 2026-05-09 | MW024 | - | May 9, 10:15 UTC | May 9, 10:45 UTC | 30m |
| 2026-05-04 | MWI025 | JNB → LLW | May 4, 11:50 UTC | May 4, 12:10 UTC | 20m |
| 2026-05-04 | MWI024 | LLW → JNB | May 4, 10:10 UTC | May 4, 10:45 UTC | 35m |
| 2026-05-03 | MWI024 | LLW → JNB | May 3, 12:10 UTC | May 4, 10:45 UTC | 22h 35m |
| 2026-05-03 | MWI024 | LLW → JNB | May 3, 10:15 UTC | May 3, 10:45 UTC | 30m |
| 2026-05-02 | MWI025 | JNB → LLW | May 2, 12:00 UTC | May 2, 12:25 UTC | 25m |
| 2026-05-02 | MWI024 | LLW → JNB | May 2, 10:15 UTC | May 2, 10:45 UTC | 30m |
| 2026-04-27 | MWI025 | JNB → LLW | Apr 27, 12:00 UTC | Apr 27, 12:25 UTC | 25m |
| 2026-04-27 | MWI024 | LLW → JNB | Apr 27, 10:20 UTC | Apr 27, 10:50 UTC | 30m |
| 2026-04-26 | MWI024 | LLW → JNB | Apr 26, 12:05 UTC | Apr 27, 10:45 UTC | 22h 40m |
| 2026-04-26 | MWI024 | LLW → JNB | Apr 26, 10:15 UTC | Apr 26, 10:50 UTC | 35m |
| 2026-04-25 | MWI024 | LLW → JNB | Apr 25, 12:15 UTC | Apr 26, 10:45 UTC | 22h 30m |
| 2026-04-25 | MWI024 | LLW → JNB | Apr 25, 10:35 UTC | Apr 25, 11:00 UTC | 25m |
| 2026-04-20 | MWI025 | JNB → LLW | Apr 20, 12:10 UTC | Apr 20, 12:30 UTC | 20m |
| 2026-04-20 | MWI024 | LLW → JNB | Apr 20, 10:20 UTC | Apr 20, 10:55 UTC | 35m |
| 2026-04-19 | MWI025 | JNB → LLW | Apr 19, 11:50 UTC | Apr 20, 10:45 UTC | 22h 55m |
| 2026-04-19 | MWI024 | LLW → JNB | Apr 19, 10:10 UTC | Apr 19, 10:45 UTC | 35m |
| 2026-04-18 | MWI024 | LLW → JNB | Apr 18, 12:05 UTC | Apr 19, 10:45 UTC | 22h 40m |
| 2026-04-18 | MWI024 | LLW → JNB | Apr 18, 10:25 UTC | Apr 18, 10:55 UTC | 30m |
| 2026-04-13 | MWI025 | - | Apr 13, 12:00 UTC | Apr 13, 12:15 UTC | 15m |
| 2026-04-13 | MWI024 | LLW → JNB | Apr 13, 10:15 UTC | Apr 13, 10:50 UTC | 35m |
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-BCF page for operator, model, and routing details .