sensors Mode-S transponder
44CCC6
ICAO 24-bit transponder address · allocated to Belgium
Currently assigned to OO-SFF · AIRBUS A-330-300
- Hex
- 44CCC6
- Octal
- 21146306
- Decimal
- 4,508,870
- Country
- BE
- Tail
- OO-SFF
- Type
- A333
- Flights observed
- 96
- Distinct callsigns
- 20
- Country
- BE
- Last broadcast
- 15h ago
Current position
Country allocation
The ICAO 24-bit address 44CCC6 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 |
|---|---|---|---|
| BEL4BE | - | 14 | 2026-07-15 |
| BEL37K | - | 12 | 2026-07-08 |
| BEL38K | Brussels Airlines | 8 | 2026-06-10 |
| BEL8VB | Brussels Airlines | 7 | 2026-06-09 |
| BEL52B | Brussels Airlines | 6 | 2026-06-23 |
| BEL4KE | - | 5 | 2026-07-09 |
| BEL39G | - | 5 | 2026-07-14 |
| BEL1CP | - | 4 | 2026-06-23 |
| BEL7MX | - | 3 | 2026-07-11 |
| BEL5YH | Brussels Airlines | 3 | 2026-07-03 |
| BEL2RG | Brussels Airlines | 3 | 2026-07-02 |
| BEL2FU | - | 3 | 2026-07-03 |
| BEL9TK | - | 2 | 2026-06-22 |
| BEL9901 | Brussels Airlines | 2 | 2026-04-25 |
| BEL8AN | - | 2 | 2026-06-30 |
| BEL6ZD | - | 2 | 2026-07-17 |
| BEL5RH | Brussels Airlines | 2 | 2026-06-15 |
| BEL3YG | - | 2 | 2026-06-16 |
| BEL2XJ | Brussels Airlines | 2 | 2026-07-02 |
| BEL26D | Brussels Airlines | 2 | 2026-06-30 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | BEL6ZD | - | Jul 17, 09:30 UTC | Jul 17, 11:30 UTC | 2h 0m |
| 2026-07-16 | BEL1BQ | BRU → BRU | Jul 16, 11:40 UTC | Jul 17, 03:10 UTC | 15h 30m |
| 2026-07-15 | BEL4BE | - | Jul 15, 09:35 UTC | Jul 16, 04:50 UTC | 19h 15m |
| 2026-07-15 | BEL4BE | - | Jul 15, 09:15 UTC | Jul 16, 04:50 UTC | 19h 35m |
| 2026-07-14 | BEL6ZD | BRU → BRU | Jul 14, 09:35 UTC | Jul 15, 03:15 UTC | 17h 39m |
| 2026-07-14 | BEL39G | - | Jul 14, 01:35 UTC | Jul 14, 03:30 UTC | 1h 55m |
| 2026-07-13 | BEL39G | - | Jul 13, 21:10 UTC | Jul 13, 21:25 UTC | 15m |
| 2026-07-13 | BEL39G | - | Jul 13, 19:25 UTC | Jul 13, 19:50 UTC | 25m |
| 2026-07-13 | BEL39G | - | Jul 13, 11:30 UTC | Jul 13, 13:25 UTC | 1h 55m |
| 2026-07-12 | BEL4BE | - | Jul 12, 09:35 UTC | Jul 13, 05:35 UTC | 20h 0m |
| 2026-07-12 | BEL4BE | BRU → BRU | Jul 12, 09:05 UTC | Jul 13, 05:35 UTC | 20h 30m |
| 2026-07-11 | BEL7MX | - | Jul 11, 18:05 UTC | Jul 12, 03:05 UTC | 9h 0m |
| 2026-07-11 | BEL7MX | - | Jul 11, 10:55 UTC | Jul 11, 16:40 UTC | 5h 45m |
| 2026-07-10 | BEL1NA | - | Jul 10, 09:35 UTC | Jul 11, 04:15 UTC | 18h 40m |
| 2026-07-10 | BEL1NA | - | Jul 10, 08:50 UTC | Jul 11, 04:15 UTC | 19h 25m |
| 2026-07-09 | BEL4KE | - | Jul 9, 09:35 UTC | Jul 10, 04:20 UTC | 18h 45m |
| 2026-07-09 | BEL4KE | BRU → BRU | Jul 9, 08:45 UTC | Jul 10, 04:20 UTC | 19h 35m |
| 2026-07-08 | BEL37K | - | Jul 8, 10:50 UTC | Jul 9, 04:05 UTC | 17h 15m |
| 2026-07-07 | BEL4KE | - | Jul 7, 09:05 UTC | Jul 8, 04:30 UTC | 19h 25m |
| 2026-07-06 | BEL39G | BRU → BRU | Jul 6, 11:20 UTC | Jul 7, 03:35 UTC | 16h 15m |
| 2026-07-05 | BEL4BE | - | Jul 5, 09:35 UTC | Jul 6, 05:10 UTC | 19h 35m |
| 2026-07-05 | BEL4BE | BRU → BRU | Jul 5, 08:50 UTC | Jul 6, 05:10 UTC | 20h 20m |
| 2026-07-03 | BEL5YH | IAD → BRU | Jul 3, 22:00 UTC | Jul 4, 05:05 UTC | 7h 5m |
| 2026-07-03 | BEL2FU | - | Jul 3, 09:20 UTC | Jul 3, 17:30 UTC | 8h 10m |
| 2026-07-02 | BEL2XJ | DSS → BRU | Jul 2, 21:50 UTC | Jul 3, 03:05 UTC | 5h 15m |
| 2026-07-02 | BEL2RG | BRU → DSS | Jul 2, 16:30 UTC | Jul 2, 16:50 UTC | 20m |
| 2026-07-02 | BEL2RG | BRU → DSS | Jul 2, 11:15 UTC | Jul 2, 14:00 UTC | 2h 45m |
| 2026-07-01 | BEL4BE | - | Jul 1, 09:35 UTC | Jul 2, 05:00 UTC | 19h 25m |
| 2026-07-01 | BEL4BE | - | Jul 1, 08:50 UTC | Jul 2, 05:00 UTC | 20h 10m |
| 2026-06-30 | BEL26D | CKY → DSS | Jun 30, 22:25 UTC | Jul 1, 03:50 UTC | 5h 25m |
| 2026-06-30 | BEL26D | CKY → DSS | Jun 30, 21:00 UTC | Jun 30, 21:20 UTC | 20m |
| 2026-06-30 | BEL8AN | - | Jun 30, 16:35 UTC | Jun 30, 17:15 UTC | 40m |
| 2026-06-30 | BEL8AN | - | Jun 30, 10:10 UTC | Jun 30, 15:35 UTC | 5h 25m |
| 2026-06-29 | BEL37K | - | Jun 29, 11:29 UTC | Jun 30, 04:40 UTC | 17h 11m |
| 2026-06-28 | BEL4BE | - | Jun 28, 09:34 UTC | Jun 29, 05:09 UTC | 19h 35m |
| 2026-06-28 | BEL4BE | - | Jun 28, 09:20 UTC | Jun 29, 05:09 UTC | 19h 50m |
| 2026-06-27 | BEL37K | BRU → BRU | Jun 27, 11:09 UTC | Jun 28, 04:50 UTC | 17h 40m |
| 2026-06-25 | BEL37K | BRU → BRU | Jun 25, 12:15 UTC | Jun 26, 05:19 UTC | 17h 5m |
| 2026-06-24 | BEL4BE | - | Jun 24, 11:34 UTC | Jun 25, 06:00 UTC | 18h 25m |
| 2026-06-24 | BEL4BE | - | Jun 24, 09:55 UTC | Jun 25, 06:00 UTC | 20h 5m |
| 2026-06-23 | BEL52B | JFK → BRU | Jun 23, 22:44 UTC | Jun 24, 05:29 UTC | 6h 45m |
| 2026-06-23 | BEL1CP | - | Jun 23, 09:14 UTC | Jun 23, 17:09 UTC | 7h 55m |
| 2026-06-22 | BEL5YH | IAD → BRU | Jun 22, 22:34 UTC | Jun 23, 05:45 UTC | 7h 10m |
| 2026-06-22 | BEL2FU | BRU → IAD | Jun 22, 09:14 UTC | Jun 22, 17:29 UTC | 8h 15m |
| 2026-06-22 | BEL9TK | - | Jun 22, 03:40 UTC | Jun 22, 05:44 UTC | 2h 5m |
| 2026-06-21 | BEL9TK | - | Jun 21, 09:00 UTC | Jun 21, 10:44 UTC | 1h 45m |
| 2026-06-20 | BEL1275 | - | Jun 20, 22:25 UTC | Jun 21, 03:49 UTC | 5h 25m |
| 2026-06-20 | BEL7MX | BRU → BJL | Jun 20, 11:44 UTC | Jun 20, 20:25 UTC | 8h 40m |
| 2026-06-19 | BEL37K | BRU → BRU | Jun 19, 11:09 UTC | Jun 20, 04:14 UTC | 17h 5m |
| 2026-06-18 | BEL52B | JFK → BRU | Jun 18, 23:35 UTC | Jun 19, 06:04 UTC | 6h 29m |
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-SFF page for operator, model, and routing details .