sensors Mode-S transponder
06432B
ICAO 24-bit transponder address · allocated to Nigeria
Currently assigned to 5N-CEG · BOEING 777-200
- Hex
- 06432B
- Octal
- 01441453
- Decimal
- 410,411
- Country
- NG
- Tail
- 5N-CEG
- Type
- B772
- Flights observed
- 58
- Distinct callsigns
- 9
- Country
- NG
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 06432B falls within the block assigned to Nigeria (NG) by ICAO Annex 10, Volume III. Every aircraft registered in Nigeria 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 9 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | APO7575 | - | May 29, 21:20 UTC | May 29, 23:20 UTC | 2h 0m |
| 2026-05-29 | APO7574 | - | May 29, 15:25 UTC | May 29, 17:40 UTC | 2h 15m |
| 2026-05-28 | APO7579 | - | May 28, 11:20 UTC | May 28, 13:20 UTC | 2h 0m |
| 2026-05-27 | APO7578 | - | May 27, 10:50 UTC | May 28, 05:15 UTC | 18h 25m |
| 2026-05-26 | APO7578 | - | May 26, 10:50 UTC | May 27, 05:04 UTC | 18h 15m |
| 2026-05-26 | APO7579 | LGW → LGW | May 26, 10:39 UTC | May 27, 05:04 UTC | 18h 25m |
| 2026-05-25 | APO7578 | - | May 25, 10:50 UTC | May 26, 05:05 UTC | 18h 15m |
| 2026-05-24 | APO7578 | - | May 24, 10:50 UTC | May 25, 05:15 UTC | 18h 25m |
| 2026-05-23 | APO7578 | LGW → LGW | May 23, 11:00 UTC | May 24, 05:15 UTC | 18h 16m |
| 2026-05-23 | APO7578 | - | May 23, 03:30 UTC | May 23, 05:40 UTC | 2h 10m |
| 2026-05-21 | APO7579 | - | May 21, 10:50 UTC | May 21, 12:50 UTC | 2h 0m |
| 2026-05-20 | APO7578 | - | May 20, 10:50 UTC | May 21, 05:15 UTC | 18h 25m |
| 2026-05-20 | APO7578 | LGW → LGW | May 20, 10:40 UTC | May 21, 05:15 UTC | 18h 35m |
| 2026-05-19 | APO7578 | LGW → LGW | May 19, 11:00 UTC | May 20, 06:00 UTC | 19h 1m |
| 2026-05-18 | APO7578 | LGW → LGW | May 18, 11:10 UTC | May 19, 05:10 UTC | 17h 59m |
| 2026-05-17 | APO7578 | - | May 17, 10:50 UTC | May 18, 05:10 UTC | 18h 20m |
| 2026-05-17 | APO7578 | LGW → LGW | May 17, 10:40 UTC | May 18, 05:10 UTC | 18h 30m |
| 2026-05-16 | APO7578 | - | May 16, 10:50 UTC | May 17, 06:00 UTC | 19h 10m |
| 2026-05-16 | APO7578 | LGW → LGW | May 16, 10:40 UTC | May 17, 06:00 UTC | 19h 20m |
| 2026-05-15 | APO7578 | LGW → LGW | May 15, 11:10 UTC | May 16, 05:15 UTC | 18h 4m |
| 2026-05-15 | APO7578 | - | May 15, 03:05 UTC | May 15, 05:15 UTC | 2h 10m |
| 2026-05-13 | APO7579 | - | May 13, 10:55 UTC | May 13, 13:05 UTC | 2h 10m |
| 2026-05-12 | AP07578 | - | May 12, 10:50 UTC | May 13, 05:20 UTC | 18h 30m |
| 2026-05-12 | APO7579 | LGW → LGW | May 12, 10:35 UTC | May 13, 05:20 UTC | 18h 45m |
| 2026-05-11 | APO7578 | - | May 11, 10:50 UTC | May 12, 05:15 UTC | 18h 25m |
| 2026-05-11 | APO7579 | LGW → LGW | May 11, 10:30 UTC | May 12, 05:15 UTC | 18h 46m |
| 2026-05-10 | APO7578 | LGW → LGW | May 10, 11:00 UTC | May 11, 05:10 UTC | 18h 10m |
| 2026-05-10 | APO7578 | - | May 10, 03:04 UTC | May 10, 05:10 UTC | 2h 5m |
| 2026-05-08 | APO7579 | - | May 8, 10:44 UTC | May 8, 12:44 UTC | 2h 0m |
| 2026-05-08 | APO7578 | - | May 8, 03:14 UTC | May 8, 05:20 UTC | 2h 5m |
| 2026-05-04 | APO7579 | - | May 4, 11:40 UTC | May 4, 13:45 UTC | 2h 5m |
| 2026-05-03 | APO7578 | LGW → LGW | May 3, 11:00 UTC | May 4, 05:35 UTC | 18h 35m |
| 2026-05-02 | APO7578 | LGW → LGW | May 2, 15:40 UTC | May 3, 06:20 UTC | 14h 39m |
| 2026-04-30 | APO7578 | - | Apr 30, 10:50 UTC | May 1, 06:05 UTC | 19h 15m |
| 2026-04-30 | APO7578 | LGW → LGW | Apr 30, 10:40 UTC | May 1, 06:05 UTC | 19h 25m |
| 2026-04-30 | APK7578 | LOS → LGW | Apr 30, 05:45 UTC | Apr 30, 08:00 UTC | 2h 15m |
| 2026-04-29 | APK7578 | LOS → LGW | Apr 29, 10:50 UTC | Apr 30, 08:00 UTC | 21h 9m |
| 2026-04-29 | APK7578 | LOS → LGW | Apr 29, 10:30 UTC | Apr 30, 08:00 UTC | 21h 29m |
| 2026-04-28 | APO7578 | - | Apr 28, 10:50 UTC | Apr 29, 06:29 UTC | 19h 40m |
| 2026-04-28 | APO7579 | LGW → LGW | Apr 28, 10:40 UTC | Apr 29, 06:29 UTC | 19h 50m |
| 2026-04-28 | APO7578 | - | Apr 28, 04:50 UTC | Apr 28, 07:25 UTC | 2h 35m |
| 2026-04-27 | APO7578 | - | Apr 27, 10:50 UTC | Apr 28, 07:25 UTC | 20h 35m |
| 2026-04-27 | APO7578 | LGW → LGW | Apr 27, 10:25 UTC | Apr 28, 07:25 UTC | 21h 0m |
| 2026-04-26 | APO7578 | - | Apr 26, 10:50 UTC | Apr 27, 05:45 UTC | 18h 55m |
| 2026-04-26 | APO7579 | LGW → LGW | Apr 26, 10:30 UTC | Apr 27, 05:45 UTC | 19h 15m |
| 2026-04-25 | APO7578 | - | Apr 25, 10:50 UTC | Apr 26, 06:10 UTC | 19h 20m |
| 2026-04-25 | APO7578 | LGW → LGW | Apr 25, 10:30 UTC | Apr 26, 06:10 UTC | 19h 40m |
| 2026-04-24 | APK7578 | LOS → LGW | Apr 24, 10:50 UTC | Apr 25, 05:10 UTC | 18h 20m |
| 2026-04-24 | APK7578 | LOS → LGW | Apr 24, 10:30 UTC | Apr 25, 05:10 UTC | 18h 40m |
| 2026-04-24 | APK7578 | LOS → LGW | Apr 24, 03:25 UTC | Apr 24, 05:35 UTC | 2h 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 5N-CEG page for operator, model, and routing details .