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