sensors Mode-S transponder
394A0D
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQN · BOEING 777-300ER
- Hex
- 394A0D
- Octal
- 16245015
- Decimal
- 3,754,509
- Country
- FR
- Tail
- F-GSQN
- Type
- B77W
- Flights observed
- 181
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- Jul 26, 19:00 UTC
Last known position
Country allocation
The ICAO 24-bit address 394A0D 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 |
|---|---|---|---|
| AFR647 | Air France | 18 | 2026-07-24 |
| AFR473 | - | 13 | 2026-06-21 |
| AFR771 | - | 10 | 2026-07-11 |
| AFR763 | Air France | 10 | 2026-07-18 |
| AFR344 | - | 10 | 2026-06-23 |
| AFR345M | - | 9 | 2026-06-23 |
| AFR652 | Air France | 8 | 2026-07-23 |
| AFR837 | Air France | 6 | 2026-06-08 |
| AFR669 | - | 6 | 2026-07-10 |
| AFR359P | - | 6 | 2026-07-23 |
| AFR358P | Air France | 6 | 2026-07-22 |
| AFR672 | Air France | 5 | 2026-06-22 |
| AFR668 | - | 5 | 2026-07-08 |
| AFR650 | Air France | 5 | 2026-07-17 |
| AFR328K | Air France | 5 | 2026-07-26 |
| AFR842 | - | 4 | 2026-07-10 |
| AFR809 | - | 4 | 2026-07-16 |
| AFR673 | - | 4 | 2026-06-23 |
| AFR651 | - | 4 | 2026-07-18 |
| AFR470 | - | 4 | 2026-06-20 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFR328K | CDG → YOW | Jul 26, 11:55 UTC | Jul 26, 18:55 UTC | 7h 0m |
| 2026-07-26 | AFR347F | YUL → CDG | Jul 26, 01:40 UTC | Jul 26, 07:50 UTC | 6h 11m |
| 2026-07-25 | AFR346 | CDG → YUL | Jul 25, 15:35 UTC | Jul 25, 22:10 UTC | 6h 35m |
| 2026-07-25 | AFR353 | YQB → CDG | Jul 25, 05:25 UTC | Jul 25, 11:20 UTC | 5h 55m |
| 2026-07-24 | AFR352 | CDG → YQB | Jul 24, 19:50 UTC | Jul 25, 02:15 UTC | 6h 25m |
| 2026-07-24 | AFR647 | RUN → CDG | Jul 24, 12:15 UTC | Jul 24, 16:20 UTC | 4h 5m |
| 2026-07-23 | AFR647 | RUN → CDG | Jul 23, 17:20 UTC | Jul 24, 16:20 UTC | 23h 0m |
| 2026-07-23 | AFR652 | ORY → FDF | Jul 23, 16:10 UTC | Jul 24, 15:15 UTC | 23h 5m |
| 2026-07-23 | AFR359P | - | Jul 23, 04:00 UTC | Jul 23, 10:40 UTC | 6h 40m |
| 2026-07-22 | AFR358P | CDG → YYZ | Jul 22, 17:20 UTC | Jul 23, 00:45 UTC | 7h 25m |
| 2026-07-21 | AFR758 | - | Jul 21, 14:45 UTC | Jul 21, 16:05 UTC | 1h 20m |
| 2026-07-21 | AFR359P | - | Jul 21, 03:40 UTC | Jul 21, 10:35 UTC | 6h 55m |
| 2026-07-20 | AFR358P | CDG → YYZ | Jul 20, 17:15 UTC | Jul 21, 00:30 UTC | 7h 14m |
| 2026-07-20 | AFR353 | YQB → CDG | Jul 20, 05:20 UTC | Jul 20, 11:25 UTC | 6h 5m |
| 2026-07-19 | AFR352 | CDG → YQB | Jul 19, 19:50 UTC | Jul 20, 02:15 UTC | 6h 25m |
| 2026-07-18 | AFR763 | PTP → CDG | Jul 18, 14:25 UTC | Jul 19, 09:05 UTC | 18h 40m |
| 2026-07-18 | AFR651 | - | Jul 18, 01:20 UTC | Jul 18, 10:35 UTC | 9h 16m |
| 2026-07-17 | AFR650 | CDG → CUN | Jul 17, 12:30 UTC | Jul 17, 22:10 UTC | 9h 40m |
| 2026-07-16 | AFR809 | - | Jul 16, 14:29 UTC | Jul 17, 08:30 UTC | 18h 0m |
| 2026-07-15 | AFR647 | - | Jul 15, 12:20 UTC | Jul 15, 16:20 UTC | 4h 0m |
| 2026-07-14 | AFR647 | - | Jul 14, 17:20 UTC | Jul 15, 16:20 UTC | 22h 59m |
| 2026-07-14 | AFR647 | - | Jul 14, 16:25 UTC | Jul 15, 15:15 UTC | 22h 49m |
| 2026-07-13 | AFR763 | - | Jul 13, 15:20 UTC | Jul 14, 09:30 UTC | 18h 10m |
| 2026-07-13 | AFR763 | - | Jul 13, 14:55 UTC | Jul 14, 09:30 UTC | 18h 35m |
| 2026-07-13 | AFR651 | - | Jul 13, 01:35 UTC | Jul 13, 10:45 UTC | 9h 10m |
| 2026-07-12 | AFR650 | - | Jul 12, 12:45 UTC | Jul 12, 22:15 UTC | 9h 30m |
| 2026-07-11 | AFR771 | - | Jul 11, 09:20 UTC | Jul 12, 03:40 UTC | 18h 20m |
| 2026-07-11 | AFR771 | - | Jul 11, 09:10 UTC | Jul 12, 03:40 UTC | 18h 30m |
| 2026-07-11 | AFR841 | - | Jul 11, 01:40 UTC | Jul 11, 03:20 UTC | 1h 40m |
| 2026-07-10 | AFR842 | - | Jul 10, 08:15 UTC | Jul 10, 09:40 UTC | 1h 25m |
| 2026-07-10 | AFR669 | - | Jul 10, 00:30 UTC | Jul 10, 03:30 UTC | 3h 0m |
| 2026-07-08 | AFR668 | - | Jul 8, 22:00 UTC | Jul 9, 00:40 UTC | 2h 40m |
| 2026-07-08 | AFR647 | - | Jul 8, 12:20 UTC | Jul 8, 16:10 UTC | 3h 50m |
| 2026-07-07 | AFR647 | - | Jul 7, 19:20 UTC | Jul 8, 16:10 UTC | 20h 50m |
| 2026-07-07 | AFR647 | - | Jul 7, 17:20 UTC | Jul 8, 16:10 UTC | 22h 50m |
| 2026-07-07 | AFR652 | - | Jul 7, 16:05 UTC | Jul 8, 15:15 UTC | 23h 10m |
| 2026-07-06 | AFR763 | - | Jul 6, 15:00 UTC | Jul 7, 09:05 UTC | 18h 5m |
| 2026-07-05 | AFR359P | - | Jul 5, 03:45 UTC | Jul 5, 10:25 UTC | 6h 40m |
| 2026-07-04 | AFR358P | - | Jul 4, 17:05 UTC | Jul 5, 00:45 UTC | 7h 40m |
| 2026-07-04 | AFR505 | - | Jul 4, 02:25 UTC | Jul 4, 13:55 UTC | 11h 30m |
| 2026-07-03 | AFR504 | - | Jul 3, 11:10 UTC | Jul 3, 22:35 UTC | 11h 25m |
| 2026-07-03 | AFR669 | - | Jul 3, 00:15 UTC | Jul 3, 03:20 UTC | 3h 5m |
| 2026-07-02 | AFR669 | - | Jul 2, 01:40 UTC | Jul 3, 01:15 UTC | 23h 35m |
| 2026-07-01 | AFR668 | - | Jul 1, 22:10 UTC | Jul 2, 01:40 UTC | 3h 30m |
| 2026-07-01 | AFR647 | - | Jul 1, 12:30 UTC | Jul 1, 16:05 UTC | 3h 35m |
| 2026-06-30 | AFR647 | - | Jun 30, 19:35 UTC | Jul 1, 16:05 UTC | 20h 30m |
| 2026-06-30 | AFR652 | - | Jun 30, 16:10 UTC | Jul 1, 15:15 UTC | 23h 5m |
| 2026-06-30 | AFR353 | - | Jun 30, 05:10 UTC | Jun 30, 11:00 UTC | 5h 50m |
| 2026-06-29 | AFR352 | - | Jun 29, 19:39 UTC | Jun 30, 02:15 UTC | 6h 36m |
| 2026-06-29 | AFR647 | - | Jun 29, 13:44 UTC | Jun 29, 16:39 UTC | 2h 55m |
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-GSQN page for operator, model, and routing details .