sensors Mode-S transponder
E94C88
ICAO 24-bit transponder address · allocated to Bolivia
Currently assigned to CP-3208 · AIRBUS A-330-200
- Hex
- E94C88
- Octal
- 72246210
- Decimal
- 15,289,480
- Country
- BO
- Tail
- CP-3208
- Type
- A332
- Flights observed
- 197
- Distinct callsigns
- 11
- Country
- BO
- Last broadcast
- Jul 26, 05:50 UTC
Last known position
Country allocation
The ICAO 24-bit address E94C88 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 | - | 49 | 2026-07-22 |
| BOV767 | Boliviana de Aviación | 44 | 2026-07-26 |
| BOV762 | Boliviana de Aviación | 39 | 2026-07-25 |
| BOV776 | Boliviana de Aviación | 30 | 2026-07-21 |
| BOV772 | Boliviana de Aviación | 14 | 2026-05-19 |
| BOV773 | Boliviana de Aviación | 12 | 2026-05-20 |
| BOV779 | Boliviana de Aviación | 3 | 2026-05-26 |
| BOV766 | - | 3 | 2026-07-20 |
| BOV765 | Boliviana de Aviación | 1 | 2026-06-23 |
| BOV708 | Boliviana de Aviación | 1 | 2026-07-12 |
| B0V708 | - | 1 | 2026-07-05 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-26 | BOV767 | MIA → VVI | Jul 26, 01:20 UTC | Jul 26, 05:50 UTC | 4h 30m |
| 2026-07-25 | BOV762 | VVI → MIA | Jul 25, 03:20 UTC | Jul 25, 19:00 UTC | 15h 40m |
| 2026-07-25 | BOV767 | MIA → VVI | Jul 25, 01:30 UTC | Jul 25, 01:50 UTC | 20m |
| 2026-07-24 | BOV762 | VVI → MIA | Jul 24, 18:35 UTC | Jul 24, 19:00 UTC | 25m |
| 2026-07-24 | BOV762 | VVI → MIA | Jul 24, 03:20 UTC | Jul 24, 17:10 UTC | 13h 50m |
| 2026-07-24 | BOV767 | MIA → VVI | Jul 24, 01:30 UTC | Jul 24, 01:50 UTC | 20m |
| 2026-07-22 | BOV777 | - | Jul 22, 16:05 UTC | Jul 23, 10:40 UTC | 18h 35m |
| 2026-07-22 | BOV777 | - | Jul 22, 14:05 UTC | Jul 23, 10:40 UTC | 20h 35m |
| 2026-07-21 | BOV776 | VVI → MAD | Jul 21, 16:05 UTC | Jul 22, 11:45 UTC | 19h 40m |
| 2026-07-21 | BOV776 | VVI → MAD | Jul 21, 14:10 UTC | Jul 22, 11:45 UTC | 21h 35m |
| 2026-07-20 | BOV766 | - | Jul 20, 21:20 UTC | Jul 21, 10:10 UTC | 12h 49m |
| 2026-07-20 | BOV777 | - | Jul 20, 14:05 UTC | Jul 21, 10:10 UTC | 20h 4m |
| 2026-07-20 | BOV777 | - | Jul 20, 13:20 UTC | Jul 21, 10:10 UTC | 20h 49m |
| 2026-07-20 | BOV776 | VVI → MAD | Jul 20, 01:00 UTC | Jul 20, 10:20 UTC | 9h 20m |
| 2026-07-19 | BOV776 | VVI → MAD | Jul 19, 04:05 UTC | Jul 20, 03:15 UTC | 23h 10m |
| 2026-07-19 | BOV767 | MIA → VVI | Jul 19, 03:00 UTC | Jul 20, 01:55 UTC | 22h 55m |
| 2026-07-19 | BOV767 | MIA → VVI | Jul 19, 01:15 UTC | Jul 19, 05:40 UTC | 4h 25m |
| 2026-07-18 | BOV762 | VVI → MIA | Jul 18, 01:10 UTC | Jul 18, 18:55 UTC | 17h 46m |
| 2026-07-17 | BOV762 | VVI → MIA | Jul 17, 18:40 UTC | Jul 17, 19:05 UTC | 25m |
| 2026-07-17 | BOV767 | - | Jul 17, 01:20 UTC | Jul 17, 16:10 UTC | 14h 50m |
| 2026-07-15 | BOV777 | - | Jul 15, 14:05 UTC | Jul 16, 09:50 UTC | 19h 45m |
| 2026-07-15 | BOV777 | - | Jul 15, 13:05 UTC | Jul 16, 09:50 UTC | 20h 45m |
| 2026-07-14 | BOV776 | - | Jul 14, 17:00 UTC | Jul 15, 10:15 UTC | 17h 14m |
| 2026-07-14 | BOV776 | - | Jul 14, 14:10 UTC | Jul 15, 10:15 UTC | 20h 4m |
| 2026-07-13 | BOV777 | - | Jul 13, 21:00 UTC | Jul 14, 11:05 UTC | 14h 5m |
| 2026-07-13 | BOV777 | - | Jul 13, 14:05 UTC | Jul 14, 11:05 UTC | 21h 0m |
| 2026-07-13 | BOV777 | - | Jul 13, 13:10 UTC | Jul 14, 11:05 UTC | 21h 55m |
| 2026-07-12 | BOV776 | - | Jul 12, 18:25 UTC | Jul 13, 10:10 UTC | 15h 45m |
| 2026-07-12 | BOV708 | CBB → EZE | Jul 12, 03:40 UTC | Jul 12, 17:01 UTC | 13h 20m |
| 2026-07-12 | BOV767 | - | Jul 12, 01:10 UTC | Jul 12, 01:30 UTC | 20m |
| 2026-07-11 | BOV762 | VVI → MIA | Jul 11, 18:40 UTC | Jul 11, 19:05 UTC | 25m |
| 2026-07-11 | BOV767 | - | Jul 11, 01:25 UTC | Jul 11, 16:05 UTC | 14h 40m |
| 2026-07-10 | BOV762 | VVI → MIA | Jul 10, 01:55 UTC | Jul 10, 19:10 UTC | 17h 15m |
| 2026-07-08 | BOV777 | - | Jul 8, 16:05 UTC | Jul 9, 10:50 UTC | 18h 45m |
| 2026-07-08 | BOV777 | - | Jul 8, 14:05 UTC | Jul 9, 10:50 UTC | 20h 45m |
| 2026-07-08 | BOV777 | - | Jul 8, 13:40 UTC | Jul 9, 10:50 UTC | 21h 10m |
| 2026-07-07 | BOV776 | - | Jul 7, 16:40 UTC | Jul 8, 10:40 UTC | 18h 0m |
| 2026-07-07 | BOV776 | - | Jul 7, 14:05 UTC | Jul 8, 10:40 UTC | 20h 35m |
| 2026-07-06 | BOV766 | - | Jul 6, 16:05 UTC | Jul 7, 10:30 UTC | 18h 25m |
| 2026-07-06 | BOV777 | - | Jul 6, 14:05 UTC | Jul 7, 10:30 UTC | 20h 25m |
| 2026-07-06 | BOV777 | - | Jul 6, 13:40 UTC | Jul 7, 10:30 UTC | 20h 50m |
| 2026-07-05 | BOV776 | EZE → MAD | Jul 5, 18:35 UTC | Jul 6, 10:40 UTC | 16h 5m |
| 2026-07-05 | B0V708 | - | Jul 5, 04:35 UTC | Jul 5, 16:10 UTC | 11h 35m |
| 2026-07-05 | BOV767 | - | Jul 5, 00:55 UTC | Jul 5, 01:15 UTC | 20m |
| 2026-07-04 | BOV762 | VVI → MIA | Jul 4, 05:00 UTC | Jul 4, 19:10 UTC | 14h 10m |
| 2026-07-04 | BOV767 | - | Jul 4, 01:20 UTC | Jul 4, 01:40 UTC | 20m |
| 2026-07-03 | BOV762 | VVI → MIA | Jul 3, 04:55 UTC | Jul 3, 19:20 UTC | 14h 25m |
| 2026-07-03 | BOV767 | - | Jul 3, 01:20 UTC | Jul 3, 01:40 UTC | 20m |
| 2026-07-01 | BOV777 | - | Jul 1, 14:05 UTC | Jul 2, 09:50 UTC | 19h 45m |
| 2026-07-01 | BOV777 | - | Jul 1, 13:05 UTC | Jul 2, 09:50 UTC | 20h 45m |
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-3208 page for operator, model, and routing details .