sensors Mode-S transponder
E94C7C
ICAO 24-bit transponder address · allocated to Bolivia
Currently assigned to CP-3196 · BOEING 737-800
- Hex
- E94C7C
- Octal
- 72246174
- Decimal
- 15,289,468
- Country
- BO
- Tail
- CP-3196
- Type
- B738
- Flights observed
- 63
- Distinct callsigns
- 18
- Country
- BO
- Last broadcast
- 9h ago
Last known position
Country allocation
The ICAO 24-bit address E94C7C 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 18 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| BOV736 | Boliviana de Aviación | 12 | 2026-05-29 |
| BOV735 | Boliviana de Aviación | 10 | 2026-05-29 |
| BOV709 | Boliviana de Aviación | 7 | 2026-05-08 |
| BOV708 | Boliviana de Aviación | 7 | 2026-05-08 |
| BOV701 | Boliviana de Aviación | 5 | 2026-05-25 |
| BOV700 | Boliviana de Aviación | 4 | 2026-05-25 |
| BOV734 | Boliviana de Aviación | 3 | 2026-05-24 |
| BOV733 | Boliviana de Aviación | 3 | 2026-04-25 |
| BOV739 | Boliviana de Aviación | 2 | 2026-05-15 |
| BOV732 | Boliviana de Aviación | 2 | 2026-04-25 |
| BOV979 | Boliviana de Aviación | 1 | 2026-04-27 |
| BOV9738 | - | 1 | 2026-05-01 |
| BOV795 | Boliviana de Aviación | 1 | 2026-05-19 |
| BOV685 | Boliviana de Aviación | 1 | 2026-05-03 |
| BOV680 | Boliviana de Aviación | 1 | 2026-05-02 |
| BOV677 | Boliviana de Aviación | 1 | 2026-04-21 |
| BOV672 | - | 1 | 2026-04-17 |
| BOV1731 | Boliviana de Aviación | 1 | 2026-05-01 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | BOV735 | GRU → VVI | May 29, 17:10 UTC | May 29, 18:55 UTC | 1h 45m |
| 2026-05-29 | BOV736 | VVI → GRU | May 29, 14:30 UTC | May 29, 15:55 UTC | 1h 26m |
| 2026-05-25 | BOV701 | EZE → VVI | May 25, 18:15 UTC | May 25, 19:00 UTC | 45m |
| 2026-05-25 | BOV700 | VVI → EZE | May 25, 16:00 UTC | May 25, 16:20 UTC | 20m |
| 2026-05-24 | BOV700 | VVI → EZE | May 24, 23:00 UTC | May 25, 13:40 UTC | 14h 40m |
| 2026-05-24 | BOV734 | VVI → GRU | May 24, 19:10 UTC | May 24, 20:40 UTC | 1h 30m |
| 2026-05-19 | BOV795 | ASU → VVI | May 19, 23:55 UTC | May 20, 00:30 UTC | 35m |
| 2026-05-19 | BOV735 | GRU → VVI | May 19, 17:00 UTC | May 19, 22:35 UTC | 5h 35m |
| 2026-05-19 | BOV736 | VVI → GRU | May 19, 14:35 UTC | May 19, 15:45 UTC | 1h 10m |
| 2026-05-17 | BOV735 | GRU → VVI | May 17, 17:01 UTC | May 17, 18:45 UTC | 1h 45m |
| 2026-05-17 | BOV736 | VVI → GRU | May 17, 14:10 UTC | May 17, 15:40 UTC | 1h 30m |
| 2026-05-16 | BOV736 | VVI → GRU | May 16, 18:00 UTC | May 17, 15:40 UTC | 21h 40m |
| 2026-05-16 | BOV701 | EZE → VVI | May 16, 05:35 UTC | May 16, 16:45 UTC | 11h 11m |
| 2026-05-15 | BOV739 | GRU → VVI | May 15, 21:50 UTC | May 16, 04:20 UTC | 6h 30m |
| 2026-05-15 | BOV734 | VVI → GRU | May 15, 18:30 UTC | May 15, 20:00 UTC | 1h 30m |
| 2026-05-11 | BOV735 | GRU → VVI | May 11, 17:30 UTC | May 11, 19:00 UTC | 1h 30m |
| 2026-05-11 | BOV736 | VVI → GRU | May 11, 14:40 UTC | May 11, 16:00 UTC | 1h 20m |
| 2026-05-08 | BOV709 | EZE → VVI | May 8, 18:35 UTC | May 8, 19:05 UTC | 30m |
| 2026-05-08 | BOV708 | CBB → EZE | May 8, 16:55 UTC | May 8, 17:30 UTC | 35m |
| 2026-05-07 | BOV709 | EZE → VVI | May 7, 17:40 UTC | May 8, 17:00 UTC | 23h 20m |
| 2026-05-07 | BOV708 | CBB → EZE | May 7, 15:45 UTC | May 7, 16:15 UTC | 30m |
| 2026-05-06 | BOV709 | EZE → VVI | May 6, 18:00 UTC | May 6, 18:35 UTC | 35m |
| 2026-05-06 | BOV708 | CBB → EZE | May 6, 16:20 UTC | May 6, 16:50 UTC | 30m |
| 2026-05-05 | BOV709 | EZE → VVI | May 5, 17:45 UTC | May 5, 18:20 UTC | 35m |
| 2026-05-05 | BOV708 | CBB → EZE | May 5, 11:20 UTC | May 5, 16:10 UTC | 4h 50m |
| 2026-05-03 | BOV709 | EZE → VVI | May 3, 17:50 UTC | May 3, 18:20 UTC | 30m |
| 2026-05-03 | BOV708 | CBB → EZE | May 3, 15:35 UTC | May 3, 16:05 UTC | 30m |
| 2026-05-03 | BOV685 | VVI → LPB | May 3, 04:50 UTC | May 3, 05:00 UTC | 10m |
| 2026-05-02 | BOV680 | LPB → VVI | May 2, 20:55 UTC | May 2, 23:25 UTC | 2h 30m |
| 2026-05-01 | BOV736 | VVI → GRU | May 1, 17:00 UTC | May 1, 18:45 UTC | 1h 45m |
| 2026-05-01 | BOV1731 | GIG → VVI | May 1, 07:55 UTC | May 1, 15:25 UTC | 7h 30m |
| 2026-05-01 | BOV9738 | - | May 1, 03:30 UTC | May 1, 06:45 UTC | 3h 15m |
| 2026-04-30 | BOV701 | EZE → VVI | Apr 30, 06:45 UTC | Apr 30, 11:30 UTC | 4h 45m |
| 2026-04-30 | BOV700 | VVI → EZE | Apr 30, 00:40 UTC | Apr 30, 05:30 UTC | 4h 50m |
| 2026-04-28 | BOV735 | GRU → VVI | Apr 28, 17:20 UTC | Apr 28, 19:00 UTC | 1h 40m |
| 2026-04-28 | BOV736 | VVI → GRU | Apr 28, 10:15 UTC | Apr 28, 16:05 UTC | 5h 50m |
| 2026-04-27 | BOV979 | VVI → LPB | Apr 27, 23:45 UTC | Apr 27, 23:55 UTC | 10m |
| 2026-04-26 | BOV735 | GRU → VVI | Apr 26, 17:40 UTC | Apr 26, 19:25 UTC | 1h 45m |
| 2026-04-26 | BOV736 | VVI → GRU | Apr 26, 14:50 UTC | Apr 26, 16:15 UTC | 1h 25m |
| 2026-04-25 | BOV733 | GRU → VVI | Apr 25, 19:05 UTC | Apr 26, 16:15 UTC | 21h 10m |
| 2026-04-25 | BOV733 | GRU → VVI | Apr 25, 18:50 UTC | Apr 26, 16:15 UTC | 21h 25m |
| 2026-04-25 | BOV732 | VVI → GIG | Apr 25, 16:00 UTC | Apr 25, 17:50 UTC | 1h 50m |
| 2026-04-25 | BOV701 | EZE → VVI | Apr 25, 05:25 UTC | Apr 25, 06:10 UTC | 45m |
| 2026-04-24 | BOV739 | GRU → VVI | Apr 24, 21:45 UTC | Apr 25, 04:10 UTC | 6h 25m |
| 2026-04-24 | BOV734 | VVI → GRU | Apr 24, 15:10 UTC | Apr 24, 20:05 UTC | 4h 55m |
| 2026-04-21 | BOV677 | VVI → LPB | Apr 21, 22:05 UTC | Apr 21, 22:15 UTC | 10m |
| 2026-04-21 | BOV735 | - | Apr 21, 17:15 UTC | Apr 21, 18:55 UTC | 1h 40m |
| 2026-04-21 | BOV736 | - | Apr 21, 14:25 UTC | Apr 21, 16:05 UTC | 1h 40m |
| 2026-04-19 | BOV709 | - | Apr 19, 17:35 UTC | Apr 19, 18:50 UTC | 1h 15m |
| 2026-04-18 | BOV708 | - | Apr 18, 21:05 UTC | Apr 19, 16:15 UTC | 19h 10m |
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-3196 page for operator, model, and routing details .