sensors Mode-S transponder
44CCC7
ICAO 24-bit transponder address · allocated to Belgium
Currently assigned to OO-SFG · AIRBUS A-330-300
- Hex
- 44CCC7
- Octal
- 21146307
- Decimal
- 4,508,871
- Country
- BE
- Tail
- OO-SFG
- Type
- A333
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- BE
- Last broadcast
- Jul 26, 10:45 UTC
Last known position
Country allocation
The ICAO 24-bit address 44CCC7 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 |
|---|---|---|---|
| BEL39G | Brussels Airlines | 21 | 2026-07-24 |
| BEL37K | Brussels Airlines | 21 | 2026-07-25 |
| BEL4BE | Brussels Airlines | 15 | 2026-07-26 |
| BEL38K | Brussels Airlines | 15 | 2026-07-07 |
| BEL23D | - | 14 | 2026-07-08 |
| BEL4KE | - | 12 | 2026-07-14 |
| BEL24D | - | 11 | 2026-07-08 |
| BEL1CP | - | 11 | 2026-06-25 |
| BEL8VB | Brussels Airlines | 10 | 2026-07-24 |
| BEL52B | Brussels Airlines | 10 | 2026-06-25 |
| BEL9TK | - | 6 | 2026-06-29 |
| BEL26D | Brussels Airlines | 6 | 2026-05-07 |
| BEL8AN | Brussels Airlines | 5 | 2026-05-07 |
| BEL12B | - | 5 | 2026-07-12 |
| BEL1FF | Brussels Airlines | 4 | 2026-07-19 |
| BEL1BQ | Brussels Airlines | 4 | 2026-07-20 |
| BEL6ZD | Brussels Airlines | 3 | 2026-07-21 |
| BEL5YH | Brussels Airlines | 3 | 2026-05-28 |
| BEL5RH | Brussels Airlines | 3 | 2026-06-05 |
| BEL3YG | Brussels Airlines | 3 | 2026-06-06 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | BEL4BE | EBB → BRU | Jul 26, 08:55 UTC | Jul 26, 10:45 UTC | 1h 50m |
| 2026-07-25 | BEL37K | BRU → FIH | Jul 25, 11:05 UTC | Jul 26, 04:25 UTC | 17h 20m |
| 2026-07-24 | BEL39G | BRU → DLA | Jul 24, 21:15 UTC | Jul 25, 03:40 UTC | 6h 25m |
| 2026-07-24 | BEL39G | BRU → DLA | Jul 24, 11:20 UTC | Jul 24, 13:00 UTC | 1h 40m |
| 2026-07-24 | BEL8VB | BRU → DLA | Jul 24, 01:30 UTC | Jul 24, 03:30 UTC | 2h 0m |
| 2026-07-23 | BEL8VB | BRU → DLA | Jul 23, 21:05 UTC | Jul 23, 21:20 UTC | 15m |
| 2026-07-23 | BEL379 | NSI → BRU | Jul 23, 18:45 UTC | Jul 23, 19:05 UTC | 20m |
| 2026-07-23 | BEL8VB | - | Jul 23, 10:35 UTC | Jul 23, 12:40 UTC | 2h 5m |
| 2026-07-22 | BEL4BE | EBB → BRU | Jul 22, 10:20 UTC | Jul 23, 05:00 UTC | 18h 40m |
| 2026-07-21 | BEL6ZD | BRU → OUA | Jul 21, 09:15 UTC | Jul 22, 03:10 UTC | 17h 55m |
| 2026-07-20 | BEL1BQ | HER → BRU | Jul 20, 11:15 UTC | Jul 21, 03:10 UTC | 15h 55m |
| 2026-07-19 | BEL37K | BRU → FIH | Jul 19, 10:55 UTC | Jul 20, 04:15 UTC | 17h 20m |
| 2026-07-19 | BEL1FF | BRU → JRO | Jul 19, 03:40 UTC | Jul 19, 05:30 UTC | 1h 50m |
| 2026-07-18 | BEL1FF | BRU → JRO | Jul 18, 08:40 UTC | Jul 18, 10:35 UTC | 1h 55m |
| 2026-07-17 | BEL21W | BRU → BRU | Jul 17, 12:04 UTC | Jul 18, 04:00 UTC | 15h 56m |
| 2026-07-14 | BEL4KE | - | Jul 14, 09:50 UTC | Jul 15, 04:15 UTC | 18h 24m |
| 2026-07-14 | BEL4KE | BRU → BRU | Jul 14, 09:05 UTC | Jul 15, 04:15 UTC | 19h 9m |
| 2026-07-13 | BEL5TA | BRU → BRU | Jul 13, 10:35 UTC | Jul 14, 03:20 UTC | 16h 45m |
| 2026-07-12 | BEL12B | BRU → BRU | Jul 12, 10:35 UTC | Jul 13, 03:15 UTC | 16h 40m |
| 2026-07-11 | BEL4KE | - | Jul 11, 09:50 UTC | Jul 12, 04:30 UTC | 18h 40m |
| 2026-07-11 | BEL4KE | BRU → BRU | Jul 11, 08:55 UTC | Jul 12, 04:30 UTC | 19h 35m |
| 2026-07-10 | BEL6ZD | BRU → BRU | Jul 10, 09:40 UTC | Jul 11, 03:40 UTC | 18h 0m |
| 2026-07-09 | BEL37K | BRU → BRU | Jul 9, 11:10 UTC | Jul 10, 04:20 UTC | 17h 10m |
| 2026-07-08 | BEL24D | - | Jul 8, 21:35 UTC | Jul 9, 03:05 UTC | 5h 30m |
| 2026-07-08 | BEL24D | - | Jul 8, 19:40 UTC | Jul 8, 20:05 UTC | 25m |
| 2026-07-08 | BEL23D | - | Jul 8, 17:35 UTC | Jul 8, 18:00 UTC | 25m |
| 2026-07-08 | BEL23D | - | Jul 8, 16:00 UTC | Jul 8, 16:20 UTC | 20m |
| 2026-07-08 | BEL23D | - | Jul 8, 10:50 UTC | Jul 8, 13:40 UTC | 2h 50m |
| 2026-07-07 | BEL38K | FIH → BRU | Jul 7, 10:50 UTC | Jul 8, 04:30 UTC | 17h 40m |
| 2026-07-06 | BEL24D | - | Jul 6, 22:05 UTC | Jul 7, 03:25 UTC | 5h 20m |
| 2026-07-06 | BEL24D | - | Jul 6, 20:20 UTC | Jul 6, 20:35 UTC | 15m |
| 2026-07-06 | BEL23D | - | Jul 6, 18:25 UTC | Jul 6, 18:45 UTC | 20m |
| 2026-07-06 | BEL23D | - | Jul 6, 11:55 UTC | Jul 6, 17:25 UTC | 5h 30m |
| 2026-07-04 | BEL2RA | BRU → BER | Jul 4, 10:40 UTC | Jul 5, 02:50 UTC | 16h 10m |
| 2026-07-03 | BEL38K | FIH → BRU | Jul 3, 10:55 UTC | Jul 4, 05:15 UTC | 18h 20m |
| 2026-07-02 | BEL38K | FIH → BRU | Jul 2, 14:30 UTC | Jul 3, 07:40 UTC | 17h 10m |
| 2026-07-01 | BEL39G | - | Jul 1, 10:30 UTC | Jul 2, 03:30 UTC | 17h 0m |
| 2026-06-30 | BEL4KE | - | Jun 30, 09:50 UTC | Jul 1, 05:10 UTC | 19h 20m |
| 2026-06-30 | BEL4KE | - | Jun 30, 09:10 UTC | Jul 1, 05:10 UTC | 20h 0m |
| 2026-06-29 | BEL39G | - | Jun 29, 11:10 UTC | Jun 30, 03:40 UTC | 16h 31m |
| 2026-06-29 | BEL9TK | - | Jun 29, 03:44 UTC | Jun 29, 05:45 UTC | 2h 0m |
| 2026-06-28 | BEL9TK | - | Jun 28, 09:05 UTC | Jun 28, 11:09 UTC | 2h 5m |
| 2026-06-27 | BEL8VB | BRU → DLA | Jun 27, 10:50 UTC | Jun 28, 03:45 UTC | 16h 55m |
| 2026-06-26 | BEL37K | - | Jun 26, 13:19 UTC | Jun 27, 06:19 UTC | 17h 0m |
| 2026-06-25 | BEL52B | JFK → BRU | Jun 25, 23:14 UTC | Jun 26, 05:44 UTC | 6h 30m |
| 2026-06-25 | BEL1CP | BRU → JFK | Jun 25, 09:10 UTC | Jun 25, 16:59 UTC | 7h 50m |
| 2026-06-24 | BEL52B | JFK → BRU | Jun 24, 22:49 UTC | Jun 25, 05:20 UTC | 6h 30m |
| 2026-06-24 | BEL1CP | - | Jun 24, 15:09 UTC | Jun 24, 16:54 UTC | 1h 45m |
| 2026-06-24 | BEL1CP | - | Jun 24, 09:00 UTC | Jun 24, 15:05 UTC | 6h 5m |
| 2026-06-23 | BEL37K | - | Jun 23, 10:55 UTC | Jun 24, 04:44 UTC | 17h 50m |
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-SFG page for operator, model, and routing details .