sensors Mode-S transponder
44CCC8
ICAO 24-bit transponder address · allocated to Belgium
Currently assigned to OO-SFH · AIRBUS A-330-300
- Hex
- 44CCC8
- Octal
- 21146310
- Decimal
- 4,508,872
- Country
- BE
- Tail
- OO-SFH
- Type
- A333
- Flights observed
- 178
- Distinct callsigns
- 20
- Country
- BE
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 44CCC8 falls within the block assigned to Belgium (BE) by ICAO Annex 10, Volume III. Every aircraft registered in Belgium 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 |
|---|---|---|---|
| BEL4KE | - | 23 | 2026-07-02 |
| BEL23D | - | 23 | 2026-07-01 |
| BEL39G | - | 17 | 2026-06-26 |
| BEL24D | - | 17 | 2026-07-02 |
| BEL37K | - | 10 | 2026-07-12 |
| BEL8VB | Brussels Airlines | 8 | 2026-06-20 |
| BEL8AN | Brussels Airlines | 7 | 2026-05-21 |
| BEL52B | Brussels Airlines | 6 | 2026-05-30 |
| BEL1NA | - | 6 | 2026-06-15 |
| BEL5RH | - | 5 | 2026-07-13 |
| BEL3YG | - | 5 | 2026-07-14 |
| BEL26D | Brussels Airlines | 5 | 2026-05-21 |
| BEL8LE | - | 4 | 2026-06-23 |
| BEL7MX | Brussels Airlines | 4 | 2026-07-04 |
| BEL6ZD | - | 4 | 2026-06-19 |
| BEL1FF | Brussels Airlines | 4 | 2026-06-28 |
| BEL5YH | - | 3 | 2026-07-11 |
| BEL2FU | - | 3 | 2026-07-11 |
| BEL27A | Brussels Airlines | 3 | 2026-06-05 |
| BEL9TK | Brussels Airlines | 2 | 2026-06-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | BEL2RG | - | Jul 14, 11:05 UTC | Jul 14, 12:00 UTC | 55m |
| 2026-07-14 | BEL3YG | - | Jul 14, 02:20 UTC | Jul 14, 04:15 UTC | 1h 55m |
| 2026-07-13 | BEL5RH | - | Jul 13, 09:15 UTC | Jul 13, 11:20 UTC | 2h 5m |
| 2026-07-12 | BEL37K | BRU → BRU | Jul 12, 10:55 UTC | Jul 13, 04:25 UTC | 17h 30m |
| 2026-07-11 | BEL5YH | IAD → BRU | Jul 11, 22:20 UTC | Jul 12, 05:20 UTC | 7h 0m |
| 2026-07-11 | BEL2FU | BRU → IAD | Jul 11, 09:35 UTC | Jul 11, 17:45 UTC | 8h 10m |
| 2026-07-10 | BEL37K | BRU → BRU | Jul 10, 10:50 UTC | Jul 11, 04:05 UTC | 17h 15m |
| 2026-07-07 | BEL28A | - | Jul 7, 10:30 UTC | Jul 8, 04:10 UTC | 17h 40m |
| 2026-07-06 | BEL37K | BRU → BRU | Jul 6, 11:00 UTC | Jul 7, 04:20 UTC | 17h 20m |
| 2026-07-06 | BEL5YH | IAD → BRU | Jul 6, 00:30 UTC | Jul 6, 07:20 UTC | 6h 50m |
| 2026-07-05 | BEL2FU | BRU → IAD | Jul 5, 09:20 UTC | Jul 5, 17:30 UTC | 8h 10m |
| 2026-07-04 | BEL7MX | BRU → BJL | Jul 4, 18:25 UTC | Jul 5, 03:10 UTC | 8h 45m |
| 2026-07-04 | BEL7MX | BRU → BJL | Jul 4, 10:45 UTC | Jul 4, 16:40 UTC | 5h 55m |
| 2026-07-03 | BEL21W | - | Jul 3, 11:00 UTC | Jul 4, 04:05 UTC | 17h 5m |
| 2026-07-02 | BEL4KE | - | Jul 2, 10:05 UTC | Jul 3, 04:30 UTC | 18h 25m |
| 2026-07-02 | BEL4KE | - | Jul 2, 09:05 UTC | Jul 3, 04:30 UTC | 19h 25m |
| 2026-07-02 | BEL24D | - | Jul 2, 00:50 UTC | Jul 2, 03:40 UTC | 2h 50m |
| 2026-07-01 | BEL204 | - | Jul 1, 22:15 UTC | Jul 1, 22:40 UTC | 25m |
| 2026-07-01 | BEL24D | - | Jul 1, 20:30 UTC | Jul 1, 20:55 UTC | 25m |
| 2026-07-01 | BEL23D | - | Jul 1, 18:55 UTC | Jul 1, 19:10 UTC | 15m |
| 2026-07-01 | BEL23D | - | Jul 1, 12:45 UTC | Jul 1, 18:00 UTC | 5h 15m |
| 2026-06-29 | BEL24D | - | Jun 29, 21:30 UTC | Jun 30, 03:00 UTC | 5h 31m |
| 2026-06-29 | BEL24D | - | Jun 29, 20:04 UTC | Jun 29, 20:30 UTC | 25m |
| 2026-06-29 | BEL203 | - | Jun 29, 18:05 UTC | Jun 29, 18:19 UTC | 15m |
| 2026-06-29 | BEL23D | - | Jun 29, 16:29 UTC | Jun 29, 16:55 UTC | 25m |
| 2026-06-29 | BEL23D | - | Jun 29, 11:25 UTC | Jun 29, 14:09 UTC | 2h 45m |
| 2026-06-28 | BEL37K | - | Jun 28, 11:50 UTC | Jun 29, 04:50 UTC | 17h 0m |
| 2026-06-28 | BEL1FF | BRU → JRO | Jun 28, 04:10 UTC | Jun 28, 06:05 UTC | 1h 55m |
| 2026-06-27 | BEL1FF | BRU → JRO | Jun 27, 09:04 UTC | Jun 27, 10:54 UTC | 1h 50m |
| 2026-06-26 | BEL39G | - | Jun 26, 12:55 UTC | Jun 27, 04:54 UTC | 16h 0m |
| 2026-06-25 | BEL1FF | BRU → JRO | Jun 25, 03:50 UTC | Jun 25, 06:00 UTC | 2h 10m |
| 2026-06-24 | BEL1FF | BRU → JRO | Jun 24, 09:09 UTC | Jun 24, 11:09 UTC | 2h 0m |
| 2026-06-23 | BEL8LE | - | Jun 23, 09:24 UTC | Jun 24, 03:35 UTC | 18h 10m |
| 2026-06-22 | BEL39G | BRU → BRU | Jun 22, 10:40 UTC | Jun 23, 03:09 UTC | 16h 30m |
| 2026-06-21 | BEL8LE | - | Jun 21, 10:04 UTC | Jun 22, 04:04 UTC | 18h 0m |
| 2026-06-21 | BEL8LE | - | Jun 21, 09:40 UTC | Jun 22, 04:04 UTC | 18h 25m |
| 2026-06-20 | BEL8VB | BRU → DLA | Jun 20, 12:09 UTC | Jun 21, 04:34 UTC | 16h 25m |
| 2026-06-19 | BEL6ZD | - | Jun 19, 09:24 UTC | Jun 20, 03:29 UTC | 18h 5m |
| 2026-06-19 | BEL3YG | - | Jun 19, 02:19 UTC | Jun 19, 04:29 UTC | 2h 10m |
| 2026-06-18 | BEL5RH | - | Jun 18, 08:50 UTC | Jun 18, 10:50 UTC | 2h 0m |
| 2026-06-17 | BEL37K | - | Jun 17, 10:30 UTC | Jun 18, 05:00 UTC | 18h 30m |
| 2026-06-15 | BEL1NA | - | Jun 15, 10:05 UTC | Jun 16, 04:25 UTC | 18h 20m |
| 2026-06-15 | BEL1NA | - | Jun 15, 08:54 UTC | Jun 16, 04:25 UTC | 19h 30m |
| 2026-06-14 | BEL21W | - | Jun 14, 11:10 UTC | Jun 15, 03:40 UTC | 16h 29m |
| 2026-06-13 | BEL5YH | IAD → BRU | Jun 13, 21:55 UTC | Jun 14, 04:55 UTC | 7h 0m |
| 2026-06-13 | BEL2FU | - | Jun 13, 09:10 UTC | Jun 13, 17:20 UTC | 8h 10m |
| 2026-06-13 | BEL39G | BRU → DLA | Jun 13, 01:10 UTC | Jun 13, 03:15 UTC | 2h 5m |
| 2026-06-12 | BEL39G | BRU → DLA | Jun 12, 20:50 UTC | Jun 12, 21:05 UTC | 15m |
| 2026-06-12 | BEL369 | - | Jun 12, 18:45 UTC | Jun 12, 19:05 UTC | 20m |
| 2026-06-12 | BEL39G | BRU → DLA | Jun 12, 10:25 UTC | Jun 12, 12:10 UTC | 1h 45m |
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 OO-SFH page for operator, model, and routing details .