sensors Mode-S transponder
76CD46
ICAO 24-bit transponder address · allocated to Singapore
Currently assigned to 9V-SJF · AIRBUS A-350-900
- Hex
- 76CD46
- Octal
- 35546506
- Decimal
- 7,785,798
- Country
- SG
- Tail
- 9V-SJF
- Type
- A359
- Flights observed
- 162
- Distinct callsigns
- 20
- Country
- SG
- Last broadcast
- Jul 26, 19:40 UTC
Current position
Country allocation
The ICAO 24-bit address 76CD46 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 |
|---|---|---|---|
| SIA31 | Singapore Airlines | 12 | 2026-07-25 |
| SIA27 | Singapore Airlines | 12 | 2026-07-19 |
| SIA32 | Singapore Airlines | 11 | 2026-07-25 |
| SIA28 | Singapore Airlines | 10 | 2026-07-19 |
| SIA38 | Singapore Airlines | 8 | 2026-07-26 |
| SIA351 | Singapore Airlines | 7 | 2026-07-22 |
| SIA958 | - | 6 | 2026-07-10 |
| SIA37 | - | 6 | 2026-07-11 |
| SIA352 | - | 6 | 2026-07-21 |
| SIA36 | Singapore Airlines | 4 | 2026-06-12 |
| SIA35 | Singapore Airlines | 4 | 2026-06-13 |
| SIA298 | - | 4 | 2026-07-17 |
| SIA959 | - | 3 | 2026-07-10 |
| SIA338 | Singapore Airlines | 3 | 2026-06-07 |
| SIA337 | Singapore Airlines | 3 | 2026-06-07 |
| SIA328 | - | 3 | 2026-07-08 |
| SIA327 | - | 3 | 2026-07-09 |
| SIA247 | - | 3 | 2026-06-22 |
| SIA962 | - | 2 | 2026-06-24 |
| SIA952 | Singapore Airlines | 2 | 2026-06-07 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | SIA38 | SIN → LAX | Jul 26, 16:10 UTC | Jul 26, 19:40 UTC | 3h 30m |
| 2026-07-25 | SIA31 | SFO → SIN | Jul 25, 19:15 UTC | Jul 26, 08:55 UTC | 13h 41m |
| 2026-07-25 | SIA32 | SIN → SFO | Jul 25, 03:55 UTC | Jul 25, 16:50 UTC | 12h 55m |
| 2026-07-25 | SIA32 | SIN → SFO | Jul 25, 01:25 UTC | Jul 25, 01:35 UTC | 10m |
| 2026-07-24 | SIA365 | FCO → SIN | Jul 24, 10:15 UTC | Jul 24, 21:40 UTC | 11h 25m |
| 2026-07-23 | SIA366 | SIN → FCO | Jul 23, 18:00 UTC | Jul 24, 06:15 UTC | 12h 15m |
| 2026-07-22 | SIA351 | CPH → SIN | Jul 22, 11:10 UTC | Jul 22, 22:00 UTC | 10h 50m |
| 2026-07-21 | SIA352 | - | Jul 21, 16:35 UTC | Jul 22, 05:10 UTC | 12h 35m |
| 2026-07-20 | SIA125 | KUL → SIN | Jul 20, 13:25 UTC | Jul 20, 14:05 UTC | 40m |
| 2026-07-20 | SIA126 | SIN → KUL | Jul 20, 11:25 UTC | Jul 20, 12:05 UTC | 40m |
| 2026-07-19 | SIA27 | SEA → SIN | Jul 19, 18:25 UTC | Jul 20, 09:50 UTC | 15h 25m |
| 2026-07-19 | SIA28 | SIN → SEA | Jul 19, 04:35 UTC | Jul 19, 16:10 UTC | 11h 35m |
| 2026-07-18 | SIA351 | CPH → SIN | Jul 18, 10:10 UTC | Jul 18, 22:05 UTC | 11h 55m |
| 2026-07-17 | SIA352 | - | Jul 17, 16:34 UTC | Jul 18, 04:40 UTC | 12h 6m |
| 2026-07-17 | SIA298 | - | Jul 17, 01:15 UTC | Jul 17, 02:10 UTC | 55m |
| 2026-07-16 | SIA298 | - | Jul 16, 23:10 UTC | Jul 16, 23:25 UTC | 15m |
| 2026-07-16 | SIA297 | - | Jul 16, 12:14 UTC | Jul 16, 21:40 UTC | 9h 25m |
| 2026-07-16 | SIA298 | - | Jul 16, 01:25 UTC | Jul 16, 02:15 UTC | 50m |
| 2026-07-15 | SIA298 | - | Jul 15, 23:30 UTC | Jul 15, 23:45 UTC | 15m |
| 2026-07-15 | SIA297 | - | Jul 15, 18:40 UTC | Jul 15, 21:50 UTC | 3h 10m |
| 2026-07-14 | SIA313 | - | Jul 14, 12:40 UTC | Jul 15, 01:05 UTC | 12h 24m |
| 2026-07-13 | SIA314 | - | Jul 13, 18:55 UTC | Jul 14, 08:20 UTC | 13h 25m |
| 2026-07-12 | SIA31 | - | Jul 12, 19:30 UTC | Jul 13, 09:35 UTC | 14h 5m |
| 2026-07-12 | SIA32 | - | Jul 12, 03:10 UTC | Jul 12, 16:55 UTC | 13h 45m |
| 2026-07-11 | SIA37 | - | Jul 11, 07:25 UTC | Jul 11, 22:01 UTC | 14h 35m |
| 2026-07-10 | SIA38 | - | Jul 10, 14:45 UTC | Jul 11, 05:10 UTC | 14h 25m |
| 2026-07-10 | SIA959 | - | Jul 10, 08:05 UTC | Jul 10, 09:35 UTC | 1h 30m |
| 2026-07-10 | SIA958 | - | Jul 10, 05:00 UTC | Jul 10, 06:25 UTC | 1h 25m |
| 2026-07-09 | SIA327 | - | Jul 9, 11:00 UTC | Jul 9, 22:35 UTC | 11h 35m |
| 2026-07-08 | SIA328 | - | Jul 8, 16:25 UTC | Jul 9, 04:20 UTC | 11h 55m |
| 2026-07-07 | SIA351 | - | Jul 7, 11:35 UTC | Jul 7, 22:05 UTC | 10h 30m |
| 2026-07-07 | SIA351 | - | Jul 7, 10:15 UTC | Jul 7, 11:25 UTC | 1h 10m |
| 2026-07-06 | SIA352 | SIN → CPH | Jul 6, 16:30 UTC | Jul 7, 05:10 UTC | 12h 40m |
| 2026-07-06 | SIA31 | - | Jul 6, 10:15 UTC | Jul 6, 10:25 UTC | 10m |
| 2026-07-05 | SIA31 | - | Jul 5, 19:10 UTC | Jul 6, 08:45 UTC | 13h 35m |
| 2026-07-05 | SIA32 | - | Jul 5, 04:30 UTC | Jul 5, 16:15 UTC | 11h 45m |
| 2026-07-05 | SIA32 | - | Jul 5, 01:30 UTC | Jul 5, 01:40 UTC | 10m |
| 2026-07-04 | SIA37 | LAX → SIN | Jul 4, 07:15 UTC | Jul 4, 21:30 UTC | 14h 15m |
| 2026-07-03 | SIA38 | SIN → LAX | Jul 3, 16:10 UTC | Jul 4, 04:20 UTC | 12h 10m |
| 2026-07-03 | SIA38 | SIN → LAX | Jul 3, 13:15 UTC | Jul 3, 13:25 UTC | 10m |
| 2026-07-03 | SIA31 | - | Jul 3, 10:50 UTC | Jul 3, 11:00 UTC | 10m |
| 2026-07-02 | SIA31 | - | Jul 2, 19:30 UTC | Jul 3, 09:20 UTC | 13h 50m |
| 2026-07-02 | SIA32 | - | Jul 2, 04:20 UTC | Jul 2, 15:50 UTC | 11h 30m |
| 2026-07-01 | SIA391 | - | Jul 1, 10:25 UTC | Jul 1, 18:25 UTC | 8h 0m |
| 2026-07-01 | SIA392 | - | Jul 1, 05:00 UTC | Jul 1, 05:20 UTC | 20m |
| 2026-06-30 | SIA392 | - | Jun 30, 18:35 UTC | Jul 1, 04:20 UTC | 9h 45m |
| 2026-06-30 | SIA242 | - | Jun 30, 08:20 UTC | Jun 30, 08:55 UTC | 35m |
| 2026-06-29 | SIA241 | - | Jun 29, 23:39 UTC | Jun 30, 06:35 UTC | 6h 56m |
| 2026-06-29 | SIA323 | - | Jun 29, 09:20 UTC | Jun 29, 21:19 UTC | 12h 0m |
| 2026-06-28 | SIA324 | - | Jun 28, 16:25 UTC | Jun 29, 05:20 UTC | 12h 55m |
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-SJF page for operator, model, and routing details .