sensors Mode-S transponder
394A00
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQA · BOEING 777-300ER
- Hex
- 394A00
- Octal
- 16245000
- Decimal
- 3,754,496
- Country
- FR
- Tail
- F-GSQA
- Type
- B77W
- Flights observed
- 93
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address 394A00 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 |
|---|---|---|---|
| AFR84E | Air France | 9 | 2026-05-29 |
| AFR83K | Air France | 9 | 2026-05-29 |
| AFR031 | Air France | 8 | 2026-05-20 |
| AFR702 | Air France | 6 | 2026-05-23 |
| AFR51N | Air France | 6 | 2026-05-28 |
| AFR454 | Air France | 6 | 2026-05-16 |
| AFR030 | Air France | 6 | 2026-05-20 |
| AFR453 | Air France | 5 | 2026-05-17 |
| AFR50N | Air France | 3 | 2026-05-28 |
| AFR332 | Air France | 3 | 2026-04-17 |
| AFR331E | - | 3 | 2026-04-18 |
| AFR2N | Air France | 3 | 2026-05-25 |
| AFR1U | Air France | 3 | 2026-05-25 |
| AFR004 | - | 3 | 2026-05-19 |
| AFR003 | - | 3 | 2026-04-15 |
| AFR007 | - | 2 | 2026-05-23 |
| AFR8U | Air France | 1 | 2026-04-20 |
| AFR8F | - | 1 | 2026-05-22 |
| AFR836 | Air France | 1 | 2026-04-26 |
| AFR706 | Air France | 1 | 2026-05-27 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | AFR83K | SFO → CDG | May 29, 23:10 UTC | May 29, 23:45 UTC | 35m |
| 2026-05-29 | AFR84E | CDG → SFO | May 29, 09:35 UTC | May 29, 20:15 UTC | 10h 40m |
| 2026-05-28 | AFR51N | IAD → CDG | May 28, 22:40 UTC | May 29, 05:40 UTC | 7h 0m |
| 2026-05-28 | AFR50N | CDG → IAD | May 28, 12:05 UTC | May 28, 19:55 UTC | 7h 50m |
| 2026-05-27 | AFR706 | ABJ → DSS | May 27, 17:35 UTC | May 28, 08:55 UTC | 15h 20m |
| 2026-05-26 | AFR83K | SFO → CDG | May 26, 22:54 UTC | May 27, 08:55 UTC | 10h 1m |
| 2026-05-26 | AFR84E | CDG → SFO | May 26, 08:50 UTC | May 26, 19:55 UTC | 11h 5m |
| 2026-05-25 | AFR1U | JFK → CDG | May 25, 20:59 UTC | May 26, 03:30 UTC | 6h 30m |
| 2026-05-25 | AFR2N | CDG → JFK | May 25, 06:55 UTC | May 25, 14:10 UTC | 7h 15m |
| 2026-05-24 | AFR1U | JFK → CDG | May 24, 21:05 UTC | May 25, 03:40 UTC | 6h 35m |
| 2026-05-24 | AFR2N | CDG → JFK | May 24, 07:15 UTC | May 24, 14:45 UTC | 7h 30m |
| 2026-05-23 | AFR702 | CDG → ABJ | May 23, 12:40 UTC | May 24, 03:45 UTC | 15h 5m |
| 2026-05-23 | AFR007 | - | May 23, 02:05 UTC | May 23, 08:15 UTC | 6h 9m |
| 2026-05-22 | AFR8F | - | May 22, 15:10 UTC | May 22, 22:30 UTC | 7h 20m |
| 2026-05-21 | AFR23G | LAX → CDG | May 21, 22:30 UTC | May 22, 08:20 UTC | 9h 50m |
| 2026-05-21 | AFR22J | CDG → LAX | May 21, 08:55 UTC | May 21, 19:30 UTC | 10h 35m |
| 2026-05-20 | AFR031 | ATL → CDG | May 20, 20:50 UTC | May 21, 04:45 UTC | 7h 55m |
| 2026-05-20 | AFR030 | CDG → ATL | May 20, 09:55 UTC | May 20, 18:35 UTC | 8h 40m |
| 2026-05-20 | AFR3T | JFK → CDG | May 20, 00:20 UTC | May 20, 06:55 UTC | 6h 36m |
| 2026-05-19 | AFR004 | - | May 19, 08:55 UTC | May 19, 16:15 UTC | 7h 20m |
| 2026-05-18 | AFR031 | ATL → CDG | May 18, 23:55 UTC | May 19, 04:45 UTC | 4h 50m |
| 2026-05-18 | AFR031 | ATL → CDG | May 18, 20:50 UTC | May 18, 23:50 UTC | 3h 0m |
| 2026-05-18 | AFR030 | CDG → ATL | May 18, 09:10 UTC | May 18, 17:50 UTC | 8h 40m |
| 2026-05-17 | AFR453 | GRU → CDG | May 17, 17:40 UTC | May 18, 04:30 UTC | 10h 50m |
| 2026-05-16 | AFR454 | CDG → GRU | May 16, 21:40 UTC | May 17, 09:05 UTC | 11h 25m |
| 2026-05-15 | AFR021 | LAX → CDG | May 15, 21:20 UTC | May 16, 07:11 UTC | 9h 51m |
| 2026-05-15 | AFR020 | CDG → LAX | May 15, 07:20 UTC | May 15, 18:25 UTC | 11h 4m |
| 2026-05-14 | AFR1U | JFK → CDG | May 14, 20:55 UTC | May 15, 03:20 UTC | 6h 25m |
| 2026-05-14 | AFR2N | CDG → JFK | May 14, 06:50 UTC | May 14, 14:20 UTC | 7h 30m |
| 2026-05-13 | AFR181 | SIN → CDG | May 13, 03:20 UTC | May 13, 16:35 UTC | 13h 15m |
| 2026-05-12 | AFR182 | CDG → SIN | May 12, 11:45 UTC | May 12, 23:40 UTC | 11h 55m |
| 2026-05-11 | AFR453 | GRU → CDG | May 11, 18:00 UTC | May 12, 04:15 UTC | 10h 15m |
| 2026-05-10 | AFR454 | CDG → GRU | May 10, 21:49 UTC | May 11, 09:10 UTC | 11h 20m |
| 2026-05-10 | AFR187 | CDG → LAS | May 10, 00:05 UTC | May 10, 13:40 UTC | 13h 35m |
| 2026-05-09 | AFR186 | LAS → CDG | May 9, 07:55 UTC | May 9, 20:34 UTC | 12h 40m |
| 2026-05-07 | AFR702 | CDG → ABJ | May 7, 13:05 UTC | May 8, 04:29 UTC | 15h 25m |
| 2026-05-06 | AFR453 | GRU → CDG | May 6, 17:55 UTC | May 7, 04:25 UTC | 10h 30m |
| 2026-05-06 | AFR454 | CDG → GRU | May 6, 06:35 UTC | May 6, 09:10 UTC | 2h 35m |
| 2026-05-05 | AFR454 | CDG → GRU | May 5, 21:55 UTC | May 6, 06:30 UTC | 8h 35m |
| 2026-05-04 | AFR51N | IAD → CDG | May 4, 22:30 UTC | May 5, 05:35 UTC | 7h 5m |
| 2026-05-04 | AFR50N | CDG → IAD | May 4, 12:00 UTC | May 4, 19:50 UTC | 7h 51m |
| 2026-05-03 | AFR702 | CDG → ABJ | May 3, 12:20 UTC | May 4, 03:30 UTC | 15h 10m |
| 2026-05-02 | AFR83K | SFO → CDG | May 2, 23:10 UTC | May 3, 09:15 UTC | 10h 4m |
| 2026-05-02 | AFR84E | CDG → SFO | May 2, 09:35 UTC | May 2, 20:30 UTC | 10h 55m |
| 2026-04-30 | AFR031 | ATL → CDG | Apr 30, 20:45 UTC | May 1, 04:55 UTC | 8h 10m |
| 2026-04-30 | AFR030 | CDG → ATL | Apr 30, 08:55 UTC | Apr 30, 17:25 UTC | 8h 30m |
| 2026-04-29 | AFR453 | GRU → CDG | Apr 29, 18:20 UTC | Apr 30, 05:00 UTC | 10h 39m |
| 2026-04-28 | AFR454 | CDG → GRU | Apr 28, 21:55 UTC | Apr 29, 09:15 UTC | 11h 21m |
| 2026-04-27 | AFR83K | SFO → CDG | Apr 27, 22:40 UTC | Apr 28, 08:50 UTC | 10h 10m |
| 2026-04-27 | AFR84E | CDG → SFO | Apr 27, 09:05 UTC | Apr 27, 19:45 UTC | 10h 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-GSQA page for operator, model, and routing details .