sensors Mode-S transponder
44B0B4
ICAO 24-bit transponder address · allocated to Belgium
Currently assigned to OO-LET · BEECH 200 Super King Air
- Hex
- 44B0B4
- Octal
- 21130264
- Decimal
- 4,501,684
- Country
- BE
- Tail
- OO-LET
- Type
- BE20
- Flights observed
- 82
- Distinct callsigns
- 1
- Country
- BE
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 44B0B4 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| OOLET | - | 81 | 2026-07-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | OOLET | - | Jul 26, 17:15 UTC | Jul 26, 20:10 UTC | 2h 55m |
| 2026-07-26 | OOLET | - | Jul 26, 10:35 UTC | Jul 26, 16:15 UTC | 5h 40m |
| 2026-07-26 | OOLET | - | Jul 26, 06:50 UTC | Jul 26, 09:45 UTC | 2h 55m |
| 2026-07-26 | OOLET | - | Jul 26, 05:50 UTC | Jul 26, 06:00 UTC | 10m |
| 2026-07-25 | OOLET | - | Jul 25, 12:50 UTC | Jul 25, 16:30 UTC | 3h 40m |
| 2026-07-25 | OOLET | - | Jul 25, 06:20 UTC | Jul 25, 10:40 UTC | 4h 20m |
| 2026-07-24 | OOLET | - | Jul 24, 06:30 UTC | Jul 24, 10:45 UTC | 4h 15m |
| 2026-07-19 | OOLET | - | Jul 19, 12:40 UTC | Jul 19, 16:30 UTC | 3h 50m |
| 2026-07-19 | OOLET | - | Jul 19, 10:20 UTC | Jul 19, 11:40 UTC | 1h 20m |
| 2026-07-18 | OOLET | - | Jul 18, 12:30 UTC | Jul 18, 17:10 UTC | 4h 40m |
| 2026-07-18 | OOLET | - | Jul 18, 06:35 UTC | Jul 18, 08:20 UTC | 1h 45m |
| 2026-07-16 | OOLET | - | Jul 16, 09:20 UTC | Jul 16, 12:20 UTC | 3h 0m |
| 2026-07-05 | OOLET | - | Jul 5, 16:55 UTC | Jul 5, 18:55 UTC | 2h 0m |
| 2026-07-05 | OOLET | - | Jul 5, 11:40 UTC | Jul 5, 15:15 UTC | 3h 35m |
| 2026-07-05 | OOLET | - | Jul 5, 06:35 UTC | Jul 5, 09:20 UTC | 2h 45m |
| 2026-07-04 | OOLET | - | Jul 4, 13:10 UTC | Jul 4, 17:45 UTC | 4h 35m |
| 2026-07-04 | OOLET | - | Jul 4, 05:40 UTC | Jul 4, 10:30 UTC | 4h 50m |
| 2026-07-03 | OOLET | - | Jul 3, 07:55 UTC | Jul 3, 10:10 UTC | 2h 15m |
| 2026-07-02 | OOLET | - | Jul 2, 14:45 UTC | Jul 2, 17:25 UTC | 2h 40m |
| 2026-06-28 | OOLET | ATH → ANR | Jun 28, 14:19 UTC | Jun 28, 19:20 UTC | 5h 0m |
| 2026-06-28 | OOLET | ATH → ATH | Jun 28, 08:50 UTC | Jun 28, 13:04 UTC | 4h 15m |
| 2026-06-28 | OOLET | ATH → ATH | Jun 28, 04:50 UTC | Jun 28, 07:54 UTC | 3h 5m |
| 2026-06-27 | OOLET | ATH → ATH | Jun 27, 13:20 UTC | Jun 27, 17:34 UTC | 4h 15m |
| 2026-06-27 | OOLET | - | Jun 27, 04:24 UTC | Jun 27, 11:30 UTC | 7h 5m |
| 2026-06-26 | OOLET | ATH → ATH | Jun 26, 10:30 UTC | Jun 26, 15:29 UTC | 5h 0m |
| 2026-06-26 | OOLET | ATH → ATH | Jun 26, 04:55 UTC | Jun 26, 09:35 UTC | 4h 40m |
| 2026-06-25 | OOLET | ATH → ATH | Jun 25, 15:29 UTC | Jun 25, 17:30 UTC | 2h 0m |
| 2026-06-25 | OOLET | ATH → ATH | Jun 25, 05:35 UTC | Jun 25, 07:45 UTC | 2h 10m |
| 2026-06-24 | OOLET | - | Jun 24, 13:14 UTC | Jun 24, 17:34 UTC | 4h 20m |
| 2026-06-11 | OOLET | - | Jun 11, 08:55 UTC | Jun 11, 10:05 UTC | 1h 10m |
| 2026-06-10 | OOLET | - | Jun 10, 14:45 UTC | Jun 10, 18:20 UTC | 3h 35m |
| 2026-06-10 | OOLET | - | Jun 10, 08:35 UTC | Jun 10, 11:00 UTC | 2h 25m |
| 2026-06-09 | OOLET | - | Jun 9, 07:55 UTC | Jun 9, 09:25 UTC | 1h 30m |
| 2026-06-08 | OOLET | - | Jun 8, 15:00 UTC | Jun 8, 17:35 UTC | 2h 35m |
| 2026-06-07 | OOLET | - | Jun 7, 14:35 UTC | Jun 7, 16:10 UTC | 1h 35m |
| 2026-06-07 | OOLET | - | Jun 7, 06:10 UTC | Jun 7, 08:50 UTC | 2h 40m |
| 2026-06-06 | OOLET | - | Jun 6, 16:30 UTC | Jun 6, 19:04 UTC | 2h 35m |
| 2026-06-06 | OOLET | - | Jun 6, 10:09 UTC | Jun 6, 12:45 UTC | 2h 35m |
| 2026-06-05 | OOLET | - | Jun 5, 15:25 UTC | Jun 5, 17:25 UTC | 2h 0m |
| 2026-06-05 | OOLET | - | Jun 5, 04:45 UTC | Jun 5, 09:10 UTC | 4h 25m |
| 2026-06-05 | OOLET | - | Jun 5, 00:25 UTC | Jun 5, 03:45 UTC | 3h 20m |
| 2026-06-04 | OOLET | - | Jun 4, 06:35 UTC | Jun 4, 22:55 UTC | 16h 20m |
| 2026-06-04 | OOLET | - | Jun 4, 03:45 UTC | Jun 4, 04:25 UTC | 40m |
| 2026-06-04 | OOLET | - | Jun 4, 02:35 UTC | Jun 4, 03:10 UTC | 35m |
| 2026-06-03 | OOLET | - | Jun 3, 05:50 UTC | Jun 4, 03:10 UTC | 21h 20m |
| 2026-06-03 | - | - | Jun 3, 04:25 UTC | Jun 3, 04:35 UTC | 10m |
| 2026-06-03 | OOLET | - | Jun 3, 02:10 UTC | Jun 3, 02:50 UTC | 40m |
| 2026-06-01 | OOLET | - | Jun 1, 06:10 UTC | Jun 1, 06:55 UTC | 45m |
| 2026-06-01 | OOLET | - | Jun 1, 04:40 UTC | Jun 1, 04:45 UTC | 5m |
| 2026-06-01 | OOLET | - | Jun 1, 00:30 UTC | Jun 1, 01:00 UTC | 30m |
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-LET page for operator, model, and routing details .