sensors Mode-S transponder
3C4CB6
ICAO 24-bit transponder address · allocated to Germany
Currently assigned to D-ACEV · BOMBARDIER BD-700 Global 6000/6500
- Hex
- 3C4CB6
- Octal
- 17046266
- Decimal
- 3,951,798
- Country
- DE
- Tail
- D-ACEV
- Type
- GLEX
- Flights observed
- 39
- Distinct callsigns
- 17
- Country
- DE
- Last broadcast
- 7h ago
Last known position
Country allocation
The ICAO 24-bit address 3C4CB6 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 17 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| IFA6241 | - | 6 | 2026-04-17 |
| IFA6085 | - | 5 | 2026-04-15 |
| IFA6337 | - | 4 | 2026-06-02 |
| IFA6148 | - | 3 | 2026-05-24 |
| IFA6359 | - | 2 | 2026-05-26 |
| IFA6340 | - | 2 | 2026-05-20 |
| IFA6315 | - | 2 | 2026-05-12 |
| IFA6283 | - | 2 | 2026-05-17 |
| IFA6257 | - | 2 | 2026-05-06 |
| IFA6256 | - | 2 | 2026-04-28 |
| IFA6255 | - | 2 | 2026-04-30 |
| IFA6252 | - | 2 | 2026-04-20 |
| IFA6282 | - | 1 | 2026-05-07 |
| IFA6264 | - | 1 | 2026-05-18 |
| IFA6254 | - | 1 | 2026-05-02 |
| IFA6253 | - | 1 | 2026-04-22 |
| IFA224 | - | 1 | 2026-05-13 |
Recent flights last 39
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | IFA6337 | - | Jun 2, 08:25 UTC | Jun 2, 11:50 UTC | 3h 25m |
| 2026-06-01 | IFA6337 | - | Jun 1, 07:10 UTC | Jun 1, 15:55 UTC | 8h 45m |
| 2026-05-29 | IFA6337 | - | May 29, 19:00 UTC | May 30, 03:25 UTC | 8h 25m |
| 2026-05-27 | IFA6337 | - | May 27, 18:05 UTC | May 27, 19:55 UTC | 1h 50m |
| 2026-05-26 | IFA6359 | - | May 26, 12:30 UTC | May 26, 20:40 UTC | 8h 10m |
| 2026-05-26 | IFA6359 | - | May 26, 08:19 UTC | May 26, 10:14 UTC | 1h 55m |
| 2026-05-24 | IFA6148 | - | May 24, 00:20 UTC | May 24, 08:10 UTC | 7h 50m |
| 2026-05-22 | IFA6148 | - | May 22, 17:25 UTC | May 22, 17:45 UTC | 20m |
| 2026-05-22 | IFA6148 | - | May 22, 15:15 UTC | May 22, 15:35 UTC | 20m |
| 2026-05-20 | IFA6340 | MAD → SJU | May 20, 16:50 UTC | May 21, 01:05 UTC | 8h 15m |
| 2026-05-19 | IFA6340 | - | May 19, 11:10 UTC | May 19, 13:05 UTC | 1h 55m |
| 2026-05-18 | IFA6264 | - | May 18, 22:25 UTC | May 19, 07:25 UTC | 9h 0m |
| 2026-05-17 | IFA6283 | - | May 17, 10:40 UTC | May 17, 22:30 UTC | 11h 50m |
| 2026-05-16 | IFA6283 | NUE → NCE | May 16, 10:16 UTC | May 16, 11:21 UTC | 1h 5m |
| 2026-05-13 | IFA224 | - | May 13, 05:20 UTC | May 13, 06:15 UTC | 55m |
| 2026-05-12 | IFA6315 | - | May 12, 20:35 UTC | May 13, 04:10 UTC | 7h 35m |
| 2026-05-11 | IFA6315 | - | May 11, 17:20 UTC | May 11, 18:40 UTC | 1h 20m |
| 2026-05-07 | IFA6282 | - | May 7, 09:00 UTC | May 7, 16:10 UTC | 7h 10m |
| 2026-05-06 | IFA6257 | - | May 6, 06:05 UTC | May 6, 07:15 UTC | 1h 10m |
| 2026-05-04 | IFA6257 | - | May 4, 16:20 UTC | May 4, 16:55 UTC | 35m |
| 2026-05-02 | IFA6254 | - | May 2, 08:15 UTC | May 2, 15:25 UTC | 7h 10m |
| 2026-04-30 | IFA6255 | - | Apr 30, 07:10 UTC | Apr 30, 07:55 UTC | 45m |
| 2026-04-30 | IFA6255 | - | Apr 30, 04:55 UTC | Apr 30, 06:25 UTC | 1h 30m |
| 2026-04-28 | IFA6256 | - | Apr 28, 10:00 UTC | Apr 28, 20:05 UTC | 10h 5m |
| 2026-04-27 | IFA6256 | BER → LTN | Apr 27, 16:15 UTC | Apr 27, 17:45 UTC | 1h 30m |
| 2026-04-22 | IFA6253 | - | Apr 22, 00:35 UTC | Apr 22, 08:20 UTC | 7h 45m |
| 2026-04-20 | IFA6252 | - | Apr 20, 14:35 UTC | Apr 20, 23:20 UTC | 8h 45m |
| 2026-04-20 | IFA6252 | - | Apr 20, 12:15 UTC | Apr 20, 13:15 UTC | 1h 0m |
| 2026-04-17 | IFA6241 | - | Apr 17, 07:20 UTC | Apr 17, 08:55 UTC | 1h 35m |
| 2026-04-17 | IFA6241 | - | Apr 17, 07:00 UTC | Apr 17, 07:15 UTC | 15m |
| 2026-04-17 | IFA6241 | - | Apr 17, 00:05 UTC | Apr 17, 00:50 UTC | 45m |
| 2026-04-16 | IFA6241 | - | Apr 16, 00:00 UTC | Apr 16, 00:55 UTC | 55m |
| 2026-04-15 | IFA6241 | - | Apr 15, 17:05 UTC | Apr 15, 17:15 UTC | 10m |
| 2026-04-15 | IFA6241 | - | Apr 15, 15:05 UTC | Apr 15, 17:00 UTC | 1h 55m |
| 2026-04-15 | IFA6085 | - | Apr 15, 09:40 UTC | Apr 15, 10:25 UTC | 45m |
| 2026-04-15 | IFA6085 | - | Apr 15, 07:01 UTC | Apr 15, 08:40 UTC | 1h 40m |
| 2026-04-15 | IFA6085 | - | Apr 15, 06:10 UTC | Apr 15, 06:55 UTC | 45m |
| 2026-04-15 | IFA6085 | - | Apr 15, 01:05 UTC | Apr 15, 02:40 UTC | 1h 35m |
| 2026-04-12 | IFA6085 | - | Apr 12, 17:15 UTC | Apr 12, 18:25 UTC | 1h 10m |
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 D-ACEV page for operator, model, and routing details .