sensors Mode-S transponder
78149E
ICAO 24-bit transponder address · allocated to China
Currently assigned to B-1168 · BOEING 787-9 Dreamliner
- Hex
- 78149E
- Octal
- 36012236
- Decimal
- 7,869,598
- Country
- CN
- Tail
- B-1168
- Type
- B789
- Flights observed
- 193
- Distinct callsigns
- 20
- Country
- CN
- Last broadcast
- Jul 26, 20:20 UTC
Current position
Country allocation
The ICAO 24-bit address 78149E falls within the block assigned to China (CN) by ICAO Annex 10, Volume III. Every aircraft registered in China 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 |
|---|---|---|---|
| CSN377 | - | 17 | 2026-07-23 |
| CSN649 | China Southern Airlines | 13 | 2026-07-24 |
| CSN378 | China Southern Airlines | 12 | 2026-07-23 |
| CSN3092 | - | 12 | 2026-06-19 |
| CSN650 | China Southern Airlines | 11 | 2026-07-25 |
| CSN320 | - | 11 | 2026-06-22 |
| CSN664 | - | 10 | 2026-07-06 |
| CSN319 | - | 9 | 2026-06-22 |
| CSN6043 | - | 7 | 2026-07-16 |
| CSN3091 | - | 7 | 2026-06-19 |
| CSN8069 | - | 6 | 2026-06-23 |
| CSN677 | China Southern Airlines | 6 | 2026-05-07 |
| CSN663 | - | 6 | 2026-07-05 |
| CSN6044 | - | 6 | 2026-07-17 |
| CSN331 | China Southern Airlines | 5 | 2026-05-25 |
| CSN303 | - | 5 | 2026-06-27 |
| CSN678 | China Southern Airlines | 4 | 2026-05-08 |
| CSN633 | China Southern Airlines | 4 | 2026-07-26 |
| CSN354 | China Southern Airlines | 4 | 2026-06-05 |
| CSN332 | China Southern Airlines | 4 | 2026-05-26 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | CSN633 | CAN → NBO | Jul 26, 19:00 UTC | Jul 26, 20:20 UTC | 1h 20m |
| 2026-07-26 | CSN350 | KUL → CAN | Jul 26, 06:10 UTC | Jul 26, 06:25 UTC | 15m |
| 2026-07-25 | CSN650 | BUD → CAN | Jul 25, 10:45 UTC | Jul 26, 04:25 UTC | 17h 40m |
| 2026-07-24 | CSN649 | CAN → BUD | Jul 24, 18:55 UTC | Jul 25, 04:00 UTC | 9h 5m |
| 2026-07-23 | CSN649 | CAN → BUD | Jul 23, 23:35 UTC | Jul 24, 22:40 UTC | 23h 5m |
| 2026-07-23 | CSN378 | MAD → CAN | Jul 23, 21:35 UTC | Jul 24, 19:05 UTC | 21h 30m |
| 2026-07-23 | CSN378 | MAD → CAN | Jul 23, 19:35 UTC | Jul 24, 19:05 UTC | 23h 30m |
| 2026-07-23 | CSN378 | MAD → CAN | Jul 23, 19:15 UTC | Jul 23, 23:45 UTC | 4h 30m |
| 2026-07-23 | CSN377 | - | Jul 23, 10:10 UTC | Jul 23, 16:05 UTC | 5h 55m |
| 2026-07-21 | CSN378 | MAD → CAN | Jul 21, 20:25 UTC | Jul 22, 00:55 UTC | 4h 30m |
| 2026-07-21 | CSN377 | - | Jul 21, 12:15 UTC | Jul 21, 18:00 UTC | 5h 45m |
| 2026-07-20 | CSN3572 | SHA → CAN | Jul 20, 15:35 UTC | Jul 20, 15:45 UTC | 10m |
| 2026-07-20 | CSN3534 | TAO → CAN | Jul 20, 04:40 UTC | Jul 20, 04:50 UTC | 10m |
| 2026-07-19 | CSN668 | BEG → CAN | Jul 19, 09:10 UTC | Jul 19, 11:50 UTC | 2h 40m |
| 2026-07-19 | CSN667 | CAN → BEG | Jul 19, 02:20 UTC | Jul 19, 05:25 UTC | 3h 5m |
| 2026-07-18 | CSN3571 | - | Jul 18, 07:30 UTC | Jul 18, 07:40 UTC | 10m |
| 2026-07-18 | - | - | Jul 18, 02:50 UTC | Jul 18, 03:05 UTC | 15m |
| 2026-07-17 | CSN6044 | - | Jul 17, 18:05 UTC | Jul 17, 22:00 UTC | 3h 55m |
| 2026-07-16 | CSN6044 | - | Jul 16, 21:35 UTC | Jul 17, 21:30 UTC | 23h 55m |
| 2026-07-16 | CSN6043 | - | Jul 16, 19:35 UTC | Jul 17, 18:40 UTC | 23h 5m |
| 2026-07-16 | CSN6043 | - | Jul 16, 18:50 UTC | Jul 16, 22:05 UTC | 3h 15m |
| 2026-07-16 | CSN350 | - | Jul 16, 06:40 UTC | Jul 16, 06:55 UTC | 15m |
| 2026-07-16 | CSN349 | - | Jul 16, 02:00 UTC | Jul 16, 05:10 UTC | 3h 10m |
| 2026-07-14 | CSN3082 | - | Jul 14, 09:00 UTC | Jul 14, 09:15 UTC | 15m |
| 2026-07-14 | CSN3081 | - | Jul 14, 06:35 UTC | Jul 14, 07:15 UTC | 40m |
| 2026-07-12 | CSN378 | - | Jul 12, 20:05 UTC | Jul 13, 00:40 UTC | 4h 35m |
| 2026-07-12 | CSN377 | - | Jul 12, 10:05 UTC | Jul 12, 15:50 UTC | 5h 45m |
| 2026-07-11 | CSN377 | - | Jul 11, 17:40 UTC | Jul 12, 15:50 UTC | 22h 10m |
| 2026-07-10 | CSN378 | - | Jul 10, 19:35 UTC | Jul 11, 15:25 UTC | 19h 50m |
| 2026-07-10 | CSN378 | MAD → DAC | Jul 10, 19:15 UTC | Jul 11, 15:25 UTC | 20h 10m |
| 2026-07-10 | CSN377 | - | Jul 10, 10:05 UTC | Jul 10, 15:55 UTC | 5h 50m |
| 2026-07-09 | CSN377 | - | Jul 9, 17:35 UTC | Jul 10, 15:55 UTC | 22h 20m |
| 2026-07-09 | CSN377 | - | Jul 9, 15:35 UTC | Jul 10, 15:30 UTC | 23h 55m |
| 2026-07-09 | CSN634 | - | Jul 9, 15:05 UTC | Jul 10, 13:30 UTC | 22h 25m |
| 2026-07-08 | CSN633 | - | Jul 8, 17:25 UTC | Jul 8, 22:00 UTC | 4h 35m |
| 2026-07-07 | CSN650 | - | Jul 7, 10:45 UTC | Jul 7, 13:30 UTC | 2h 45m |
| 2026-07-06 | CSN649 | - | Jul 6, 21:50 UTC | Jul 7, 03:45 UTC | 5h 55m |
| 2026-07-06 | CSN664 | - | Jul 6, 08:55 UTC | Jul 6, 09:10 UTC | 15m |
| 2026-07-06 | CSN664 | - | Jul 6, 01:15 UTC | Jul 6, 08:05 UTC | 6h 50m |
| 2026-07-05 | CSN663 | - | Jul 5, 14:50 UTC | Jul 5, 22:35 UTC | 7h 45m |
| 2026-07-05 | CSN3082 | - | Jul 5, 09:10 UTC | Jul 5, 10:35 UTC | 1h 25m |
| 2026-07-04 | CSN650 | - | Jul 4, 11:35 UTC | Jul 5, 07:25 UTC | 19h 50m |
| 2026-07-04 | CSN650 | BUD → BKK | Jul 4, 11:00 UTC | Jul 5, 07:25 UTC | 20h 25m |
| 2026-07-03 | CSN649 | - | Jul 3, 22:25 UTC | Jul 4, 04:40 UTC | 6h 15m |
| 2026-07-02 | CSN650 | - | Jul 2, 11:00 UTC | Jul 2, 13:50 UTC | 2h 50m |
| 2026-07-01 | CSN649 | - | Jul 1, 21:50 UTC | Jul 2, 04:15 UTC | 6h 25m |
| 2026-06-30 | CSN650 | - | Jun 30, 11:00 UTC | Jun 30, 14:00 UTC | 3h 0m |
| 2026-06-29 | CSN649 | - | Jun 29, 21:50 UTC | Jun 30, 04:10 UTC | 6h 21m |
| 2026-06-27 | CSN304 | - | Jun 27, 21:25 UTC | Jun 28, 03:45 UTC | 6h 20m |
| 2026-06-27 | CSN303 | - | Jun 27, 11:39 UTC | Jun 27, 18:35 UTC | 6h 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 B-1168 page for operator, model, and routing details .