sensors Mode-S transponder
76CCE6
ICAO 24-bit transponder address · allocated to Singapore
Currently assigned to 9V-SGF · AIRBUS A-350-900
- Hex
- 76CCE6
- Octal
- 35546346
- Decimal
- 7,785,702
- Country
- SG
- Tail
- 9V-SGF
- Type
- A359
- Flights observed
- 109
- Distinct callsigns
- 6
- Country
- SG
- Last broadcast
- 4h ago
Current position
Country allocation
The ICAO 24-bit address 76CCE6 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 6 distinct
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-14 | SIA24 | - | Jul 14, 07:50 UTC | Jul 14, 11:25 UTC | 3h 35m |
| 2026-07-14 | SIA24 | - | Jul 14, 04:40 UTC | Jul 14, 04:50 UTC | 10m |
| 2026-07-12 | SIA21 | - | Jul 12, 13:45 UTC | Jul 13, 08:01 UTC | 18h 15m |
| 2026-07-11 | SIA22 | - | Jul 11, 19:20 UTC | Jul 12, 10:30 UTC | 15h 10m |
| 2026-07-11 | SIA22 | - | Jul 11, 16:10 UTC | Jul 11, 16:20 UTC | 10m |
| 2026-07-10 | SIA21 | - | Jul 10, 13:45 UTC | Jul 11, 07:50 UTC | 18h 5m |
| 2026-07-09 | SIA22 | - | Jul 9, 19:05 UTC | Jul 10, 10:00 UTC | 14h 55m |
| 2026-07-08 | SIA23 | - | Jul 8, 02:50 UTC | Jul 8, 21:00 UTC | 18h 10m |
| 2026-07-07 | SIA24 | - | Jul 7, 07:35 UTC | Jul 7, 22:35 UTC | 15h 0m |
| 2026-07-06 | SIA23 | - | Jul 6, 04:45 UTC | Jul 6, 18:00 UTC | 13h 15m |
| 2026-07-05 | SIA24 | - | Jul 5, 07:50 UTC | Jul 5, 22:45 UTC | 14h 55m |
| 2026-07-04 | SIA33 | - | Jul 4, 05:45 UTC | Jul 4, 19:25 UTC | 13h 40m |
| 2026-07-03 | SIA34 | - | Jul 3, 15:20 UTC | Jul 4, 03:00 UTC | 11h 40m |
| 2026-07-02 | SIA33 | - | Jul 2, 05:55 UTC | Jul 2, 19:35 UTC | 13h 40m |
| 2026-07-01 | SIA34 | - | Jul 1, 15:50 UTC | Jul 2, 03:20 UTC | 11h 30m |
| 2026-07-01 | SIA34 | - | Jul 1, 12:45 UTC | Jul 1, 12:55 UTC | 10m |
| 2026-06-30 | SIA33 | - | Jun 30, 05:50 UTC | Jun 30, 20:00 UTC | 14h 10m |
| 2026-06-29 | SIA34 | - | Jun 29, 15:19 UTC | Jun 30, 02:55 UTC | 11h 36m |
| 2026-06-28 | SIA33 | - | Jun 28, 21:04 UTC | Jun 28, 21:14 UTC | 10m |
| 2026-06-28 | SIA33 | - | Jun 28, 05:55 UTC | Jun 28, 19:40 UTC | 13h 45m |
| 2026-06-27 | SIA34 | - | Jun 27, 13:49 UTC | Jun 28, 03:05 UTC | 13h 15m |
| 2026-06-26 | SIA21 | - | Jun 26, 07:39 UTC | Jun 26, 08:20 UTC | 40m |
| 2026-06-25 | SIA21 | - | Jun 25, 14:20 UTC | Jun 26, 04:45 UTC | 14h 25m |
| 2026-06-24 | SIA22 | - | Jun 24, 17:34 UTC | Jun 25, 09:29 UTC | 15h 55m |
| 2026-06-23 | SIA33 | - | Jun 23, 05:45 UTC | Jun 23, 19:59 UTC | 14h 15m |
| 2026-06-22 | SIA34 | - | Jun 22, 15:24 UTC | Jun 23, 02:49 UTC | 11h 25m |
| 2026-06-21 | SIA33 | - | Jun 21, 05:54 UTC | Jun 21, 21:49 UTC | 15h 55m |
| 2026-06-20 | SIA34 | - | Jun 20, 15:14 UTC | Jun 21, 03:05 UTC | 11h 50m |
| 2026-06-19 | SIA21 | - | Jun 19, 13:50 UTC | Jun 20, 07:39 UTC | 17h 50m |
| 2026-06-18 | SIA22 | - | Jun 18, 18:35 UTC | Jun 19, 10:04 UTC | 15h 29m |
| 2026-06-16 | SIA23 | - | Jun 16, 02:45 UTC | Jun 16, 20:20 UTC | 17h 36m |
| 2026-06-15 | SIA24 | - | Jun 15, 07:40 UTC | Jun 15, 22:20 UTC | 14h 40m |
| 2026-06-13 | SIA21 | - | Jun 13, 14:10 UTC | Jun 14, 08:20 UTC | 18h 11m |
| 2026-06-12 | SIA22 | - | Jun 12, 19:00 UTC | Jun 13, 09:35 UTC | 14h 34m |
| 2026-06-10 | SIA23 | JFK → SIN | Jun 10, 02:45 UTC | Jun 10, 20:20 UTC | 17h 35m |
| 2026-06-09 | SIA24 | SIN → JFK | Jun 9, 07:35 UTC | Jun 9, 22:30 UTC | 14h 55m |
| 2026-06-08 | SIA23 | JFK → SIN | Jun 8, 03:15 UTC | Jun 8, 20:40 UTC | 17h 25m |
| 2026-06-07 | SIA24 | SIN → JFK | Jun 7, 07:20 UTC | Jun 7, 22:30 UTC | 15h 10m |
| 2026-06-07 | SIA24 | SIN → JFK | Jun 7, 04:25 UTC | Jun 7, 04:35 UTC | 10m |
| 2026-06-05 | SIA21 | EWR → SIN | Jun 5, 13:55 UTC | Jun 6, 07:45 UTC | 17h 50m |
| 2026-06-04 | SIA22 | SIN → EWR | Jun 4, 19:05 UTC | Jun 5, 09:50 UTC | 14h 45m |
| 2026-06-04 | SIA22 | SIN → EWR | Jun 4, 16:10 UTC | Jun 4, 16:20 UTC | 10m |
| 2026-06-02 | SIA21 | EWR → SIN | Jun 2, 13:50 UTC | Jun 3, 07:35 UTC | 17h 45m |
| 2026-06-01 | SIA22 | SIN → EWR | Jun 1, 18:30 UTC | Jun 2, 10:25 UTC | 15h 55m |
| 2026-06-01 | SIA22 | SIN → EWR | Jun 1, 16:00 UTC | Jun 1, 16:10 UTC | 10m |
| 2026-05-30 | SIA21 | EWR → SIN | May 30, 13:50 UTC | May 31, 00:00 UTC | 10h 10m |
| 2026-05-29 | SIA22 | SIN → EWR | May 29, 18:55 UTC | May 30, 10:15 UTC | 15h 20m |
| 2026-05-27 | SIA23 | JFK → SIN | May 27, 02:39 UTC | May 27, 20:40 UTC | 18h 0m |
| 2026-05-26 | SIA24 | SIN → JFK | May 26, 07:29 UTC | May 26, 22:50 UTC | 15h 20m |
| 2026-05-24 | SIA21 | EWR → SIN | May 24, 13:45 UTC | May 25, 08:35 UTC | 18h 50m |
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-SGF page for operator, model, and routing details .