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