sensors Mode-S transponder
394A06
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQG · BOEING 777-300ER
- Hex
- 394A06
- Octal
- 16245006
- Decimal
- 3,754,502
- Country
- FR
- Tail
- F-GSQG
- Type
- B77W
- Flights observed
- 159
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 3h ago
Last known position
Country allocation
The ICAO 24-bit address 394A06 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 |
|---|---|---|---|
| AFR453 | - | 18 | 2026-07-10 |
| AFR84E | - | 16 | 2026-07-12 |
| AFR030 | Air France | 15 | 2026-07-05 |
| AFR83K | - | 14 | 2026-07-12 |
| AFR454 | - | 14 | 2026-07-13 |
| AFR51N | - | 12 | 2026-07-01 |
| AFR50N | Air France | 12 | 2026-07-01 |
| AFR031 | - | 12 | 2026-07-05 |
| AFR703 | - | 5 | 2026-06-15 |
| AFR2N | Air France | 5 | 2026-06-05 |
| AFR1U | Air France | 5 | 2026-06-05 |
| AFR966 | - | 3 | 2026-07-11 |
| AFR963 | - | 3 | 2026-07-11 |
| AFR093 | Air France | 3 | 2026-04-15 |
| AFR702 | Air France | 2 | 2026-06-13 |
| AFR092 | Air France | 2 | 2026-04-14 |
| AFR021 | Air France | 2 | 2026-05-19 |
| AFR020 | Air France | 2 | 2026-05-19 |
| AFR8U | Air France | 1 | 2026-05-17 |
| AFR662 | - | 1 | 2026-07-08 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | AFR454 | - | Jul 13, 21:55 UTC | Jul 13, 23:40 UTC | 1h 45m |
| 2026-07-12 | AFR83K | - | Jul 12, 22:40 UTC | Jul 13, 08:40 UTC | 10h 0m |
| 2026-07-12 | AFR84E | - | Jul 12, 09:00 UTC | Jul 12, 20:01 UTC | 11h 0m |
| 2026-07-11 | AFR963 | - | Jul 11, 14:05 UTC | Jul 11, 18:20 UTC | 4h 15m |
| 2026-07-11 | AFR966 | - | Jul 11, 08:10 UTC | Jul 11, 12:15 UTC | 4h 5m |
| 2026-07-10 | AFR453 | - | Jul 10, 17:50 UTC | Jul 11, 04:05 UTC | 10h 15m |
| 2026-07-09 | AFR454 | - | Jul 9, 21:55 UTC | Jul 10, 09:00 UTC | 11h 5m |
| 2026-07-09 | AFR963 | - | Jul 9, 14:30 UTC | Jul 9, 18:40 UTC | 4h 10m |
| 2026-07-09 | AFR966 | - | Jul 9, 08:55 UTC | Jul 9, 12:35 UTC | 3h 40m |
| 2026-07-08 | AFR655 | - | Jul 8, 22:15 UTC | Jul 9, 04:30 UTC | 6h 15m |
| 2026-07-08 | AFR662 | - | Jul 8, 12:10 UTC | Jul 8, 19:15 UTC | 7h 5m |
| 2026-07-07 | AFR453 | GRU → CDG | Jul 7, 21:45 UTC | Jul 8, 08:15 UTC | 10h 30m |
| 2026-07-06 | AFR454 | CDG → GRU | Jul 6, 22:05 UTC | Jul 7, 09:00 UTC | 10h 55m |
| 2026-07-06 | AFR963 | - | Jul 6, 13:55 UTC | Jul 6, 18:10 UTC | 4h 15m |
| 2026-07-06 | AFR966 | - | Jul 6, 08:10 UTC | Jul 6, 11:55 UTC | 3h 45m |
| 2026-07-05 | AFR031 | ATL → CDG | Jul 5, 21:00 UTC | Jul 6, 04:45 UTC | 7h 45m |
| 2026-07-05 | AFR030 | CDG → ATL | Jul 5, 09:00 UTC | Jul 5, 17:35 UTC | 8h 35m |
| 2026-07-04 | AFR031 | ATL → CDG | Jul 4, 20:45 UTC | Jul 5, 04:25 UTC | 7h 40m |
| 2026-07-04 | AFR030 | CDG → ATL | Jul 4, 09:50 UTC | Jul 4, 18:30 UTC | 8h 40m |
| 2026-07-03 | AFR031 | ATL → CDG | Jul 3, 21:20 UTC | Jul 4, 04:55 UTC | 7h 35m |
| 2026-07-03 | AFR030 | CDG → ATL | Jul 3, 09:05 UTC | Jul 3, 17:45 UTC | 8h 40m |
| 2026-07-02 | AFR031 | ATL → CDG | Jul 2, 20:50 UTC | Jul 3, 04:30 UTC | 7h 40m |
| 2026-07-02 | AFR030 | CDG → ATL | Jul 2, 08:55 UTC | Jul 2, 17:40 UTC | 8h 45m |
| 2026-07-01 | AFR51N | - | Jul 1, 22:50 UTC | Jul 2, 05:40 UTC | 6h 50m |
| 2026-07-01 | AFR50N | CDG → IAD | Jul 1, 12:05 UTC | Jul 1, 20:00 UTC | 7h 55m |
| 2026-06-30 | AFR51N | - | Jun 30, 22:35 UTC | Jul 1, 05:40 UTC | 7h 5m |
| 2026-06-30 | AFR50N | CDG → IAD | Jun 30, 12:15 UTC | Jun 30, 20:10 UTC | 7h 55m |
| 2026-06-29 | AFR031 | - | Jun 29, 22:19 UTC | Jun 30, 06:00 UTC | 7h 41m |
| 2026-06-29 | AFR030 | CDG → ATL | Jun 29, 11:20 UTC | Jun 29, 19:49 UTC | 8h 30m |
| 2026-06-28 | AFR51N | IAD → CDG | Jun 28, 22:49 UTC | Jun 29, 05:40 UTC | 6h 50m |
| 2026-06-28 | AFR50N | CDG → IAD | Jun 28, 12:29 UTC | Jun 28, 20:34 UTC | 8h 5m |
| 2026-06-27 | AFR51N | IAD → CDG | Jun 27, 22:40 UTC | Jun 28, 05:20 UTC | 6h 40m |
| 2026-06-27 | AFR50N | CDG → IAD | Jun 27, 11:59 UTC | Jun 27, 19:34 UTC | 7h 35m |
| 2026-06-26 | AFR51N | IAD → CDG | Jun 26, 23:30 UTC | Jun 27, 06:05 UTC | 6h 35m |
| 2026-06-26 | AFR50N | CDG → IAD | Jun 26, 13:10 UTC | Jun 26, 20:59 UTC | 7h 50m |
| 2026-06-22 | AFR83K | - | Jun 22, 22:30 UTC | Jun 23, 08:25 UTC | 9h 55m |
| 2026-06-22 | AFR84E | CDG → SFO | Jun 22, 08:50 UTC | Jun 22, 19:29 UTC | 10h 40m |
| 2026-06-21 | AFR453 | GRU → CDG | Jun 21, 18:00 UTC | Jun 22, 04:44 UTC | 10h 45m |
| 2026-06-20 | AFR454 | CDG → GRU | Jun 20, 21:55 UTC | Jun 21, 08:49 UTC | 10h 55m |
| 2026-06-19 | AFR83K | - | Jun 19, 22:55 UTC | Jun 20, 08:59 UTC | 10h 5m |
| 2026-06-19 | AFR84E | CDG → SFO | Jun 19, 09:04 UTC | Jun 19, 19:34 UTC | 10h 30m |
| 2026-06-18 | AFR453 | GRU → CDG | Jun 18, 18:15 UTC | Jun 19, 04:50 UTC | 10h 34m |
| 2026-06-17 | AFR454 | CDG → GRU | Jun 17, 21:50 UTC | Jun 18, 09:40 UTC | 11h 50m |
| 2026-06-16 | AFR51N | IAD → CDG | Jun 16, 22:45 UTC | Jun 17, 05:20 UTC | 6h 35m |
| 2026-06-16 | AFR50N | CDG → IAD | Jun 16, 12:10 UTC | Jun 16, 19:55 UTC | 7h 46m |
| 2026-06-15 | AFR703 | - | Jun 15, 12:55 UTC | Jun 16, 03:50 UTC | 14h 55m |
| 2026-06-14 | AFR83K | SFO → CDG | Jun 14, 22:35 UTC | Jun 15, 09:00 UTC | 10h 24m |
| 2026-06-14 | AFR84E | CDG → SFO | Jun 14, 09:15 UTC | Jun 14, 19:40 UTC | 10h 25m |
| 2026-06-13 | AFR702 | CDG → ABJ | Jun 13, 12:25 UTC | Jun 14, 03:35 UTC | 15h 10m |
| 2026-06-12 | AFR51N | - | Jun 12, 23:05 UTC | Jun 13, 06:10 UTC | 7h 4m |
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-GSQG page for operator, model, and routing details .