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
- 88
- Distinct callsigns
- 8
- Country
- BO
- Last broadcast
- 34m ago
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 8 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| BOV767 | Boliviana de Aviación | 22 | 2026-05-25 |
| BOV762 | Boliviana de Aviación | 21 | 2026-05-24 |
| BOV772 | Boliviana de Aviación | 14 | 2026-05-19 |
| BOV773 | Boliviana de Aviación | 12 | 2026-05-20 |
| BOV777 | Boliviana de Aviación | 8 | 2026-05-29 |
| BOV776 | Boliviana de Aviación | 7 | 2026-05-29 |
| BOV779 | Boliviana de Aviación | 3 | 2026-05-26 |
| BOV766 | - | 1 | 2026-04-16 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | BOV777 | MAD → VVI | May 29, 19:30 UTC | May 30, 06:00 UTC | 10h 30m |
| 2026-05-29 | BOV776 | VVI → MAD | May 29, 03:10 UTC | May 29, 12:55 UTC | 9h 45m |
| 2026-05-26 | BOV779 | MAD → CBB | May 26, 19:25 UTC | May 27, 05:49 UTC | 10h 25m |
| 2026-05-25 | BOV776 | VVI → MAD | May 25, 18:45 UTC | May 26, 12:24 UTC | 17h 39m |
| 2026-05-25 | BOV767 | MIA → VVI | May 25, 02:20 UTC | May 25, 16:50 UTC | 14h 30m |
| 2026-05-24 | BOV762 | VVI → MIA | May 24, 02:20 UTC | May 24, 19:50 UTC | 17h 30m |
| 2026-05-23 | BOV762 | VVI → MIA | May 23, 04:50 UTC | May 23, 20:30 UTC | 15h 41m |
| 2026-05-23 | BOV767 | MIA → VVI | May 23, 02:15 UTC | May 23, 02:40 UTC | 24m |
| 2026-05-22 | BOV762 | VVI → MIA | May 22, 04:50 UTC | May 22, 19:50 UTC | 15h 0m |
| 2026-05-22 | BOV767 | MIA → VVI | May 22, 02:05 UTC | May 22, 02:30 UTC | 25m |
| 2026-05-20 | BOV773 | MAD → VVI | May 20, 20:50 UTC | May 21, 10:45 UTC | 13h 55m |
| 2026-05-20 | BOV773 | MAD → VVI | May 20, 14:05 UTC | May 21, 10:45 UTC | 20h 40m |
| 2026-05-20 | BOV773 | MAD → VVI | May 20, 13:00 UTC | May 21, 10:45 UTC | 21h 45m |
| 2026-05-19 | BOV772 | VVI → MAD | May 19, 23:50 UTC | May 20, 09:30 UTC | 9h 41m |
| 2026-05-19 | BOV772 | VVI → MAD | May 19, 06:05 UTC | May 20, 02:05 UTC | 20h 0m |
| 2026-05-19 | BOV772 | VVI → MAD | May 19, 04:35 UTC | May 20, 02:05 UTC | 21h 30m |
| 2026-05-19 | BOV767 | MIA → VVI | May 19, 02:05 UTC | May 20, 02:00 UTC | 23h 55m |
| 2026-05-19 | BOV767 | MIA → VVI | May 19, 01:50 UTC | May 20, 00:00 UTC | 22h 10m |
| 2026-05-18 | BOV762 | VVI → MIA | May 18, 01:55 UTC | May 18, 19:35 UTC | 17h 39m |
| 2026-05-17 | BOV762 | VVI → MIA | May 17, 05:40 UTC | May 17, 19:25 UTC | 13h 45m |
| 2026-05-17 | BOV767 | MIA → VVI | May 17, 02:10 UTC | May 17, 02:30 UTC | 20m |
| 2026-05-16 | BOV762 | VVI → MIA | May 16, 03:00 UTC | May 16, 19:55 UTC | 16h 55m |
| 2026-05-15 | BOV777 | MAD → VVI | May 15, 19:10 UTC | May 16, 17:05 UTC | 21h 56m |
| 2026-05-15 | BOV776 | VVI → MAD | May 15, 03:10 UTC | May 15, 13:15 UTC | 10h 5m |
| 2026-05-12 | BOV779 | MAD → CBB | May 12, 19:30 UTC | May 13, 06:25 UTC | 10h 55m |
| 2026-05-11 | BOV776 | VVI → MAD | May 11, 17:45 UTC | May 12, 11:40 UTC | 17h 55m |
| 2026-05-11 | BOV767 | MIA → VVI | May 11, 02:00 UTC | May 11, 16:35 UTC | 14h 35m |
| 2026-05-10 | BOV762 | VVI → MIA | May 10, 05:34 UTC | May 10, 19:19 UTC | 13h 45m |
| 2026-05-10 | BOV767 | MIA → VVI | May 10, 02:00 UTC | May 10, 02:20 UTC | 20m |
| 2026-05-09 | BOV762 | VVI → MIA | May 9, 05:40 UTC | May 9, 20:25 UTC | 14h 45m |
| 2026-05-09 | BOV767 | MIA → VVI | May 9, 02:05 UTC | May 9, 02:30 UTC | 25m |
| 2026-05-08 | BOV762 | VVI → MIA | May 8, 05:59 UTC | May 8, 19:20 UTC | 13h 20m |
| 2026-05-08 | BOV767 | MIA → VVI | May 8, 02:24 UTC | May 8, 02:44 UTC | 20m |
| 2026-05-06 | BOV773 | MAD → VVI | May 6, 20:45 UTC | May 7, 10:15 UTC | 13h 30m |
| 2026-05-06 | BOV773 | MAD → VVI | May 6, 14:05 UTC | May 7, 10:15 UTC | 20h 10m |
| 2026-05-06 | BOV773 | MAD → VVI | May 6, 13:00 UTC | May 7, 10:15 UTC | 21h 15m |
| 2026-05-05 | BOV772 | VVI → MAD | May 5, 23:50 UTC | May 6, 09:25 UTC | 9h 35m |
| 2026-05-05 | BOV772 | VVI → MAD | May 5, 06:05 UTC | May 6, 02:05 UTC | 20h 0m |
| 2026-05-05 | BOV772 | VVI → MAD | May 5, 05:45 UTC | May 6, 02:05 UTC | 20h 20m |
| 2026-05-05 | BOV772 | VVI → MAD | May 5, 02:10 UTC | May 6, 02:01 UTC | 23h 50m |
| 2026-05-04 | BOV767 | MIA → VVI | May 4, 02:04 UTC | May 4, 20:55 UTC | 18h 51m |
| 2026-05-03 | BOV762 | VVI → MIA | May 3, 02:15 UTC | May 3, 19:00 UTC | 16h 44m |
| 2026-05-02 | BOV777 | MAD → VVI | May 2, 03:20 UTC | May 2, 19:10 UTC | 15h 50m |
| 2026-05-01 | BOV777 | MAD → VVI | May 1, 21:10 UTC | May 2, 19:10 UTC | 22h 0m |
| 2026-05-01 | BOV777 | MAD → VVI | May 1, 19:15 UTC | May 1, 20:30 UTC | 1h 15m |
| 2026-05-01 | BOV776 | VVI → MAD | May 1, 04:15 UTC | May 1, 14:00 UTC | 9h 45m |
| 2026-04-28 | BOV779 | MAD → CBB | Apr 28, 19:15 UTC | Apr 29, 05:30 UTC | 10h 15m |
| 2026-04-27 | BOV776 | VVI → MAD | Apr 27, 18:10 UTC | Apr 28, 12:10 UTC | 18h 0m |
| 2026-04-27 | BOV777 | MAD → VVI | Apr 27, 03:05 UTC | Apr 27, 16:30 UTC | 13h 25m |
| 2026-04-26 | BOV777 | MAD → VVI | Apr 26, 20:05 UTC | Apr 27, 16:30 UTC | 20h 25m |
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 .