sensors Mode-S transponder

88819E

ICAO 24-bit transponder address · allocated to Vietnam

Currently assigned to VN-A585 · AIRBUS A-321

Hex
88819E
Octal
42100636
Decimal
8,946,078
Country
VN
Tail
VN-A585
Type
A321
No current signal · last broadcast 12h ago
Flights observed
51
Distinct callsigns
9
Country
VN
Last broadcast
12h ago

Last known position

Most recent position reported by Mode-S 88819E.

Country allocation

The ICAO 24-bit address 88819E falls within the block assigned to Vietnam (VN) by ICAO Annex 10, Volume III. Every aircraft registered in Vietnam 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 9 distinct

Callsign Airline Flights Last seen
BAV9589 Bay Aviation Ltd 16 2026-05-21
BAV9588 Bay Aviation Ltd 10 2026-05-28
BAV9345 Bay Aviation Ltd 9 2026-05-29
BAV9344 Bay Aviation Ltd 9 2026-05-29
BAV203 Bay Aviation Ltd 2 2026-05-29
BAV148 Bay Aviation Ltd 2 2026-05-29
BAV286 Bay Aviation Ltd 1 2026-05-28
BAV273 Bay Aviation Ltd 1 2026-05-27
BAV173 Bay Aviation Ltd 1 2026-04-22

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 BAV9345 MNL → DAD May 29, 20:10 UTCMay 29, 20:45 UTC35m
2026-05-29 BAV9344 DAD → MNL May 29, 13:55 UTCMay 29, 18:05 UTC4h 10m
2026-05-29 BAV148 DAD → HAN May 29, 12:05 UTCMay 29, 12:20 UTC15m
2026-05-29 BAV203 HAN → SGN May 29, 00:20 UTCMay 29, 00:45 UTC25m
2026-05-28 BAV286 SGN → HAN May 28, 15:25 UTCMay 28, 15:40 UTC15m
2026-05-28 BAV9588 DAD → MFM May 28, 07:00 UTCMay 28, 07:15 UTC15m
2026-05-28 BAV203 HAN → SGN May 28, 00:35 UTCMay 28, 01:00 UTC25m
2026-05-27 BAV273 HAN → SGN May 27, 13:55 UTCMay 27, 18:25 UTC4h 30m
2026-05-27 BAV148 DAD → HAN May 27, 12:15 UTCMay 27, 12:30 UTC15m
2026-05-26 BAV9588 DAD → MFM May 26, 07:05 UTCMay 26, 07:19 UTC15m
2026-05-25 BAV9345 MNL → DAD May 25, 19:40 UTCMay 25, 20:09 UTC30m
2026-05-25 BAV9344 DAD → MNL May 25, 17:15 UTCMay 25, 17:50 UTC35m
2026-05-25 BAV9588 DAD → MFM May 25, 07:15 UTCMay 25, 07:25 UTC10m
2026-05-24 BAV9588 DAD → MFM May 24, 06:55 UTCMay 24, 07:05 UTC10m
2026-05-22 BAV9345 - May 22, 19:50 UTCMay 22, 20:15 UTC25m
2026-05-22 BAV9344 DAD → MNL May 22, 17:40 UTCMay 22, 18:10 UTC30m
2026-05-22 BAV9588 DAD → MFM May 22, 06:50 UTCMay 22, 07:00 UTC10m
2026-05-21 BAV9589 MFM → DAD May 21, 08:55 UTCMay 21, 09:10 UTC15m
2026-05-20 BAV9588 DAD → MFM May 20, 07:00 UTCMay 20, 07:15 UTC15m
2026-05-19 BAV9589 MFM → DAD May 19, 09:00 UTCMay 19, 09:15 UTC15m
2026-05-18 BAV9345 - May 18, 19:15 UTCMay 18, 19:50 UTC35m
2026-05-18 BAV9344 DAD → MNL May 18, 17:05 UTCMay 18, 17:45 UTC40m
2026-05-18 BAV9588 DAD → MFM May 18, 07:00 UTCMay 18, 07:10 UTC10m
2026-05-17 BAV9589 MFM → DAD May 17, 09:00 UTCMay 17, 09:15 UTC15m
2026-05-16 BAV9589 MFM → DAD May 16, 09:01 UTCMay 16, 09:16 UTC15m
2026-05-15 BAV9345 MNL → DAD May 15, 20:20 UTCMay 15, 20:50 UTC30m
2026-05-15 BAV9344 DAD → MNL May 15, 17:35 UTCMay 15, 18:20 UTC45m
2026-05-15 BAV9589 MFM → DAD May 15, 09:15 UTCMay 15, 09:30 UTC15m
2026-05-07 BAV9589 MFM → DAD May 7, 09:00 UTCMay 7, 09:15 UTC15m
2026-05-06 BAV9589 MFM → DAD May 6, 09:00 UTCMay 6, 09:10 UTC10m
2026-05-05 BAV9589 MFM → DAD May 5, 09:00 UTCMay 5, 09:10 UTC10m
2026-05-04 BAV9345 MNL → DAD May 4, 19:35 UTCMay 4, 20:05 UTC30m
2026-05-04 BAV9344 DAD → MNL May 4, 17:45 UTCMay 4, 18:15 UTC30m
2026-05-04 BAV9589 MFM → DAD May 4, 08:55 UTCMay 4, 09:10 UTC15m
2026-05-03 BAV9589 MFM → DAD May 3, 10:35 UTCMay 3, 10:50 UTC15m
2026-05-02 BAV9589 MFM → DAD May 2, 18:35 UTCMay 2, 18:45 UTC10m
2026-04-27 BAV9345 MNL → DAD Apr 27, 19:20 UTCApr 27, 19:50 UTC30m
2026-04-27 BAV9344 DAD → MNL Apr 27, 17:25 UTCApr 27, 18:00 UTC35m
2026-04-27 BAV9589 MFM → DAD Apr 27, 08:55 UTCApr 27, 09:10 UTC15m
2026-04-26 BAV9589 MFM → DAD Apr 26, 09:00 UTCApr 26, 09:15 UTC15m
2026-04-25 BAV9589 MFM → DAD Apr 25, 09:25 UTCApr 25, 09:40 UTC15m
2026-04-24 BAV9345 MNL → DAD Apr 24, 19:40 UTCApr 24, 20:15 UTC35m
2026-04-24 BAV9344 DAD → MNL Apr 24, 17:50 UTCApr 24, 18:25 UTC35m
2026-04-24 BAV9589 MFM → DAD Apr 24, 09:00 UTCApr 24, 09:15 UTC15m
2026-04-23 BAV9589 MFM → DAD Apr 23, 09:40 UTCApr 23, 09:55 UTC15m
2026-04-22 BAV173 DAD → SGN Apr 22, 12:50 UTCApr 22, 13:00 UTC10m
2026-04-22 BAV9588 DAD → MFM Apr 22, 07:10 UTCApr 22, 07:20 UTC10m
2026-04-14 BAV9588 DAD → MFM Apr 14, 06:55 UTCApr 14, 07:05 UTC10m
2026-04-13 BAV9345 - Apr 13, 19:15 UTCApr 13, 19:50 UTC35m
2026-04-13 BAV9344 - Apr 13, 17:10 UTCApr 13, 17:40 UTC30m

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

Mode-S 88819E frequently asked

What is Mode-S code 88819E?
88819E is an ICAO 24-bit transponder address. Allocated to Vietnam. Assigned to VN-A585.
Where is Mode-S 88819E registered?
Mode-S code 88819E is allocated to Vietnam (VN). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is 88819E broadcasting right now?
No active broadcast right now. Last signal was 12h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 88819E, octal 42100636, decimal 8,946,078.
What flights does 88819E operate?
Mode-S 88819E has broadcast 9 distinct callsigns, including BAV9589, BAV9588, BAV9345, BAV9344, BAV203.