sensors Mode-S transponder
04C33A
ICAO 24-bit transponder address · allocated to Kenya
Currently assigned to 5Y-SVR · BOEING 767-300
- Hex
- 04C33A
- Octal
- 01141472
- Decimal
- 312,122
- Country
- KE
- Tail
- 5Y-SVR
- Type
- B763
- Flights observed
- 38
- Distinct callsigns
- 20
- Country
- KE
- Last broadcast
- 2d ago
Last known position
Country allocation
The ICAO 24-bit address 04C33A falls within the block assigned to Kenya (KE) by ICAO Annex 10, Volume III. Every aircraft registered in Kenya 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 |
|---|---|---|---|
| ACP8502 | Astral Aviation | 5 | 2026-05-23 |
| ACP8501 | - | 4 | 2026-05-28 |
| ACP9982 | - | 2 | 2026-04-22 |
| ACP9593 | - | 2 | 2026-05-03 |
| ACP9592 | - | 2 | 2026-05-02 |
| ACP9591 | - | 2 | 2026-04-30 |
| ACP9590 | - | 2 | 2026-05-12 |
| ACP9561 | - | 2 | 2026-04-23 |
| ACP9446 | - | 2 | 2026-04-16 |
| ACP8508 | - | 2 | 2026-05-09 |
| ACP9581 | - | 1 | 2026-05-24 |
| ACP9566 | - | 1 | 2026-04-27 |
| ACP9563 | - | 1 | 2026-04-25 |
| ACP9551 | - | 1 | 2026-05-21 |
| ACP9447 | - | 1 | 2026-04-16 |
| ACP8550 | - | 1 | 2026-05-20 |
| ACP8521 | - | 1 | 2026-05-06 |
| ACP8520 | Astral Aviation | 1 | 2026-05-04 |
| ACP8503 | - | 1 | 2026-04-14 |
| ACP8021 | - | 1 | 2026-04-20 |
Recent flights last 38
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | ACP8501 | - | May 28, 05:50 UTC | May 28, 06:15 UTC | 25m |
| 2026-05-24 | ACP9581 | - | May 24, 08:40 UTC | May 24, 09:20 UTC | 40m |
| 2026-05-23 | ACP8502 | NBO → SHJ | May 23, 10:00 UTC | May 23, 10:20 UTC | 20m |
| 2026-05-21 | ACP9551 | - | May 21, 23:05 UTC | May 21, 23:35 UTC | 30m |
| 2026-05-20 | ACP8550 | - | May 20, 13:00 UTC | May 21, 00:45 UTC | 11h 45m |
| 2026-05-12 | ACP9590 | - | May 12, 11:00 UTC | May 12, 11:40 UTC | 40m |
| 2026-05-11 | ACP9590 | SHJ → SHJ | May 11, 01:00 UTC | May 11, 01:25 UTC | 25m |
| 2026-05-09 | ACP8508 | SHJ → SHJ | May 9, 09:05 UTC | May 9, 09:30 UTC | 25m |
| 2026-05-06 | ACP8521 | - | May 6, 11:10 UTC | May 6, 11:45 UTC | 35m |
| 2026-05-04 | ACP8520 | NBO → JNB | May 4, 16:25 UTC | May 4, 17:00 UTC | 35m |
| 2026-05-04 | - | - | May 4, 08:55 UTC | May 4, 09:05 UTC | 10m |
| 2026-05-04 | ACP8502 | NBO → SHJ | May 4, 00:40 UTC | May 4, 01:05 UTC | 25m |
| 2026-05-03 | ACP9593 | - | May 3, 09:45 UTC | May 3, 10:10 UTC | 25m |
| 2026-05-02 | ACP9593 | - | May 2, 22:00 UTC | May 3, 03:05 UTC | 5h 5m |
| 2026-05-02 | ACP9592 | - | May 2, 04:35 UTC | May 2, 04:45 UTC | 10m |
| 2026-05-01 | ACP9592 | - | May 1, 23:20 UTC | May 2, 03:25 UTC | 4h 5m |
| 2026-04-30 | ACP9591 | - | Apr 30, 23:45 UTC | Apr 30, 23:55 UTC | 10m |
| 2026-04-30 | ACP9591 | - | Apr 30, 14:55 UTC | Apr 30, 23:05 UTC | 8h 10m |
| 2026-04-30 | ACP8501 | - | Apr 30, 06:40 UTC | Apr 30, 07:05 UTC | 25m |
| 2026-04-29 | ACP8502 | NBO → SHJ | Apr 29, 08:55 UTC | Apr 29, 09:25 UTC | 31m |
| 2026-04-29 | ACP8508 | - | Apr 29, 04:10 UTC | Apr 29, 05:40 UTC | 1h 30m |
| 2026-04-27 | ACP9566 | - | Apr 27, 05:10 UTC | Apr 27, 05:20 UTC | 10m |
| 2026-04-25 | ACP9563 | - | Apr 25, 09:15 UTC | Apr 25, 10:20 UTC | 1h 5m |
| 2026-04-23 | ACP9561 | - | Apr 23, 09:01 UTC | Apr 23, 09:20 UTC | 20m |
| 2026-04-22 | ACP9982 | - | Apr 22, 12:50 UTC | Apr 22, 13:15 UTC | 25m |
| 2026-04-22 | ACP9982 | - | Apr 22, 07:50 UTC | Apr 22, 08:55 UTC | 1h 5m |
| 2026-04-21 | ACP9561 | - | Apr 21, 15:55 UTC | Apr 21, 16:55 UTC | 1h 0m |
| 2026-04-20 | ACP8021 | - | Apr 20, 03:50 UTC | Apr 20, 04:15 UTC | 25m |
| 2026-04-19 | ACP8020 | - | Apr 19, 23:25 UTC | Apr 20, 00:00 UTC | 35m |
| 2026-04-19 | 5YSVR | - | Apr 19, 16:45 UTC | Apr 19, 16:55 UTC | 10m |
| 2026-04-19 | ACP8502 | NBO → SHJ | Apr 19, 01:20 UTC | Apr 19, 01:50 UTC | 30m |
| 2026-04-18 | ACP8501 | - | Apr 18, 11:00 UTC | Apr 18, 11:30 UTC | 30m |
| 2026-04-16 | ACP9447 | - | Apr 16, 23:25 UTC | Apr 17, 00:10 UTC | 45m |
| 2026-04-16 | ACP9446 | - | Apr 16, 04:40 UTC | Apr 16, 04:49 UTC | 10m |
| 2026-04-15 | ACP9446 | - | Apr 15, 18:00 UTC | Apr 15, 18:20 UTC | 20m |
| 2026-04-14 | ACP8503 | - | Apr 14, 21:30 UTC | Apr 14, 21:55 UTC | 25m |
| 2026-04-14 | ACP8502 | NBO → SHJ | Apr 14, 07:20 UTC | Apr 14, 07:40 UTC | 20m |
| 2026-04-13 | ACP8501 | - | Apr 13, 06:45 UTC | Apr 13, 07:10 UTC | 25m |
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 5Y-SVR page for operator, model, and routing details .