sensors Mode-S transponder

E94C86

ICAO 24-bit transponder address · allocated to Bolivia

Currently assigned to CP-3206 · BOEING 737-800

Hex
E94C86
Octal
72246206
Decimal
15,289,478
Country
BO
Tail
CP-3206
Type
B738
No current signal · last broadcast 9h ago
Flights observed
66
Distinct callsigns
20
Country
BO
Last broadcast
9h ago

Last known position

Most recent position reported by Mode-S E94C86.

Country allocation

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

Recent flights last 50

DateFlightRouteTakeoffLandingDuration
2026-05-29 BOV739 GRU → VVI May 29, 21:45 UTCMay 29, 23:25 UTC1h 40m
2026-05-29 BOV734 VVI → GRU May 29, 18:50 UTCMay 29, 20:25 UTC1h 35m
2026-05-27 BOV795 ASU → VVI May 27, 00:10 UTCMay 27, 00:39 UTC30m
2026-05-26 BOV794 VVI → ASU May 26, 22:35 UTCMay 26, 22:59 UTC25m
2026-05-25 BOV735 GRU → VVI May 25, 20:50 UTCMay 25, 22:40 UTC1h 50m
2026-05-25 BOV736 VVI → GRU May 25, 18:05 UTCMay 25, 19:35 UTC1h 29m
2026-05-24 BOV735 GRU → VVI May 24, 17:00 UTCMay 24, 18:55 UTC1h 55m
2026-05-23 BOV733 GRU → VVI May 23, 20:10 UTCMay 24, 15:30 UTC19h 20m
2026-05-23 BOV732 VVI → GIG May 23, 17:10 UTCMay 23, 18:55 UTC1h 45m
2026-05-22 BOV735 GRU → VVI May 22, 17:35 UTCMay 23, 17:30 UTC23h 54m
2026-05-22 BOV735 GRU → VVI May 22, 17:15 UTCMay 22, 19:05 UTC1h 50m
2026-05-22 BOV736 VVI → GRU May 22, 14:40 UTCMay 22, 16:05 UTC1h 25m
2026-05-21 BOV736 VVI → GRU May 21, 17:40 UTCMay 22, 16:05 UTC22h 25m
2026-05-21 BOV708 CBB → EZE May 21, 15:20 UTCMay 21, 16:15 UTC55m
2026-05-20 BOV735 GRU → VVI May 20, 17:35 UTCMay 21, 16:15 UTC22h 40m
2026-05-20 BOV735 GRU → VVI May 20, 17:15 UTCMay 21, 15:30 UTC22h 15m
2026-05-20 BOV736 VVI → GRU May 20, 14:25 UTCMay 20, 15:45 UTC1h 20m
2026-05-19 BOV736 VVI → GRU May 19, 17:50 UTCMay 20, 15:45 UTC21h 56m
2026-05-19 BOV708 CBB → EZE May 19, 15:30 UTCMay 19, 16:35 UTC1h 5m
2026-05-18 BOV708 CBB → EZE May 18, 17:35 UTCMay 19, 16:35 UTC22h 59m
2026-05-18 BOV735 GRU → VVI May 18, 17:00 UTCMay 19, 15:30 UTC22h 29m
2026-05-18 BOV736 VVI → GRU May 18, 14:50 UTCMay 18, 15:30 UTC40m
2026-05-14 BOV709 EZE → VVI May 14, 17:40 UTCMay 14, 18:25 UTC45m
2026-05-14 BOV708 CBB → EZE May 14, 05:40 UTCMay 14, 16:15 UTC10h 35m
2026-05-14 BOV700 VVI → EZE May 14, 03:45 UTCMay 14, 04:40 UTC55m
2026-05-12 BOV735 GRU → VVI May 12, 16:55 UTCMay 12, 18:45 UTC1h 50m
2026-05-12 BOV736 VVI → GRU May 12, 14:10 UTCMay 12, 15:30 UTC1h 20m
2026-05-10 BOV709 EZE → VVI May 10, 17:45 UTCMay 10, 18:09 UTC25m
2026-05-10 BOV708 CBB → EZE May 10, 15:49 UTCMay 10, 16:30 UTC40m
2026-05-07 BOV735 GRU → VVI May 7, 17:25 UTCMay 7, 19:00 UTC1h 35m
2026-05-07 BOV736 VVI → GRU May 7, 06:05 UTCMay 7, 16:10 UTC10h 5m
2026-05-07 BOV700 VVI → EZE May 7, 03:55 UTCMay 7, 04:25 UTC30m
2026-05-06 BOV673 VVI → LPB May 6, 19:30 UTCMay 6, 19:40 UTC10m
2026-05-05 BOV677 VVI → LPB May 5, 22:50 UTCMay 5, 23:00 UTC10m
2026-05-04 BOV735 GRU → VVI May 4, 18:00 UTCMay 4, 19:35 UTC1h 36m
2026-05-04 BOV736 VVI → GRU May 4, 15:35 UTCMay 4, 16:55 UTC1h 20m
2026-05-04 BOV687 VVI → LPB May 4, 04:39 UTCMay 4, 04:50 UTC10m
2026-05-03 BOV610 CBB → LPB May 3, 16:45 UTCMay 3, 17:00 UTC15m
2026-04-30 BOV602 CBB → LPB Apr 30, 11:40 UTCApr 30, 11:45 UTC5m
2026-04-29 BOV677 VVI → LPB Apr 29, 23:15 UTCApr 29, 23:25 UTC10m
2026-04-29 BOV9733 - Apr 29, 18:05 UTCApr 29, 20:25 UTC2h 20m
2026-04-29 BOV1732 CBB → GIG Apr 29, 11:40 UTCApr 29, 16:35 UTC4h 55m
2026-04-27 BOV673 VVI → LPB Apr 27, 19:30 UTCApr 27, 19:55 UTC25m
2026-04-27 BOV684 LPB → VVI Apr 27, 00:30 UTCApr 27, 03:00 UTC2h 30m
2026-04-26 BOV979 VVI → LPB Apr 26, 23:15 UTCApr 26, 23:25 UTC10m
2026-04-25 BOV795 ASU → VVI Apr 25, 18:05 UTCApr 25, 18:40 UTC35m
2026-04-25 BOV794 VVI → ASU Apr 25, 16:25 UTCApr 25, 16:50 UTC25m
2026-04-25 BOV686 LPB → VVI Apr 25, 02:05 UTCApr 25, 02:15 UTC10m
2026-04-24 BOV677 VVI → LPB Apr 24, 22:05 UTCApr 24, 22:15 UTC10m
2026-04-24 BOV735 - Apr 24, 17:35 UTCApr 24, 19:10 UTC1h 35m

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

Mode-S E94C86 frequently asked

What is Mode-S code E94C86?
E94C86 is an ICAO 24-bit transponder address. Allocated to Bolivia. Assigned to CP-3206.
Where is Mode-S E94C86 registered?
Mode-S code E94C86 is allocated to Bolivia (BO). All aircraft registered there receive a Mode-S address from a fixed block defined by ICAO Annex 10.
Is E94C86 broadcasting right now?
No active broadcast right now. Last signal was 9h ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex E94C86, octal 72246206, decimal 15,289,478.
What flights does E94C86 operate?
Mode-S E94C86 has broadcast 20 distinct callsigns, including BOV735, BOV736, BOV708, BOV709, BOV739.