sensors Mode-S transponder
394A0E
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQO · BOEING 777-300ER
- Hex
- 394A0E
- Octal
- 16245016
- Decimal
- 3,754,510
- Country
- FR
- Tail
- F-GSQO
- Type
- B77W
- Flights observed
- 147
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 14d ago
Last known position
Country allocation
The ICAO 24-bit address 394A0E 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| AFR345M | Air France | 16 | 2026-05-29 |
| AFR344 | Air France | 15 | 2026-05-29 |
| AFR473 | - | 12 | 2026-06-26 |
| AFR809 | Air France | 10 | 2026-05-10 |
| AFR647 | - | 8 | 2026-06-22 |
| AFR673 | - | 7 | 2026-06-16 |
| AFR500 | - | 7 | 2026-06-17 |
| AFR672 | Air France | 6 | 2026-06-15 |
| AFR651 | Air France | 6 | 2026-06-10 |
| AFR501 | - | 6 | 2026-06-17 |
| AFR328K | Air France | 5 | 2026-05-27 |
| AFR327 | Air France | 5 | 2026-05-27 |
| AFR837 | - | 4 | 2026-06-28 |
| AFR771 | Air France | 4 | 2026-04-21 |
| AFR470 | - | 4 | 2026-06-25 |
| AFR816 | Air France | 3 | 2026-05-30 |
| AFR758 | Air France | 3 | 2026-05-20 |
| AFR650 | Air France | 3 | 2026-06-09 |
| AFR358P | Air France | 3 | 2026-06-11 |
| AFR836 | - | 2 | 2026-06-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-29 | AFR372V | - | Jun 29, 09:05 UTC | Jun 29, 10:04 UTC | 1h 0m |
| 2026-06-28 | AFR837 | - | Jun 28, 09:34 UTC | Jun 29, 05:04 UTC | 19h 30m |
| 2026-06-28 | AFR837 | - | Jun 28, 09:20 UTC | Jun 29, 05:04 UTC | 19h 45m |
| 2026-06-27 | AFR770 | - | Jun 27, 11:04 UTC | Jun 28, 05:29 UTC | 18h 25m |
| 2026-06-26 | AFR473 | - | Jun 26, 18:20 UTC | Jun 26, 20:04 UTC | 1h 45m |
| 2026-06-25 | AFR473 | - | Jun 25, 23:34 UTC | Jun 26, 20:04 UTC | 20h 30m |
| 2026-06-25 | AFR473 | - | Jun 25, 21:35 UTC | Jun 26, 20:04 UTC | 22h 30m |
| 2026-06-25 | AFR470 | - | Jun 25, 19:49 UTC | Jun 26, 19:30 UTC | 23h 40m |
| 2026-06-24 | AFR837 | - | Jun 24, 09:34 UTC | Jun 25, 04:20 UTC | 18h 45m |
| 2026-06-24 | AFR836 | - | Jun 24, 09:05 UTC | Jun 25, 04:20 UTC | 19h 15m |
| 2026-06-22 | AFR647 | - | Jun 22, 19:34 UTC | Jun 23, 17:09 UTC | 21h 35m |
| 2026-06-22 | AFR647 | - | Jun 22, 17:34 UTC | Jun 23, 17:09 UTC | 23h 35m |
| 2026-06-22 | AFR652 | - | Jun 22, 17:20 UTC | Jun 23, 15:30 UTC | 22h 10m |
| 2026-06-22 | AFR353 | - | Jun 22, 09:34 UTC | Jun 22, 11:14 UTC | 1h 40m |
| 2026-06-22 | AFR353 | - | Jun 22, 05:20 UTC | Jun 22, 06:10 UTC | 50m |
| 2026-06-21 | AFR352 | - | Jun 21, 20:34 UTC | Jun 22, 02:59 UTC | 6h 25m |
| 2026-06-21 | AFR647 | - | Jun 21, 13:20 UTC | Jun 21, 17:24 UTC | 4h 5m |
| 2026-06-20 | AFR647 | - | Jun 20, 19:34 UTC | Jun 21, 17:24 UTC | 21h 50m |
| 2026-06-20 | AFR647 | - | Jun 20, 17:34 UTC | Jun 21, 17:24 UTC | 23h 50m |
| 2026-06-20 | AFR652 | - | Jun 20, 16:59 UTC | Jun 21, 13:29 UTC | 20h 30m |
| 2026-06-19 | AFR473 | - | Jun 19, 14:24 UTC | Jun 19, 17:29 UTC | 3h 5m |
| 2026-06-18 | AFR473 | - | Jun 18, 19:55 UTC | Jun 19, 17:29 UTC | 21h 34m |
| 2026-06-18 | AFR473 | - | Jun 18, 17:35 UTC | Jun 19, 17:29 UTC | 23h 54m |
| 2026-06-18 | AFR470 | - | Jun 18, 17:10 UTC | Jun 19, 15:29 UTC | 22h 19m |
| 2026-06-17 | AFR501 | - | Jun 17, 17:00 UTC | Jun 18, 10:55 UTC | 17h 55m |
| 2026-06-17 | AFR500 | - | Jun 17, 09:35 UTC | Jun 18, 09:30 UTC | 23h 55m |
| 2026-06-17 | AFR500 | - | Jun 17, 08:50 UTC | Jun 18, 02:55 UTC | 18h 5m |
| 2026-06-16 | AFR673 | - | Jun 16, 23:50 UTC | Jun 17, 03:45 UTC | 3h 55m |
| 2026-06-16 | AFR673 | - | Jun 16, 01:40 UTC | Jun 17, 01:30 UTC | 23h 51m |
| 2026-06-15 | AFR672 | MEX → CDG | Jun 15, 22:05 UTC | Jun 16, 01:45 UTC | 3h 40m |
| 2026-06-14 | AFR501 | - | Jun 14, 18:50 UTC | Jun 15, 11:54 UTC | 17h 4m |
| 2026-06-14 | AFR501 | - | Jun 14, 11:55 UTC | Jun 15, 11:30 UTC | 23h 35m |
| 2026-06-14 | AFR500 | - | Jun 14, 09:35 UTC | Jun 15, 04:10 UTC | 18h 34m |
| 2026-06-14 | AFR500 | - | Jun 14, 08:55 UTC | Jun 15, 04:10 UTC | 19h 14m |
| 2026-06-14 | AFR673 | - | Jun 14, 00:45 UTC | Jun 14, 03:50 UTC | 3h 5m |
| 2026-06-12 | AFR672 | MEX → CDG | Jun 12, 21:45 UTC | Jun 13, 00:25 UTC | 2h 40m |
| 2026-06-12 | AFR359P | - | Jun 12, 03:40 UTC | Jun 12, 10:20 UTC | 6h 40m |
| 2026-06-11 | AFR358P | CDG → YYZ | Jun 11, 16:55 UTC | Jun 12, 00:25 UTC | 7h 30m |
| 2026-06-11 | AFR349 | YUL → CDG | Jun 11, 02:55 UTC | Jun 11, 09:00 UTC | 6h 5m |
| 2026-06-10 | AFR348F | CDG → YUL | Jun 10, 16:50 UTC | Jun 11, 00:00 UTC | 7h 10m |
| 2026-06-10 | AFR651 | CUN → CDG | Jun 10, 03:30 UTC | Jun 10, 12:35 UTC | 9h 5m |
| 2026-06-09 | AFR650 | CDG → CUN | Jun 9, 13:30 UTC | Jun 9, 23:35 UTC | 10h 5m |
| 2026-06-03 | AFR473 | MRU → CDG | Jun 3, 13:15 UTC | Jun 3, 17:35 UTC | 4h 20m |
| 2026-06-02 | AFR473 | MRU → CDG | Jun 2, 19:35 UTC | Jun 3, 17:35 UTC | 22h 0m |
| 2026-06-02 | AFR473 | MRU → CDG | Jun 2, 17:35 UTC | Jun 3, 17:30 UTC | 23h 55m |
| 2026-06-02 | AFR470 | CDG → MRU | Jun 2, 16:50 UTC | Jun 3, 15:30 UTC | 22h 40m |
| 2026-06-02 | AFR501 | ABJ → ACC | Jun 2, 09:35 UTC | Jun 2, 10:55 UTC | 1h 20m |
| 2026-06-01 | AFR500 | ACC → ABJ | Jun 1, 09:05 UTC | Jun 1, 19:45 UTC | 10h 40m |
| 2026-05-31 | AFR51GN | BUD → CDG | May 31, 18:15 UTC | May 31, 20:15 UTC | 2h 0m |
| 2026-05-31 | AFR53FD | CDG → BUD | May 31, 14:30 UTC | May 31, 16:10 UTC | 1h 40m |
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-GSQO page for operator, model, and routing details .