sensors Mode-S transponder
3F9A92
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to 15+03 · AIRBUS A-319
- Hex
- 3F9A92
- Octal
- 17715222
- Decimal
- 4,168,338
- Country
- DE
- Tail
- 15+03
- Type
- A319
- Flights observed
- 59
- Distinct callsigns
- 8
- Country
- DE
- Last broadcast
- 17h ago
Last known position
Country allocation
The ICAO 24-bit address 3F9A92 falls within the block assigned to Germany (DE) by ICAO Annex 10, Volume III. Every aircraft registered in Germany 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 8 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | OSY11T | WAW → CGN | Jul 17, 07:35 UTC | Jul 17, 09:10 UTC | 1h 35m |
| 2026-07-15 | OSY11F | - | Jul 15, 08:35 UTC | Jul 15, 12:45 UTC | 4h 10m |
| 2026-07-13 | OSY11T | CGN → WAW | Jul 13, 11:25 UTC | Jul 13, 12:55 UTC | 1h 30m |
| 2026-07-06 | OSY11T | BER → CGN | Jul 6, 16:35 UTC | Jul 6, 17:20 UTC | 45m |
| 2026-07-06 | OSY11F | - | Jul 6, 14:05 UTC | Jul 6, 15:30 UTC | 1h 25m |
| 2026-07-06 | OSY11T | BER → GKE | Jul 6, 06:25 UTC | Jul 6, 07:35 UTC | 1h 10m |
| 2026-07-05 | OSY11T | CGN → BER | Jul 5, 13:55 UTC | Jul 5, 15:10 UTC | 1h 15m |
| 2026-07-03 | OSY11T | TBS → CGN | Jul 3, 06:05 UTC | Jul 3, 10:25 UTC | 4h 20m |
| 2026-07-01 | OSY11F | TBS → TBS | Jul 1, 06:05 UTC | Jul 1, 09:00 UTC | 2h 55m |
| 2026-06-29 | OSY11T | - | Jun 29, 11:55 UTC | Jun 29, 12:05 UTC | 10m |
| 2026-06-29 | OSY11T | - | Jun 29, 07:59 UTC | Jun 29, 10:50 UTC | 2h 50m |
| 2026-06-27 | GAF850 | - | Jun 27, 13:30 UTC | Jun 27, 15:14 UTC | 1h 45m |
| 2026-06-26 | GAF850 | - | Jun 26, 16:44 UTC | Jun 27, 15:14 UTC | 22h 30m |
| 2026-06-26 | GAF850 | - | Jun 26, 12:34 UTC | Jun 26, 14:15 UTC | 1h 40m |
| 2026-06-22 | GAF850 | - | Jun 22, 11:30 UTC | Jun 22, 13:35 UTC | 2h 5m |
| 2026-06-19 | OSY11T | - | Jun 19, 16:29 UTC | Jun 19, 18:09 UTC | 1h 40m |
| 2026-06-19 | OSY11T | - | Jun 19, 13:59 UTC | Jun 19, 15:04 UTC | 1h 5m |
| 2026-06-16 | OSY11T | - | Jun 16, 12:35 UTC | Jun 16, 13:40 UTC | 1h 5m |
| 2026-06-15 | OSY11T | CGN → AAL | Jun 15, 10:45 UTC | Jun 15, 11:49 UTC | 1h 5m |
| 2026-06-12 | GAF633 | BER → CGN | Jun 12, 08:30 UTC | Jun 12, 09:20 UTC | 50m |
| 2026-06-12 | GAF633 | CGN → BER | Jun 12, 06:40 UTC | Jun 12, 07:25 UTC | 45m |
| 2026-06-11 | OSY11F | CGN → CGN | Jun 11, 10:05 UTC | Jun 11, 12:40 UTC | 2h 35m |
| 2026-06-07 | OSY11T | FCN → CGN | Jun 7, 09:05 UTC | Jun 7, 09:40 UTC | 35m |
| 2026-06-05 | OSY11T | CGN → FCN | Jun 5, 07:25 UTC | Jun 5, 08:05 UTC | 40m |
| 2026-06-04 | OSY11T | - | Jun 4, 22:10 UTC | Jun 5, 03:55 UTC | 5h 45m |
| 2026-06-03 | OSY11T | - | Jun 3, 15:20 UTC | Jun 3, 16:25 UTC | 1h 5m |
| 2026-06-01 | OSY11F | - | Jun 1, 18:25 UTC | Jun 1, 18:35 UTC | 10m |
| 2026-06-01 | OSY11F | - | Jun 1, 17:05 UTC | Jun 1, 17:25 UTC | 20m |
| 2026-06-01 | OSY11F | - | Jun 1, 13:05 UTC | Jun 1, 14:15 UTC | 1h 10m |
| 2026-05-30 | OSY11T | - | May 30, 09:15 UTC | May 30, 16:05 UTC | 6h 50m |
| 2026-05-27 | OSY11F | CGN → CGN | May 27, 09:00 UTC | May 27, 11:35 UTC | 2h 35m |
| 2026-05-22 | OSY11T | - | May 22, 09:35 UTC | May 22, 11:20 UTC | 1h 44m |
| 2026-05-22 | OSY11T | - | May 22, 07:55 UTC | May 22, 08:30 UTC | 35m |
| 2026-05-20 | OSY11F | - | May 20, 09:10 UTC | May 20, 10:55 UTC | 1h 45m |
| 2026-05-18 | OSY11T | - | May 18, 12:20 UTC | May 18, 13:00 UTC | 40m |
| 2026-05-18 | OSY11T | - | May 18, 09:25 UTC | May 18, 10:55 UTC | 1h 30m |
| 2026-05-12 | OSY11F | CGN → CGN | May 12, 10:05 UTC | May 12, 12:45 UTC | 2h 40m |
| 2026-05-08 | OSY11T | - | May 8, 10:39 UTC | May 8, 11:34 UTC | 55m |
| 2026-05-08 | OSY11T | - | May 8, 08:14 UTC | May 8, 09:30 UTC | 1h 15m |
| 2026-05-06 | OSY11F | - | May 6, 08:01 UTC | May 6, 11:40 UTC | 3h 40m |
| 2026-05-04 | OSY11T | - | May 4, 13:05 UTC | May 4, 14:40 UTC | 1h 35m |
| 2026-05-04 | OSY11T | - | May 4, 10:40 UTC | May 4, 11:45 UTC | 1h 5m |
| 2026-05-01 | GAF851 | - | May 1, 13:45 UTC | May 1, 15:40 UTC | 1h 55m |
| 2026-04-29 | GAF851 | - | Apr 29, 12:30 UTC | Apr 29, 18:55 UTC | 6h 25m |
| 2026-04-26 | GAF851 | - | Apr 26, 09:45 UTC | Apr 26, 11:40 UTC | 1h 55m |
| 2026-04-20 | GAF849 | BER → CGN | Apr 20, 11:35 UTC | Apr 20, 12:20 UTC | 45m |
| 2026-04-20 | GAF849 | CGN → BER | Apr 20, 10:00 UTC | Apr 20, 10:50 UTC | 50m |
| 2026-04-17 | GAF868 | OBF → CGN | Apr 17, 12:05 UTC | Apr 17, 12:50 UTC | 45m |
| 2026-04-17 | GAF868 | CGN → OBF | Apr 17, 08:20 UTC | Apr 17, 09:05 UTC | 45m |
| 2026-04-15 | OSY11F | - | Apr 15, 11:00 UTC | Apr 15, 12:40 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 15+03 page for operator, model, and routing details .