sensors Mode-S transponder
E94C8E
ICAO 24-bit transponder address · allocated to Bolivia
Currently assigned to CP-3214 · AIRBUS A-330-200
- Hex
- E94C8E
- Octal
- 72246216
- Decimal
- 15,289,486
- Country
- BO
- Tail
- CP-3214
- Type
- A332
- Flights observed
- 94
- Distinct callsigns
- 11
- Country
- BO
- Last broadcast
- 2h ago
Current position
Country allocation
The ICAO 24-bit address E94C8E 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 11 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| BOV777 | Boliviana de Aviación | 38 | 2026-05-25 |
| BOV776 | Boliviana de Aviación | 18 | 2026-05-23 |
| BOV773 | Boliviana de Aviación | 9 | 2026-05-27 |
| BOV779 | Boliviana de Aviación | 7 | 2026-05-19 |
| BOV767 | Boliviana de Aviación | 7 | 2026-05-30 |
| BOV772 | Boliviana de Aviación | 5 | 2026-05-27 |
| BOV762 | Boliviana de Aviación | 4 | 2026-05-29 |
| BOV736 | - | 2 | 2026-04-15 |
| BOV708 | - | 2 | 2026-04-13 |
| BOV735 | - | 1 | 2026-04-15 |
| BOV709 | - | 1 | 2026-04-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-30 | BOV767 | MIA → VVI | May 30, 02:00 UTC | May 30, 02:20 UTC | 20m |
| 2026-05-29 | BOV762 | VVI → MIA | May 29, 04:55 UTC | May 29, 19:45 UTC | 14h 50m |
| 2026-05-29 | BOV767 | MIA → VVI | May 29, 02:25 UTC | May 29, 02:45 UTC | 20m |
| 2026-05-27 | BOV773 | MAD → VVI | May 27, 15:35 UTC | May 28, 10:35 UTC | 19h 0m |
| 2026-05-27 | BOV773 | MAD → VVI | May 27, 13:35 UTC | May 28, 10:35 UTC | 21h 0m |
| 2026-05-27 | BOV773 | MAD → VVI | May 27, 13:20 UTC | May 28, 10:35 UTC | 21h 15m |
| 2026-05-27 | BOV772 | VVI → MAD | May 27, 00:30 UTC | May 27, 10:00 UTC | 9h 30m |
| 2026-05-26 | BOV767 | MIA → VVI | May 26, 02:00 UTC | May 27, 01:19 UTC | 23h 20m |
| 2026-05-25 | BOV777 | MAD → VVI | May 25, 03:10 UTC | May 25, 19:50 UTC | 16h 39m |
| 2026-05-24 | BOV777 | MAD → VVI | May 24, 21:35 UTC | May 25, 19:50 UTC | 22h 15m |
| 2026-05-24 | BOV777 | MAD → VVI | May 24, 19:35 UTC | May 25, 19:30 UTC | 23h 55m |
| 2026-05-24 | BOV777 | MAD → VVI | May 24, 19:15 UTC | May 25, 16:40 UTC | 21h 25m |
| 2026-05-23 | BOV776 | VVI → MAD | May 23, 17:55 UTC | May 24, 10:40 UTC | 16h 45m |
| 2026-05-22 | BOV777 | MAD → VVI | May 22, 21:35 UTC | May 23, 16:30 UTC | 18h 54m |
| 2026-05-22 | BOV777 | MAD → VVI | May 22, 19:35 UTC | May 23, 16:30 UTC | 20h 54m |
| 2026-05-22 | BOV777 | MAD → VVI | May 22, 19:10 UTC | May 23, 16:30 UTC | 21h 19m |
| 2026-05-22 | BOV776 | VVI → MAD | May 22, 02:40 UTC | May 22, 12:15 UTC | 9h 35m |
| 2026-05-19 | BOV779 | MAD → CBB | May 19, 19:20 UTC | May 20, 05:40 UTC | 10h 21m |
| 2026-05-18 | BOV776 | VVI → MAD | May 18, 18:05 UTC | May 19, 11:55 UTC | 17h 49m |
| 2026-05-17 | BOV777 | MAD → VVI | May 17, 21:35 UTC | May 18, 16:35 UTC | 19h 0m |
| 2026-05-17 | BOV777 | MAD → VVI | May 17, 19:35 UTC | May 18, 16:35 UTC | 21h 0m |
| 2026-05-17 | BOV777 | MAD → VVI | May 17, 19:15 UTC | May 18, 16:35 UTC | 21h 20m |
| 2026-05-16 | BOV776 | VVI → MAD | May 16, 17:35 UTC | May 17, 11:50 UTC | 18h 15m |
| 2026-05-16 | BOV776 | VVI → MAD | May 16, 17:20 UTC | May 17, 11:50 UTC | 18h 30m |
| 2026-05-16 | BOV767 | MIA → VVI | May 16, 02:10 UTC | May 16, 15:50 UTC | 13h 41m |
| 2026-05-15 | BOV762 | VVI → MIA | May 15, 02:20 UTC | May 15, 19:30 UTC | 17h 9m |
| 2026-05-14 | BOV773 | MAD → VVI | May 14, 01:05 UTC | May 14, 14:15 UTC | 13h 10m |
| 2026-05-13 | BOV773 | MAD → VVI | May 13, 17:35 UTC | May 14, 14:15 UTC | 20h 40m |
| 2026-05-13 | BOV773 | MAD → VVI | May 13, 16:35 UTC | May 14, 14:15 UTC | 21h 40m |
| 2026-05-13 | BOV772 | VVI → MAD | May 13, 00:05 UTC | May 13, 09:35 UTC | 9h 30m |
| 2026-05-12 | BOV772 | VVI → MAD | May 12, 05:45 UTC | May 13, 02:25 UTC | 20h 40m |
| 2026-05-11 | BOV777 | MAD → VVI | May 11, 04:20 UTC | May 11, 19:35 UTC | 15h 15m |
| 2026-05-10 | BOV777 | MAD → VVI | May 10, 21:40 UTC | May 11, 19:35 UTC | 21h 56m |
| 2026-05-10 | BOV777 | MAD → VVI | May 10, 19:40 UTC | May 11, 19:30 UTC | 23h 51m |
| 2026-05-09 | BOV776 | VVI → MAD | May 9, 18:15 UTC | May 10, 11:20 UTC | 17h 5m |
| 2026-05-08 | BOV777 | MAD → VVI | May 8, 21:35 UTC | May 9, 16:45 UTC | 19h 10m |
| 2026-05-08 | BOV777 | MAD → VVI | May 8, 19:35 UTC | May 9, 16:45 UTC | 21h 10m |
| 2026-05-08 | BOV777 | MAD → VVI | May 8, 19:20 UTC | May 9, 16:45 UTC | 21h 25m |
| 2026-05-08 | BOV776 | VVI → MAD | May 8, 03:14 UTC | May 8, 13:00 UTC | 9h 45m |
| 2026-05-05 | BOV779 | MAD → CBB | May 5, 19:05 UTC | May 6, 05:50 UTC | 10h 45m |
| 2026-05-04 | BOV776 | VVI → MAD | May 4, 19:15 UTC | May 5, 12:30 UTC | 17h 15m |
| 2026-05-04 | BOV777 | MAD → VVI | May 4, 03:35 UTC | May 4, 17:50 UTC | 14h 15m |
| 2026-05-03 | BOV777 | MAD → VVI | May 3, 21:35 UTC | May 4, 17:50 UTC | 20h 15m |
| 2026-05-03 | BOV777 | MAD → VVI | May 3, 19:34 UTC | May 4, 17:50 UTC | 22h 15m |
| 2026-05-03 | BOV777 | MAD → VVI | May 3, 19:15 UTC | May 4, 17:30 UTC | 22h 15m |
| 2026-05-02 | BOV776 | VVI → MAD | May 2, 17:15 UTC | May 3, 11:05 UTC | 17h 49m |
| 2026-05-02 | BOV767 | MIA → VVI | May 2, 02:10 UTC | May 2, 15:40 UTC | 13h 30m |
| 2026-05-01 | BOV762 | VVI → MIA | May 1, 02:00 UTC | May 1, 19:15 UTC | 17h 15m |
| 2026-04-29 | BOV773 | MAD → VVI | Apr 29, 15:35 UTC | Apr 30, 10:15 UTC | 18h 39m |
| 2026-04-29 | BOV773 | MAD → VVI | Apr 29, 13:35 UTC | Apr 30, 10:15 UTC | 20h 39m |
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-3214 page for operator, model, and routing details .