sensors Mode-S transponder
394A08
ICAO 24-bit transponder address · allocated to France
Currently assigned to F-GSQI · BOEING 777-300ER
- Hex
- 394A08
- Octal
- 16245010
- Decimal
- 3,754,504
- Country
- FR
- Tail
- F-GSQI
- Type
- B77W
- Flights observed
- 184
- Distinct callsigns
- 20
- Country
- FR
- Last broadcast
- Jul 26, 20:10 UTC
Last known position
Country allocation
The ICAO 24-bit address 394A08 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 |
|---|---|---|---|
| AFR51N | - | 14 | 2026-06-21 |
| AFR50N | Air France | 14 | 2026-06-21 |
| AFR454 | Air France | 12 | 2026-07-23 |
| AFR030 | - | 11 | 2026-07-18 |
| AFR5U | - | 10 | 2026-07-08 |
| AFR453 | Air France | 10 | 2026-07-24 |
| AFR031 | Air France | 10 | 2026-07-18 |
| AFR84E | Air France | 9 | 2026-07-26 |
| AFR83K | - | 9 | 2026-07-10 |
| AFR257 | Air France | 8 | 2026-06-23 |
| AFR256 | Air France | 7 | 2026-06-22 |
| AFR006 | - | 7 | 2026-07-08 |
| AFR092 | Air France | 5 | 2026-06-19 |
| AFR98G | - | 4 | 2026-07-15 |
| AFR099 | - | 4 | 2026-07-15 |
| AFR093 | - | 4 | 2026-06-20 |
| AFR703 | - | 3 | 2026-06-16 |
| AFR702 | - | 3 | 2026-06-28 |
| AFR357E | - | 3 | 2026-07-16 |
| AFR356G | - | 3 | 2026-07-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | AFR84E | CDG → SFO | Jul 26, 09:00 UTC | Jul 26, 19:50 UTC | 10h 50m |
| 2026-07-25 | AFR923 | LBV → CDG | Jul 25, 09:30 UTC | Jul 26, 03:25 UTC | 17h 55m |
| 2026-07-24 | AFR453 | GRU → CDG | Jul 24, 18:00 UTC | Jul 25, 04:40 UTC | 10h 40m |
| 2026-07-23 | AFR454 | CDG → GRU | Jul 23, 22:20 UTC | Jul 24, 09:45 UTC | 11h 25m |
| 2026-07-23 | AFR42DT | NCE → CDG | Jul 23, 12:40 UTC | Jul 23, 14:00 UTC | 1h 20m |
| 2026-07-23 | AFR61AL | CDG → NCE | Jul 23, 09:25 UTC | Jul 23, 10:35 UTC | 1h 10m |
| 2026-07-23 | AFR829 | COF → COF | Jul 23, 01:40 UTC | Jul 23, 04:45 UTC | 3h 5m |
| 2026-07-22 | AFR828 | CDG → NBO | Jul 22, 17:20 UTC | Jul 22, 17:30 UTC | 10m |
| 2026-07-22 | AFR828 | CDG → NBO | Jul 22, 10:20 UTC | Jul 22, 12:50 UTC | 2h 30m |
| 2026-07-21 | AFR923 | LBV → CDG | Jul 21, 09:25 UTC | Jul 22, 03:35 UTC | 18h 10m |
| 2026-07-20 | AFR453 | - | Jul 20, 17:55 UTC | Jul 21, 04:15 UTC | 10h 19m |
| 2026-07-19 | AFR454 | - | Jul 19, 21:55 UTC | Jul 20, 09:15 UTC | 11h 20m |
| 2026-07-19 | AFR963 | TLV → CDG | Jul 19, 14:15 UTC | Jul 19, 18:30 UTC | 4h 15m |
| 2026-07-19 | AFR966 | CDG → TLV | Jul 19, 07:45 UTC | Jul 19, 11:35 UTC | 3h 50m |
| 2026-07-18 | AFR031 | ATL → CDG | Jul 18, 20:40 UTC | Jul 19, 04:45 UTC | 8h 5m |
| 2026-07-18 | AFR030 | - | Jul 18, 10:00 UTC | Jul 18, 18:00 UTC | 8h 0m |
| 2026-07-18 | AFR030 | - | Jul 18, 09:25 UTC | Jul 18, 09:55 UTC | 30m |
| 2026-07-17 | AFR031 | ATL → CDG | Jul 17, 21:15 UTC | Jul 18, 05:15 UTC | 8h 1m |
| 2026-07-17 | AFR030 | - | Jul 17, 08:54 UTC | Jul 17, 17:20 UTC | 8h 25m |
| 2026-07-16 | AFR357E | YYZ → CDG | Jul 16, 22:19 UTC | Jul 17, 05:20 UTC | 7h 0m |
| 2026-07-16 | AFR356G | - | Jul 16, 12:09 UTC | Jul 16, 19:35 UTC | 7h 25m |
| 2026-07-15 | AFR099 | - | Jul 15, 22:40 UTC | Jul 16, 07:35 UTC | 8h 55m |
| 2026-07-15 | AFR98G | - | Jul 15, 09:45 UTC | Jul 15, 19:50 UTC | 10h 5m |
| 2026-07-14 | AFR345M | - | Jul 14, 23:25 UTC | Jul 15, 05:45 UTC | 6h 20m |
| 2026-07-14 | AFR344 | - | Jul 14, 12:10 UTC | Jul 14, 19:00 UTC | 6h 50m |
| 2026-07-13 | AFR099 | - | Jul 13, 22:40 UTC | Jul 14, 07:50 UTC | 9h 10m |
| 2026-07-13 | AFR98G | - | Jul 13, 10:00 UTC | Jul 13, 20:05 UTC | 10h 5m |
| 2026-07-12 | AFR453 | - | Jul 12, 17:55 UTC | Jul 13, 04:10 UTC | 10h 15m |
| 2026-07-11 | AFR454 | - | Jul 11, 22:10 UTC | Jul 12, 09:55 UTC | 11h 45m |
| 2026-07-10 | AFR83K | - | Jul 10, 23:05 UTC | Jul 11, 09:10 UTC | 10h 5m |
| 2026-07-10 | AFR84E | - | Jul 10, 09:50 UTC | Jul 10, 20:35 UTC | 10h 45m |
| 2026-07-09 | AFR357E | - | Jul 9, 22:30 UTC | Jul 10, 05:10 UTC | 6h 40m |
| 2026-07-09 | AFR356G | - | Jul 9, 12:20 UTC | Jul 9, 20:00 UTC | 7h 40m |
| 2026-07-08 | AFR5U | - | Jul 8, 23:40 UTC | Jul 9, 06:20 UTC | 6h 40m |
| 2026-07-08 | AFR006 | - | Jul 8, 12:55 UTC | Jul 8, 20:00 UTC | 7h 5m |
| 2026-07-08 | AFR377 | - | Jul 8, 01:55 UTC | Jul 8, 09:10 UTC | 7h 15m |
| 2026-07-07 | AFR378E | - | Jul 7, 15:15 UTC | Jul 7, 22:45 UTC | 7h 30m |
| 2026-07-06 | AFR099 | - | Jul 6, 23:45 UTC | Jul 7, 08:45 UTC | 9h 0m |
| 2026-07-06 | AFR98G | - | Jul 6, 11:25 UTC | Jul 6, 21:05 UTC | 9h 40m |
| 2026-07-05 | AFR099 | - | Jul 5, 23:00 UTC | Jul 6, 07:40 UTC | 8h 40m |
| 2026-07-05 | AFR98G | - | Jul 5, 10:00 UTC | Jul 5, 20:00 UTC | 10h 0m |
| 2026-07-04 | AFR453 | GRU → CDG | Jul 4, 18:00 UTC | Jul 5, 04:35 UTC | 10h 35m |
| 2026-07-03 | AFR454 | CDG → GRU | Jul 3, 22:00 UTC | Jul 4, 09:25 UTC | 11h 25m |
| 2026-07-02 | AFR345M | YUL → CDG | Jul 2, 00:25 UTC | Jul 2, 06:20 UTC | 5h 55m |
| 2026-07-01 | AFR344 | - | Jul 1, 13:40 UTC | Jul 1, 21:00 UTC | 7h 20m |
| 2026-06-30 | AFR149 | - | Jun 30, 14:25 UTC | Jul 1, 06:00 UTC | 15h 35m |
| 2026-06-29 | AFR83K | - | Jun 29, 22:39 UTC | Jun 30, 08:40 UTC | 10h 1m |
| 2026-06-29 | AFR84E | CDG → SFO | Jun 29, 09:00 UTC | Jun 29, 19:09 UTC | 10h 10m |
| 2026-06-28 | AFR702 | - | Jun 28, 13:00 UTC | Jun 29, 04:55 UTC | 15h 55m |
| 2026-06-27 | AFR031 | ATL → CDG | Jun 27, 20:44 UTC | Jun 28, 04:25 UTC | 7h 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-GSQI page for operator, model, and routing details .