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
- 106
- Distinct callsigns
- 20
- Country
- BO
- Last broadcast
- 13h 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 | 19 | 2026-07-17 |
| BOV708 | Boliviana de Aviación | 16 | 2026-06-27 |
| BOV735 | Boliviana de Aviación | 14 | 2026-07-17 |
| BOV709 | Boliviana de Aviación | 13 | 2026-06-27 |
| BOV734 | Boliviana de Aviación | 4 | 2026-07-16 |
| BOV733 | Boliviana de Aviación | 4 | 2026-06-10 |
| BOV732 | Boliviana de Aviación | 4 | 2026-06-10 |
| BOV701 | Boliviana de Aviación | 4 | 2026-06-19 |
| BOV700 | - | 4 | 2026-07-07 |
| BOV673 | Boliviana de Aviación | 4 | 2026-05-04 |
| BOV794 | Boliviana de Aviación | 3 | 2026-05-23 |
| BOV739 | - | 3 | 2026-07-16 |
| BOV737 | Boliviana de Aviación | 3 | 2026-07-02 |
| BOV979 | Boliviana de Aviación | 2 | 2026-05-01 |
| BOV977 | - | 1 | 2026-04-17 |
| 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 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-17 | BOV735 | GRU → VVI | Jul 17, 17:20 UTC | Jul 17, 19:00 UTC | 1h 40m |
| 2026-07-17 | BOV736 | VVI → GRU | Jul 17, 06:00 UTC | Jul 17, 15:49 UTC | 9h 50m |
| 2026-07-16 | BOV739 | - | Jul 16, 21:45 UTC | Jul 17, 04:29 UTC | 6h 45m |
| 2026-07-16 | BOV734 | VVI → GRU | Jul 16, 18:40 UTC | Jul 16, 20:09 UTC | 1h 30m |
| 2026-07-07 | BOV735 | GRU → VVI | Jul 7, 17:30 UTC | Jul 7, 19:20 UTC | 1h 50m |
| 2026-07-07 | BOV736 | VVI → GRU | Jul 7, 06:25 UTC | Jul 7, 15:40 UTC | 9h 15m |
| 2026-07-07 | BOV700 | - | Jul 7, 03:55 UTC | Jul 7, 05:10 UTC | 1h 15m |
| 2026-07-02 | BOV737 | GRU → CBB | Jul 2, 17:15 UTC | Jul 2, 18:55 UTC | 1h 40m |
| 2026-07-01 | BOV739 | - | Jul 1, 21:50 UTC | Jul 2, 15:45 UTC | 17h 55m |
| 2026-07-01 | BOV734 | VVI → GRU | Jul 1, 18:55 UTC | Jul 1, 20:25 UTC | 1h 30m |
| 2026-06-27 | BOV709 | EZE → VVI | Jun 27, 18:09 UTC | Jun 27, 18:54 UTC | 45m |
| 2026-06-27 | BOV708 | CBB → EZE | Jun 27, 15:45 UTC | Jun 27, 16:49 UTC | 1h 5m |
| 2026-06-22 | BOV709 | EZE → VVI | Jun 22, 17:50 UTC | Jun 22, 18:19 UTC | 30m |
| 2026-06-22 | BOV708 | CBB → EZE | Jun 22, 05:49 UTC | Jun 22, 16:20 UTC | 10h 30m |
| 2026-06-21 | BOV709 | EZE → VVI | Jun 21, 17:54 UTC | Jun 22, 04:40 UTC | 10h 45m |
| 2026-06-21 | BOV708 | CBB → EZE | Jun 21, 15:40 UTC | Jun 21, 16:34 UTC | 55m |
| 2026-06-19 | BOV701 | EZE → VVI | Jun 19, 06:54 UTC | Jun 19, 07:34 UTC | 40m |
| 2026-06-18 | BOV737 | GRU → CBB | Jun 18, 17:35 UTC | Jun 19, 05:30 UTC | 11h 54m |
| 2026-06-18 | BOV736 | VVI → GRU | Jun 18, 15:05 UTC | Jun 18, 16:30 UTC | 1h 25m |
| 2026-06-16 | BOV709 | EZE → VVI | Jun 16, 19:00 UTC | Jun 16, 19:30 UTC | 30m |
| 2026-06-16 | BOV708 | CBB → EZE | Jun 16, 17:10 UTC | Jun 16, 17:49 UTC | 40m |
| 2026-06-13 | BOV737 | GRU → CBB | Jun 13, 18:40 UTC | Jun 13, 20:35 UTC | 1h 55m |
| 2026-06-13 | BOV736 | VVI → GRU | Jun 13, 05:25 UTC | Jun 13, 17:30 UTC | 12h 5m |
| 2026-06-12 | BOV735 | GRU → VVI | Jun 12, 17:35 UTC | Jun 13, 04:20 UTC | 10h 45m |
| 2026-06-12 | BOV736 | VVI → GRU | Jun 12, 04:55 UTC | Jun 12, 16:15 UTC | 11h 20m |
| 2026-06-10 | BOV733 | GRU → VVI | Jun 10, 21:45 UTC | Jun 10, 23:45 UTC | 2h 0m |
| 2026-06-10 | BOV733 | GRU → VVI | Jun 10, 19:45 UTC | Jun 10, 20:30 UTC | 45m |
| 2026-06-10 | BOV732 | VVI → GIG | Jun 10, 17:50 UTC | Jun 10, 18:25 UTC | 35m |
| 2026-06-10 | BOV732 | VVI → GIG | Jun 10, 06:40 UTC | Jun 10, 17:00 UTC | 10h 20m |
| 2026-06-09 | BOV709 | EZE → VVI | Jun 9, 18:55 UTC | Jun 10, 05:30 UTC | 10h 35m |
| 2026-06-08 | BOV735 | GRU → VVI | Jun 8, 17:50 UTC | Jun 8, 19:45 UTC | 1h 55m |
| 2026-06-08 | BOV736 | VVI → GRU | Jun 8, 15:15 UTC | Jun 8, 16:45 UTC | 1h 30m |
| 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 |
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 .