sensors Mode-S transponder
76CCCE
ICAO 24-bit transponder address · allocated to Singapore
Currently assigned to 9V-SFN · BOEING 747-400
- Hex
- 76CCCE
- Octal
- 35546316
- Decimal
- 7,785,678
- Country
- SG
- Tail
- 9V-SFN
- Type
- B744
- Flights observed
- 214
- Distinct callsigns
- 20
- Country
- SG
- Last broadcast
- 10d ago
Last known position
Country allocation
The ICAO 24-bit address 76CCCE falls within the block assigned to Singapore (SG) by ICAO Annex 10, Volume III. Every aircraft registered in Singapore 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 |
|---|---|---|---|
| SIA7352 | - | 28 | 2026-07-02 |
| SIA7980 | Singapore Airlines | 15 | 2026-06-20 |
| SIA7297 | Singapore Airlines | 12 | 2026-06-24 |
| SIA7298 | - | 11 | 2026-06-23 |
| SIA7952 | - | 9 | 2026-06-25 |
| SIA7353 | - | 9 | 2026-07-03 |
| SIA7988 | Singapore Airlines | 8 | 2026-06-17 |
| SIA7977 | - | 8 | 2026-06-21 |
| SIA7351 | Singapore Airlines | 8 | 2026-05-07 |
| SIA7973 | Singapore Airlines | 7 | 2026-06-10 |
| SIA7951 | - | 7 | 2026-06-27 |
| SIA7874 | Singapore Airlines | 6 | 2026-06-22 |
| SIA7327 | - | 6 | 2026-06-18 |
| SIA7921 | Singapore Airlines | 5 | 2026-06-04 |
| SIA7873 | Singapore Airlines | 5 | 2026-06-22 |
| SIA7976 | Singapore Airlines | 4 | 2026-06-08 |
| SIA7974 | Singapore Airlines | 4 | 2026-05-25 |
| SIA7922 | Singapore Airlines | 4 | 2026-06-02 |
| SIA7868 | Singapore Airlines | 4 | 2026-05-30 |
| SIA7862 | - | 4 | 2026-07-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-03 | SIA7353 | - | Jul 3, 08:55 UTC | Jul 3, 13:00 UTC | 4h 5m |
| 2026-07-03 | SIA7353 | - | Jul 3, 06:35 UTC | Jul 3, 06:50 UTC | 15m |
| 2026-07-02 | SIA7353 | - | Jul 2, 21:50 UTC | Jul 3, 05:10 UTC | 7h 20m |
| 2026-07-02 | SIA7352 | - | Jul 2, 18:20 UTC | Jul 2, 19:10 UTC | 50m |
| 2026-07-02 | SIA7352 | - | Jul 2, 06:35 UTC | Jul 2, 14:50 UTC | 8h 15m |
| 2026-07-01 | SIA7352 | - | Jul 1, 22:50 UTC | Jul 2, 02:25 UTC | 3h 35m |
| 2026-07-01 | SIA7861 | HKG → SIN | Jul 1, 14:25 UTC | Jul 1, 14:50 UTC | 25m |
| 2026-07-01 | SIA7861 | HKG → SIN | Jul 1, 11:50 UTC | Jul 1, 12:05 UTC | 15m |
| 2026-07-01 | SIA7862 | - | Jul 1, 07:55 UTC | Jul 1, 08:20 UTC | 25m |
| 2026-07-01 | SIA7862 | - | Jul 1, 04:55 UTC | Jul 1, 05:25 UTC | 30m |
| 2026-06-30 | SIA7847 | - | Jun 30, 11:00 UTC | Jun 30, 23:55 UTC | 12h 55m |
| 2026-06-29 | SIA7333 | LHR → SIN | Jun 29, 12:39 UTC | Jun 29, 20:19 UTC | 7h 40m |
| 2026-06-29 | SIA7343 | - | Jun 29, 05:54 UTC | Jun 29, 08:04 UTC | 2h 10m |
| 2026-06-28 | SIA7344 | - | Jun 28, 17:25 UTC | Jun 28, 17:39 UTC | 15m |
| 2026-06-28 | SIA7344 | - | Jun 28, 03:55 UTC | Jun 28, 14:09 UTC | 10h 15m |
| 2026-06-27 | SIA7895 | - | Jun 27, 11:04 UTC | Jun 28, 00:59 UTC | 13h 55m |
| 2026-06-27 | SIA7951 | - | Jun 27, 03:44 UTC | Jun 27, 07:34 UTC | 3h 50m |
| 2026-06-26 | SIA7951 | - | Jun 26, 16:44 UTC | Jun 27, 01:00 UTC | 8h 15m |
| 2026-06-26 | SIA7951 | DFW → BRU | Jun 26, 03:45 UTC | Jun 26, 12:14 UTC | 8h 30m |
| 2026-06-25 | SIA7952 | ANC → DFW | Jun 25, 18:29 UTC | Jun 26, 00:10 UTC | 5h 40m |
| 2026-06-25 | SIA7952 | HKG → ANC | Jun 25, 07:25 UTC | Jun 25, 16:55 UTC | 9h 30m |
| 2026-06-25 | SIA7952 | - | Jun 25, 03:40 UTC | Jun 25, 04:04 UTC | 25m |
| 2026-06-25 | SIA7952 | - | Jun 25, 00:40 UTC | Jun 25, 01:04 UTC | 25m |
| 2026-06-24 | SIA7297 | MEL → SIN | Jun 24, 11:09 UTC | Jun 24, 12:20 UTC | 1h 10m |
| 2026-06-24 | SIA7297 | MEL → SIN | Jun 24, 04:05 UTC | Jun 24, 07:30 UTC | 3h 25m |
| 2026-06-23 | SIA7298 | SYD → AKL | Jun 23, 11:35 UTC | Jun 23, 13:59 UTC | 2h 25m |
| 2026-06-23 | SIA7298 | - | Jun 23, 02:15 UTC | Jun 23, 08:45 UTC | 6h 30m |
| 2026-06-22 | SIA7873 | HKG → SIN | Jun 22, 14:49 UTC | Jun 22, 15:24 UTC | 35m |
| 2026-06-22 | SIA7873 | HKG → SIN | Jun 22, 12:10 UTC | Jun 22, 12:25 UTC | 15m |
| 2026-06-22 | SIA7874 | SIN → HKG | Jun 22, 08:50 UTC | Jun 22, 09:14 UTC | 25m |
| 2026-06-22 | SIA7874 | SIN → HKG | Jun 22, 05:44 UTC | Jun 22, 06:19 UTC | 35m |
| 2026-06-21 | SIA7977 | - | Jun 21, 11:59 UTC | Jun 22, 02:45 UTC | 14h 45m |
| 2026-06-20 | SIA7977 | DFW → BRU | Jun 20, 23:45 UTC | Jun 21, 08:15 UTC | 8h 30m |
| 2026-06-20 | SIA7980 | ANC → DFW | Jun 20, 14:39 UTC | Jun 20, 20:05 UTC | 5h 25m |
| 2026-06-20 | SIA7980 | ANC → DFW | Jun 20, 03:04 UTC | Jun 20, 13:04 UTC | 10h 0m |
| 2026-06-19 | SIA7980 | ANC → DFW | Jun 19, 20:34 UTC | Jun 19, 23:39 UTC | 3h 5m |
| 2026-06-18 | SIA7327 | - | Jun 18, 19:55 UTC | Jun 19, 10:29 UTC | 14h 34m |
| 2026-06-18 | SIA7327 | - | Jun 18, 06:00 UTC | Jun 18, 16:05 UTC | 10h 5m |
| 2026-06-17 | SIA7988 | ANC → LAX | Jun 17, 22:10 UTC | Jun 18, 02:40 UTC | 4h 30m |
| 2026-06-17 | SIA7988 | ANC → LAX | Jun 17, 11:00 UTC | Jun 17, 20:30 UTC | 9h 30m |
| 2026-06-17 | SIA7988 | ANC → LAX | Jun 17, 08:05 UTC | Jun 17, 08:20 UTC | 15m |
| 2026-06-17 | SIA7988 | ANC → LAX | Jun 17, 04:55 UTC | Jun 17, 05:20 UTC | 25m |
| 2026-06-17 | SIA7823 | CAN → SIN | Jun 17, 01:45 UTC | Jun 17, 02:05 UTC | 20m |
| 2026-06-16 | SIA7824 | SIN → SIN | Jun 16, 17:59 UTC | Jun 16, 18:15 UTC | 15m |
| 2026-06-16 | SIA7824 | SIN → SIN | Jun 16, 14:55 UTC | Jun 16, 15:20 UTC | 25m |
| 2026-06-15 | SIA7873 | HKG → SIN | Jun 15, 14:40 UTC | Jun 15, 15:00 UTC | 20m |
| 2026-06-15 | SIA7873 | HKG → SIN | Jun 15, 12:10 UTC | Jun 15, 12:19 UTC | 10m |
| 2026-06-15 | SIA7874 | SIN → HKG | Jun 15, 08:15 UTC | Jun 15, 08:40 UTC | 25m |
| 2026-06-15 | SIA7874 | SIN → HKG | Jun 15, 05:15 UTC | Jun 15, 05:40 UTC | 25m |
| 2026-06-14 | SIA7293 | MEL → SIN | Jun 14, 13:05 UTC | Jun 14, 14:15 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 9V-SFN page for operator, model, and routing details .