sensors Mode-S transponder

E0B214

ICAO 24-bit transponder address · allocated to Argentina

Currently assigned to LV-KHT · AIRBUS A-330-200

Hex
E0B214
Octal
70131024
Decimal
14,725,652
Country
AR
Tail
LV-KHT
Type
A332
No current signal · last broadcast 1h ago
Flights observed
57
Distinct callsigns
8
Country
AR
Last broadcast
1h ago

Last known position

Most recent position reported by Mode-S E0B214.

Country allocation

The ICAO 24-bit address E0B214 falls within the block assigned to Argentina (AR) by ICAO Annex 10, Volume III. Every aircraft registered in Argentina 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 8 distinct

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-30 ARG1324 EZE → PUJ May 30, 02:15 UTCMay 30, 02:50 UTC35m
2026-05-28 ARG1371 CUN → EZE May 28, 03:05 UTCMay 28, 22:30 UTC19h 25m
2026-05-28 ARG1371 CUN → EZE May 28, 02:35 UTCMay 28, 22:30 UTC19h 55m
2026-05-23 ARG1373 CUN → EZE May 23, 23:00 UTCMay 24, 06:55 UTC7h 55m
2026-05-23 ARG1372 EZE → CUN May 23, 11:55 UTCMay 23, 20:50 UTC8h 55m
2026-05-22 ARG1371 CUN → EZE May 22, 14:00 UTCMay 22, 22:15 UTC8h 15m
2026-05-22 ARG1370 EZE → CUN May 22, 02:35 UTCMay 22, 11:35 UTC9h 0m
2026-05-21 ARG1371 CUN → EZE May 21, 14:05 UTCMay 21, 22:15 UTC8h 10m
2026-05-21 ARG1370 EZE → CUN May 21, 02:30 UTCMay 21, 11:15 UTC8h 45m
2026-05-17 ARG1329 PUJ → EZE May 17, 13:05 UTCMay 18, 07:05 UTC18h 0m
2026-05-17 ARG1328 EZE → PUJ May 17, 11:50 UTCMay 18, 07:05 UTC19h 15m
2026-05-16 ARG1373 CUN → EZE May 16, 23:20 UTCMay 17, 07:10 UTC7h 50m
2026-05-16 ARG1372 EZE → CUN May 16, 11:46 UTCMay 16, 20:55 UTC9h 10m
2026-05-15 ARG1329 PUJ → EZE May 15, 13:05 UTCMay 16, 07:05 UTC18h 0m
2026-05-15 ARG1328 EZE → PUJ May 15, 11:45 UTCMay 16, 07:05 UTC19h 20m
2026-05-14 ARG1371 CUN → EZE May 14, 14:15 UTCMay 14, 22:25 UTC8h 10m
2026-05-14 ARG1370 EZE → CUN May 14, 02:50 UTCMay 14, 11:30 UTC8h 40m
2026-05-13 ARG1324 EZE → PUJ May 13, 02:15 UTCMay 13, 19:50 UTC17h 35m
2026-05-12 ARG1324 EZE → PUJ May 12, 02:45 UTCMay 12, 19:55 UTC17h 10m
2026-05-10 ARG1329 PUJ → EZE May 10, 13:05 UTCMay 11, 07:30 UTC18h 25m
2026-05-10 ARG1329 PUJ → EZE May 10, 11:50 UTCMay 11, 07:30 UTC19h 40m
2026-05-09 ARG1373 CUN → EZE May 9, 16:10 UTCMay 10, 07:34 UTC15h 25m
2026-05-09 ARG1372 EZE → CUN May 9, 12:15 UTCMay 10, 07:34 UTC19h 20m
2026-05-08 ARG1329 PUJ → EZE May 8, 13:05 UTCMay 9, 07:20 UTC18h 15m
2026-05-08 ARG1328 EZE → PUJ May 8, 11:49 UTCMay 9, 07:20 UTC19h 30m
2026-05-07 ARG1370 EZE → CUN May 7, 03:05 UTCMay 7, 22:35 UTC19h 30m
2026-05-07 ARG1370 EZE → CUN May 7, 02:45 UTCMay 7, 22:35 UTC19h 50m
2026-04-26 ARG1373 CUN → EZE Apr 26, 06:45 UTCApr 26, 07:00 UTC15m
2026-04-25 ARG1373 CUN → EZE Apr 25, 23:00 UTCApr 26, 03:05 UTC4h 5m
2026-04-25 ARG1372 EZE → CUN Apr 25, 11:40 UTCApr 25, 20:20 UTC8h 40m
2026-04-24 ARG1329 PUJ → EZE Apr 24, 13:05 UTCApr 25, 07:30 UTC18h 25m
2026-04-24 ARG1329 PUJ → EZE Apr 24, 11:45 UTCApr 25, 07:30 UTC19h 45m
2026-04-22 ARG1324 EZE → PUJ Apr 22, 02:30 UTCApr 22, 19:45 UTC17h 15m
2026-04-21 ARG1324 EZE → PUJ Apr 21, 02:10 UTCApr 21, 19:50 UTC17h 40m
2026-04-19 ARG1329 PUJ → EZE Apr 19, 13:05 UTCApr 20, 07:20 UTC18h 15m
2026-04-19 ARG1329 PUJ → EZE Apr 19, 11:50 UTCApr 20, 07:20 UTC19h 30m
2026-04-19 ARG1373 CUN → EZE Apr 19, 06:35 UTCApr 19, 06:50 UTC15m
2026-04-18 ARG1373 CUN → EZE Apr 18, 22:45 UTCApr 19, 02:55 UTC4h 10m
2026-04-18 ARG1372 EZE → CUN Apr 18, 11:35 UTCApr 18, 20:00 UTC8h 25m
2026-04-18 ARG1329 PUJ → EZE Apr 18, 07:25 UTCApr 18, 07:30 UTC5m
2026-04-18 ARG1329 PUJ → EZE Apr 18, 05:25 UTCApr 18, 07:20 UTC1h 55m
2026-04-18 ARG1329 PUJ → EZE Apr 18, 04:45 UTCApr 18, 06:30 UTC1h 45m
2026-04-18 ARG1329 PUJ → EZE Apr 18, 03:55 UTCApr 18, 05:20 UTC1h 25m
2026-04-18 ARG1329 PUJ → EZE Apr 18, 01:25 UTCApr 18, 01:40 UTC15m
2026-04-18 ARG1329 PUJ → EZE Apr 18, 00:00 UTCApr 18, 01:20 UTC1h 20m
2026-04-17 ARG1328 EZE → PUJ Apr 17, 17:25 UTCApr 17, 18:40 UTC1h 15m
2026-04-17 ARG1328 EZE → PUJ Apr 17, 17:05 UTCApr 17, 17:15 UTC10m
2026-04-17 ARG1328 EZE → PUJ Apr 17, 13:20 UTCApr 17, 14:55 UTC1h 35m
2026-04-17 ARG1328 EZE → PUJ Apr 17, 11:45 UTCApr 17, 13:15 UTC1h 30m
2026-04-15 ARG1371 CUN → EZE Apr 15, 21:30 UTCApr 15, 22:00 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 LV-KHT page for operator, model, and routing details .

Mode-S E0B214 frequently asked

What is Mode-S code E0B214?
E0B214 is an ICAO 24-bit transponder address. Allocated to Argentina. Assigned to LV-KHT.
Where is Mode-S E0B214 registered?
Mode-S code E0B214 is allocated to Argentina (AR). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is E0B214 broadcasting right now?
No active broadcast right now. Last signal was 1h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex E0B214, octal 70131024, decimal 14,725,652.
What flights does E0B214 operate?
Mode-S E0B214 has broadcast 8 distinct callsigns, including ARG1329, ARG1371, ARG1370, ARG1373, ARG1328.