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