sensors Mode-S transponder
3B7B64
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-ZBMB · BEECH 200 Super King Air
- Hex
- 3B7B64
- Octal
- 16675544
- Decimal
- 3,898,212
- Country
- FR
- Tail
- F-ZBMB
- Type
- BE20
- Flights observed
- 57
- Distinct callsigns
- 7
- Country
- FR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address 3B7B64 falls within the block assigned to France (FR) by ICAO Annex 10, Volume III. Every aircraft registered in France 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 7 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | BENGA97 | - | Jul 26, 17:30 UTC | Jul 26, 18:30 UTC | 1h 0m |
| 2026-07-26 | BENGA97 | FNI → BOD | Jul 26, 15:50 UTC | Jul 26, 17:00 UTC | 1h 10m |
| 2026-07-26 | BENGA97 | FNI → FNI | Jul 26, 12:10 UTC | Jul 26, 14:55 UTC | 2h 45m |
| 2026-07-25 | BENGA97 | - | Jul 25, 14:45 UTC | Jul 25, 15:20 UTC | 35m |
| 2026-07-25 | BENGA97 | FNI → CEQ | Jul 25, 12:55 UTC | Jul 25, 13:35 UTC | 40m |
| 2026-07-24 | BENGA97 | BOD → FNI | Jul 24, 21:40 UTC | Jul 24, 22:50 UTC | 1h 10m |
| 2026-07-24 | BENGA97 | FNI → BOD | Jul 24, 19:30 UTC | Jul 24, 20:45 UTC | 1h 15m |
| 2026-07-24 | BENGA97 | - | Jul 24, 14:20 UTC | Jul 24, 14:45 UTC | 25m |
| 2026-07-24 | BENGA97 | - | Jul 24, 13:10 UTC | Jul 24, 13:35 UTC | 25m |
| 2026-07-23 | BENGA97 | - | Jul 23, 15:15 UTC | Jul 23, 16:15 UTC | 1h 0m |
| 2026-07-23 | BENGA97 | - | Jul 23, 12:05 UTC | Jul 23, 13:20 UTC | 1h 15m |
| 2026-07-22 | BENGA97 | - | Jul 22, 04:55 UTC | Jul 22, 05:25 UTC | 30m |
| 2026-07-21 | BENGA97 | - | Jul 21, 16:35 UTC | Jul 21, 19:45 UTC | 3h 10m |
| 2026-07-21 | BENGA97 | - | Jul 21, 12:50 UTC | Jul 21, 15:25 UTC | 2h 35m |
| 2026-07-19 | BENGA97 | - | Jul 19, 14:15 UTC | Jul 19, 15:25 UTC | 1h 10m |
| 2026-07-19 | BENGA97 | - | Jul 19, 12:05 UTC | Jul 19, 13:15 UTC | 1h 10m |
| 2026-07-16 | BENGA9A | - | Jul 16, 17:20 UTC | Jul 16, 18:44 UTC | 1h 25m |
| 2026-07-16 | BENGA9A | - | Jul 16, 15:30 UTC | Jul 16, 16:44 UTC | 1h 15m |
| 2026-07-14 | BENGA97 | - | Jul 14, 13:35 UTC | Jul 14, 14:45 UTC | 1h 10m |
| 2026-07-14 | BENGA97 | - | Jul 14, 11:35 UTC | Jul 14, 12:45 UTC | 1h 10m |
| 2026-07-09 | BENGA9A | BOD → FNI | Jul 9, 10:10 UTC | Jul 9, 11:15 UTC | 1h 5m |
| 2026-07-09 | BENGA9A | - | Jul 9, 08:05 UTC | Jul 9, 09:10 UTC | 1h 5m |
| 2026-07-07 | BENGA97 | - | Jul 7, 19:00 UTC | Jul 7, 20:05 UTC | 1h 5m |
| 2026-07-07 | BENGA97 | - | Jul 7, 17:30 UTC | Jul 7, 18:25 UTC | 55m |
| 2026-07-05 | BENGA9A | - | Jul 5, 10:35 UTC | Jul 5, 12:35 UTC | 2h 0m |
| 2026-07-05 | BENGA9A | - | Jul 5, 08:30 UTC | Jul 5, 09:25 UTC | 55m |
| 2026-07-04 | BENGA97 | - | Jul 4, 14:05 UTC | Jul 4, 16:05 UTC | 2h 0m |
| 2026-07-01 | BENGA97 | - | Jul 1, 15:45 UTC | Jul 1, 18:50 UTC | 3h 5m |
| 2026-06-28 | BENGA97 | - | Jun 28, 10:00 UTC | Jun 28, 10:50 UTC | 50m |
| 2026-06-28 | BENGA97 | - | Jun 28, 08:09 UTC | Jun 28, 09:05 UTC | 55m |
| 2026-06-22 | BENGA97 | - | Jun 22, 08:10 UTC | Jun 22, 09:10 UTC | 1h 0m |
| 2026-06-18 | BENGA97 | - | Jun 18, 08:05 UTC | Jun 18, 10:35 UTC | 2h 30m |
| 2026-05-20 | BENGA9D | - | May 20, 12:10 UTC | May 20, 13:00 UTC | 50m |
| 2026-05-20 | BENGA9B | - | May 20, 08:20 UTC | May 20, 09:25 UTC | 1h 5m |
| 2026-05-19 | BENGA9B | - | May 19, 18:40 UTC | May 19, 19:20 UTC | 40m |
| 2026-05-19 | BENGA9B | - | May 19, 15:45 UTC | May 19, 16:45 UTC | 1h 0m |
| 2026-05-19 | BENGA9B | - | May 19, 09:35 UTC | May 19, 10:30 UTC | 55m |
| 2026-05-19 | BENGA9B | FNI → CEQ | May 19, 07:00 UTC | May 19, 07:30 UTC | 30m |
| 2026-05-14 | BENGA9S | MXP → FNI | May 14, 08:15 UTC | May 14, 09:45 UTC | 1h 30m |
| 2026-05-14 | BENGA9S | FNI → MXP | May 14, 06:10 UTC | May 14, 07:10 UTC | 1h 0m |
| 2026-05-12 | BENGA9S | - | May 12, 15:35 UTC | May 12, 16:50 UTC | 1h 15m |
| 2026-05-12 | BENGA9S | FNI → MXP | May 12, 13:35 UTC | May 12, 14:50 UTC | 1h 15m |
| 2026-05-12 | BENGA9B | - | May 12, 09:20 UTC | May 12, 09:50 UTC | 30m |
| 2026-05-12 | BENGA9B | - | May 12, 08:15 UTC | May 12, 08:40 UTC | 25m |
| 2026-05-11 | BENGA97 | - | May 11, 09:55 UTC | May 11, 10:15 UTC | 20m |
| 2026-05-11 | BENGA97 | - | May 11, 08:15 UTC | May 11, 08:50 UTC | 35m |
| 2026-05-05 | BENGA9C | - | May 5, 14:25 UTC | May 5, 14:50 UTC | 25m |
| 2026-05-05 | BENGA97 | - | May 5, 12:40 UTC | May 5, 13:10 UTC | 30m |
| 2026-05-04 | BENGA9P | - | May 4, 15:20 UTC | May 4, 15:45 UTC | 25m |
| 2026-05-04 | BENGA9P | - | May 4, 14:20 UTC | May 4, 14:45 UTC | 25m |
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 F-ZBMB page for operator, model, and routing details .