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