sensors Mode-S transponder
44CCD0
ICAO 24-bit transponder address · allocated to Belgium
Currently assigned to OO-SFP · AIRBUS A-330-300
- Hex
- 44CCD0
- Octal
- 21146320
- Decimal
- 4,508,880
- Country
- BE
- Tail
- OO-SFP
- Type
- A333
- Flights observed
- 150
- Distinct callsigns
- 20
- Country
- BE
- Last broadcast
- 7h ago
Current position
Country allocation
The ICAO 24-bit address 44CCD0 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 |
|---|---|---|---|
| BEL52B | - | 25 | 2026-07-09 |
| BEL1CP | - | 24 | 2026-07-09 |
| BEL5YH | Brussels Airlines | 20 | 2026-07-01 |
| BEL2FU | - | 20 | 2026-07-01 |
| BEL27A | - | 9 | 2026-07-13 |
| BEL7WR | - | 8 | 2026-06-30 |
| BEL21W | Brussels Airlines | 7 | 2026-05-29 |
| BEL5TA | - | 5 | 2026-06-25 |
| BEL23D | - | 4 | 2026-07-10 |
| BEL1FF | - | 4 | 2026-07-12 |
| BEL8VB | Brussels Airlines | 3 | 2026-06-14 |
| BEL4TH | Brussels Airlines | 3 | 2026-07-04 |
| BEL24D | - | 3 | 2026-07-10 |
| BEL9TK | Brussels Airlines | 2 | 2026-05-28 |
| BEL5RH | - | 2 | 2026-07-02 |
| BEL4KE | Brussels Airlines | 2 | 2026-06-11 |
| BEL3YG | - | 2 | 2026-07-03 |
| BEL1NA | Brussels Airlines | 2 | 2026-06-12 |
| BEL1BQ | Brussels Airlines | 2 | 2026-06-22 |
| BEL6ZD | Brussels Airlines | 1 | 2026-05-31 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | BEL27A | BRU → BRU | Jul 13, 11:15 UTC | Jul 14, 04:25 UTC | 17h 10m |
| 2026-07-12 | BEL1FF | - | Jul 12, 04:20 UTC | Jul 12, 06:15 UTC | 1h 55m |
| 2026-07-11 | BEL1FF | - | Jul 11, 10:05 UTC | Jul 11, 12:00 UTC | 1h 55m |
| 2026-07-10 | BEL24D | - | Jul 10, 21:40 UTC | Jul 11, 02:55 UTC | 5h 15m |
| 2026-07-10 | BEL24D | - | Jul 10, 20:00 UTC | Jul 10, 20:20 UTC | 20m |
| 2026-07-10 | BEL23D | - | Jul 10, 18:20 UTC | Jul 10, 18:40 UTC | 20m |
| 2026-07-10 | BEL23D | BRU → DSS | Jul 10, 11:20 UTC | Jul 10, 17:05 UTC | 5h 45m |
| 2026-07-09 | BEL52B | JFK → BRU | Jul 9, 22:30 UTC | Jul 10, 05:10 UTC | 6h 40m |
| 2026-07-09 | BEL1CP | BRU → JFK | Jul 9, 09:10 UTC | Jul 9, 16:55 UTC | 7h 45m |
| 2026-07-08 | BEL52B | - | Jul 8, 22:45 UTC | Jul 9, 05:35 UTC | 6h 50m |
| 2026-07-08 | BEL1CP | BRU → JFK | Jul 8, 09:10 UTC | Jul 8, 16:50 UTC | 7h 40m |
| 2026-07-06 | BEL27A | - | Jul 6, 10:35 UTC | Jul 7, 04:05 UTC | 17h 30m |
| 2026-07-05 | BEL27A | BRU → BRU | Jul 5, 10:30 UTC | Jul 6, 04:10 UTC | 17h 40m |
| 2026-07-04 | BEL4TH | BRU → ACC | Jul 4, 11:45 UTC | Jul 5, 03:25 UTC | 15h 40m |
| 2026-07-03 | BEL52B | JFK → BRU | Jul 3, 22:45 UTC | Jul 4, 05:10 UTC | 6h 25m |
| 2026-07-03 | BEL1CP | - | Jul 3, 09:00 UTC | Jul 3, 16:55 UTC | 7h 55m |
| 2026-07-03 | BEL3YG | - | Jul 3, 02:20 UTC | Jul 3, 04:20 UTC | 2h 0m |
| 2026-07-02 | BEL5RH | - | Jul 2, 08:45 UTC | Jul 2, 10:30 UTC | 1h 45m |
| 2026-07-01 | BEL5YH | IAD → BRU | Jul 1, 22:00 UTC | Jul 2, 05:05 UTC | 7h 5m |
| 2026-07-01 | BEL2FU | - | Jul 1, 09:15 UTC | Jul 1, 17:25 UTC | 8h 10m |
| 2026-06-30 | BEL7WR | BRU → BRU | Jun 30, 11:30 UTC | Jul 1, 04:15 UTC | 16h 45m |
| 2026-06-29 | BEL5YH | IAD → BRU | Jun 29, 22:00 UTC | Jun 30, 04:55 UTC | 6h 56m |
| 2026-06-29 | BEL2FU | BRU → IAD | Jun 29, 09:54 UTC | Jun 29, 18:10 UTC | 8h 15m |
| 2026-06-28 | BEL5YH | IAD → BRU | Jun 28, 22:10 UTC | Jun 29, 04:55 UTC | 6h 45m |
| 2026-06-28 | BEL2FU | - | Jun 28, 09:50 UTC | Jun 28, 17:50 UTC | 8h 0m |
| 2026-06-27 | BEL4TH | BRU → ACC | Jun 27, 11:25 UTC | Jun 28, 03:19 UTC | 15h 55m |
| 2026-06-26 | BEL5YH | IAD → BRU | Jun 26, 22:05 UTC | Jun 27, 05:04 UTC | 7h 0m |
| 2026-06-26 | BEL2FU | - | Jun 26, 09:20 UTC | Jun 26, 17:29 UTC | 8h 10m |
| 2026-06-25 | BEL5TA | BRU → BRU | Jun 25, 10:25 UTC | Jun 26, 03:20 UTC | 16h 55m |
| 2026-06-24 | BEL27A | - | Jun 24, 10:39 UTC | Jun 25, 04:10 UTC | 17h 30m |
| 2026-06-22 | BEL1BQ | HER → BRU | Jun 22, 11:14 UTC | Jun 23, 04:25 UTC | 17h 10m |
| 2026-06-21 | BEL52B | JFK → BRU | Jun 21, 23:10 UTC | Jun 22, 05:29 UTC | 6h 20m |
| 2026-06-21 | BEL1CP | BRU → JFK | Jun 21, 09:04 UTC | Jun 21, 16:39 UTC | 7h 35m |
| 2026-06-20 | BEL4TH | BRU → ACC | Jun 20, 11:34 UTC | Jun 21, 03:25 UTC | 15h 50m |
| 2026-06-19 | BEL5YH | IAD → BRU | Jun 19, 22:04 UTC | Jun 20, 04:54 UTC | 6h 50m |
| 2026-06-19 | BEL2FU | - | Jun 19, 09:19 UTC | Jun 19, 17:39 UTC | 8h 20m |
| 2026-06-18 | BEL1BQ | HER → BRU | Jun 18, 10:55 UTC | Jun 19, 04:50 UTC | 17h 54m |
| 2026-06-18 | BEL1FF | BRU → JRO | Jun 18, 04:20 UTC | Jun 18, 06:20 UTC | 2h 0m |
| 2026-06-17 | BEL1FF | BRU → JRO | Jun 17, 09:35 UTC | Jun 17, 12:00 UTC | 2h 25m |
| 2026-06-15 | BEL5YH | IAD → BRU | Jun 15, 22:15 UTC | Jun 16, 05:15 UTC | 7h 0m |
| 2026-06-15 | BEL2FU | - | Jun 15, 09:05 UTC | Jun 15, 17:15 UTC | 8h 10m |
| 2026-06-14 | BEL5YH | IAD → BRU | Jun 14, 21:55 UTC | Jun 15, 04:50 UTC | 6h 55m |
| 2026-06-14 | BEL2FU | - | Jun 14, 15:20 UTC | Jun 14, 17:15 UTC | 1h 55m |
| 2026-06-14 | BEL2FU | - | Jun 14, 09:05 UTC | Jun 14, 15:15 UTC | 6h 10m |
| 2026-06-14 | BEL8VB | BRU → DLA | Jun 14, 01:40 UTC | Jun 14, 03:30 UTC | 1h 50m |
| 2026-06-13 | BEL8VB | BRU → DLA | Jun 13, 21:10 UTC | Jun 13, 21:25 UTC | 15m |
| 2026-06-13 | BEL8VB | BRU → DLA | Jun 13, 10:40 UTC | Jun 13, 12:25 UTC | 1h 45m |
| 2026-06-12 | BEL1NA | EBB → BRU | Jun 12, 10:05 UTC | Jun 13, 04:30 UTC | 18h 24m |
| 2026-06-12 | BEL1NA | EBB → BRU | Jun 12, 09:05 UTC | Jun 13, 04:30 UTC | 19h 24m |
| 2026-06-11 | BEL4KE | EBB → BRU | Jun 11, 10:05 UTC | Jun 12, 04:55 UTC | 18h 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-SFP page for operator, model, and routing details .