sensors Mode-S transponder

801548

ICAO 24-bit transponder address · allocated to India

Currently assigned to VT-YAM · BOEING 737 MAX 8

Hex
801548
Octal
40012510
Decimal
8,394,056
Country
IN
Tail
VT-YAM
Type
B38M
No current signal · last broadcast 3h ago
Flights observed
398
Distinct callsigns
20
Country
IN
Last broadcast
3h ago

Last known position

Most recent position reported by Mode-S 801548.

Country allocation

The ICAO 24-bit address 801548 falls within the block assigned to India (IN) by ICAO Annex 10, Volume III. Every aircraft registered in India 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
AKJ1359 - 11 2026-06-29
AKJ367Q - 8 2026-06-29
AKJ1350 Akasa Air 8 2026-06-28
AKJ619 Akasa Air 6 2026-06-28
AKJ453M - 6 2026-06-27
AKJ322P Akasa Air 6 2026-06-14
AKJ1421 - 6 2026-06-22
AKJ1178 - 6 2026-06-24
AKJ1106 Akasa Air 6 2026-06-04
AKJ978C - 5 2026-06-23
AKJ824G - 5 2026-05-21
AKJ618 - 5 2026-06-28
AKJ381V Akasa Air 5 2026-06-27
AKJ1515 - 5 2026-06-19
AKJ1177 - 5 2026-06-23
AKJ1122 Akasa Air 5 2026-06-03
AKJ1103 - 5 2026-06-29
AKJ880W - 4 2026-06-18
AKJ861Y - 4 2026-04-20
AKJ780F - 4 2026-06-14

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-07-13 AKJ503 - Jul 13, 12:00 UTCJul 13, 23:50 UTC11h 50m
2026-07-13 AKJ551 - Jul 13, 01:40 UTCJul 13, 02:01 UTC20m
2026-07-12 AKJ551 - Jul 12, 21:55 UTCJul 12, 22:35 UTC40m
2026-07-11 AKJ506 - Jul 11, 18:15 UTCJul 11, 23:20 UTC5h 5m
2026-07-11 AKJ505 - Jul 11, 15:10 UTCJul 11, 16:00 UTC50m
2026-07-11 AKJ505 - Jul 11, 12:05 UTCJul 11, 15:05 UTC3h 0m
2026-07-11 AKJ479M - Jul 11, 04:35 UTCJul 11, 05:35 UTC1h 0m
2026-07-11 AKJ479M - Jul 11, 03:50 UTCJul 11, 04:01 UTC10m
2026-07-02 AKJ1142 GOX → PNQ Jul 2, 14:55 UTCJul 2, 15:20 UTC25m
2026-07-02 AKJ1142 GOX → PNQ Jul 2, 12:30 UTCJul 2, 13:35 UTC1h 5m
2026-07-02 AKJ1141 - Jul 2, 10:00 UTCJul 2, 11:10 UTC1h 10m
2026-07-02 AKJ1141 - Jul 2, 08:35 UTCJul 2, 08:45 UTC10m
2026-07-02 AKJ1426 - Jul 2, 06:20 UTCJul 2, 06:35 UTC15m
2026-07-02 AKJ1425 - Jul 2, 01:50 UTCJul 2, 02:05 UTC15m
2026-07-01 AKJ2074 - Jul 1, 10:15 UTCJul 1, 10:30 UTC15m
2026-07-01 AKJ2074 - Jul 1, 08:50 UTCJul 1, 09:30 UTC40m
2026-07-01 AKJ1607 - Jul 1, 03:20 UTCJul 1, 05:05 UTC1h 45m
2026-06-30 AKJ914 - Jun 30, 06:45 UTCJun 30, 22:25 UTC15h 40m
2026-06-30 AKJ914 - Jun 30, 00:09 UTCJun 30, 22:25 UTC22h 15m
2026-06-29 AKJ914 - Jun 29, 22:19 UTCJun 30, 22:00 UTC23h 41m
2026-06-29 AKJ1103 - Jun 29, 16:50 UTCJun 29, 16:59 UTC10m
2026-06-29 AKJ378C - Jun 29, 15:09 UTCJun 29, 15:30 UTC20m
2026-06-29 AKJ172Q - Jun 29, 12:34 UTCJun 29, 12:45 UTC10m
2026-06-29 AKJ367Q - Jun 29, 04:55 UTCJun 29, 05:09 UTC15m
2026-06-29 AKJ367Q - Jun 29, 03:34 UTCJun 29, 04:04 UTC30m
2026-06-29 AKJ1359 - Jun 29, 01:10 UTCJun 29, 01:55 UTC45m
2026-06-28 AKJ1359 - Jun 28, 23:34 UTCJun 28, 23:44 UTC10m
2026-06-28 AKJ1350 DEL → BLR Jun 28, 19:04 UTCJun 28, 19:14 UTC10m
2026-06-28 AKJ1350 DEL → BLR Jun 28, 16:49 UTCJun 28, 17:30 UTC40m
2026-06-28 AKJ225Q - Jun 28, 13:45 UTCJun 28, 15:40 UTC1h 55m
2026-06-28 AKJ619 HKT → BOM Jun 28, 11:00 UTCJun 28, 11:14 UTC15m
2026-06-28 AKJ618 - Jun 28, 02:34 UTCJun 28, 09:55 UTC7h 20m
2026-06-27 AKJ701 - Jun 27, 11:59 UTCJun 27, 23:50 UTC11h 50m
2026-06-27 AKJ381V PNQ → BLR Jun 27, 09:04 UTCJun 27, 09:19 UTC15m
2026-06-27 AKJ381V PNQ → BLR Jun 27, 07:04 UTCJun 27, 07:55 UTC50m
2026-06-27 AKJ453M - Jun 27, 04:39 UTCJun 27, 05:25 UTC45m
2026-06-27 AKJ453M - Jun 27, 03:15 UTCJun 27, 03:25 UTC10m
2026-06-26 AKJ1126 CCU → BOM Jun 26, 20:10 UTCJun 26, 20:24 UTC15m
2026-06-26 AKJ1126 CCU → BOM Jun 26, 18:09 UTCJun 26, 18:49 UTC40m
2026-06-26 AKJ201P BOM → COK Jun 26, 15:54 UTCJun 26, 16:54 UTC1h 0m
2026-06-26 AKJ201P BOM → COK Jun 26, 14:25 UTCJun 26, 14:35 UTC10m
2026-06-26 AKJ1124 - Jun 26, 12:05 UTCJun 26, 12:29 UTC25m
2026-06-26 AKJ1123 BOM → IXD Jun 26, 07:45 UTCJun 26, 08:00 UTC15m
2026-06-26 AKJ367Q - Jun 26, 04:45 UTCJun 26, 05:05 UTC20m
2026-06-26 AKJ367Q - Jun 26, 03:24 UTCJun 26, 03:54 UTC30m
2026-06-26 AKJ1359 - Jun 26, 01:20 UTCJun 26, 02:05 UTC45m
2026-06-25 AKJ1359 - Jun 25, 23:44 UTCJun 25, 23:55 UTC10m
2026-06-25 AKJ692M - Jun 25, 10:09 UTCJun 25, 11:25 UTC1h 15m
2026-06-25 AKJ1313 - Jun 25, 06:55 UTCJun 25, 07:05 UTC10m
2026-06-25 AKJ1512 - Jun 25, 04:40 UTCJun 25, 05:05 UTC25m

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 VT-YAM page for operator, model, and routing details .

Mode-S 801548 frequently asked

What is Mode-S code 801548?
801548 is an ICAO 24-bit transponder address. Allocated to India. Assigned to VT-YAM.
Where is Mode-S 801548 registered?
Mode-S code 801548 is allocated to India (IN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 801548 broadcasting right now?
No active broadcast right now. Last signal was 3h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 801548, octal 40012510, decimal 8,394,056.
What flights does 801548 operate?
Mode-S 801548 has broadcast 20 distinct callsigns, including AKJ1359, AKJ367Q, AKJ1350, AKJ619, AKJ453M.