sensors Mode-S transponder
E485B9
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PR-VHB · BEECH 400 Beechjet
- Hex
- E485B9
- Octal
- 71102671
- Decimal
- 14,976,441
- Country
- BR
- Tail
- PR-VHB
- Type
- BE40
- Flights observed
- 54
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- Jul 24, 19:55 UTC
Last known position
Country allocation
The ICAO 24-bit address E485B9 falls within the block assigned to Brazil (BR) by ICAO Annex 10, Volume III. Every aircraft registered in Brazil 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 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| PRVHB | - | 54 | 2026-07-24 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-24 | PRVHB | - | Jul 24, 13:35 UTC | Jul 24, 19:55 UTC | 6h 20m |
| 2026-07-21 | PRVHB | - | Jul 21, 13:50 UTC | Jul 21, 18:25 UTC | 4h 35m |
| 2026-07-21 | PRVHB | - | Jul 21, 11:55 UTC | Jul 21, 12:10 UTC | 15m |
| 2026-07-19 | PRVHB | - | Jul 19, 17:15 UTC | Jul 19, 17:25 UTC | 10m |
| 2026-07-19 | PRVHB | - | Jul 19, 12:00 UTC | Jul 19, 16:35 UTC | 4h 35m |
| 2026-07-18 | PRVHB | - | Jul 18, 14:40 UTC | Jul 19, 12:50 UTC | 22h 10m |
| 2026-07-18 | PRVHB | - | Jul 18, 11:05 UTC | Jul 18, 15:25 UTC | 4h 20m |
| 2026-07-17 | PRVHB | - | Jul 17, 10:25 UTC | Jul 17, 19:49 UTC | 9h 25m |
| 2026-07-15 | PRVHB | - | Jul 15, 11:55 UTC | Jul 15, 20:00 UTC | 8h 5m |
| 2026-07-09 | PRVHB | - | Jul 9, 22:25 UTC | Jul 9, 23:20 UTC | 55m |
| 2026-07-08 | PRVHB | - | Jul 8, 14:50 UTC | Jul 8, 23:15 UTC | 8h 25m |
| 2026-07-08 | PRVHB | - | Jul 8, 13:00 UTC | Jul 8, 13:30 UTC | 30m |
| 2026-07-06 | PRVHB | - | Jul 6, 20:15 UTC | Jul 6, 21:00 UTC | 45m |
| 2026-07-04 | PRVHB | - | Jul 4, 15:40 UTC | Jul 4, 16:40 UTC | 1h 0m |
| 2026-07-03 | PRVHB | - | Jul 3, 17:20 UTC | Jul 3, 18:10 UTC | 50m |
| 2026-07-02 | PRVHB | - | Jul 2, 19:15 UTC | Jul 3, 18:10 UTC | 22h 55m |
| 2026-07-02 | PRVHB | - | Jul 2, 10:20 UTC | Jul 2, 10:50 UTC | 30m |
| 2026-06-26 | PRVHB | - | Jun 26, 17:59 UTC | Jun 26, 18:29 UTC | 30m |
| 2026-06-25 | PRVHB | - | Jun 25, 12:54 UTC | Jun 25, 13:40 UTC | 45m |
| 2026-06-25 | PRVHB | - | Jun 25, 09:40 UTC | Jun 25, 11:30 UTC | 1h 50m |
| 2026-06-22 | PRVHB | - | Jun 22, 18:54 UTC | Jun 23, 12:55 UTC | 18h 0m |
| 2026-06-20 | PRVHB | - | Jun 20, 13:34 UTC | Jun 20, 17:39 UTC | 4h 5m |
| 2026-06-20 | PRVHB | - | Jun 20, 11:25 UTC | Jun 20, 12:04 UTC | 40m |
| 2026-06-03 | PRVHB | - | Jun 3, 21:15 UTC | Jun 3, 21:25 UTC | 10m |
| 2026-06-03 | PRVHB | - | Jun 3, 16:10 UTC | Jun 3, 20:15 UTC | 4h 5m |
| 2026-05-28 | PRVHB | - | May 28, 21:00 UTC | May 28, 21:10 UTC | 10m |
| 2026-05-27 | PRVHB | - | May 27, 21:25 UTC | May 27, 22:10 UTC | 45m |
| 2026-05-27 | PRVHB | - | May 27, 18:15 UTC | May 27, 20:05 UTC | 1h 50m |
| 2026-05-27 | PRVHB | - | May 27, 14:25 UTC | May 27, 14:45 UTC | 20m |
| 2026-05-26 | PRVHB | - | May 26, 17:04 UTC | May 26, 17:50 UTC | 45m |
| 2026-05-26 | PRVHB | - | May 26, 14:24 UTC | May 26, 14:40 UTC | 15m |
| 2026-05-25 | PRVHB | - | May 25, 14:55 UTC | May 25, 15:30 UTC | 35m |
| 2026-05-20 | PRVHB | - | May 20, 12:50 UTC | May 20, 19:20 UTC | 6h 30m |
| 2026-05-18 | PRVHB | - | May 18, 10:00 UTC | May 18, 16:50 UTC | 6h 50m |
| 2026-05-17 | PRVHB | - | May 17, 20:20 UTC | May 18, 16:50 UTC | 20h 30m |
| 2026-05-17 | PRVHB | - | May 17, 20:01 UTC | May 18, 16:50 UTC | 20h 50m |
| 2026-05-15 | PRVHB | - | May 15, 20:20 UTC | May 16, 12:21 UTC | 16h 1m |
| 2026-05-15 | PRVHB | - | May 15, 18:55 UTC | May 15, 19:35 UTC | 40m |
| 2026-05-14 | PRVHB | - | May 14, 12:50 UTC | May 14, 13:30 UTC | 40m |
| 2026-05-08 | PRVHB | - | May 8, 18:05 UTC | May 8, 21:00 UTC | 2h 55m |
| 2026-05-06 | PRVHB | - | May 6, 19:50 UTC | May 7, 13:20 UTC | 17h 30m |
| 2026-05-03 | PRVHB | - | May 3, 18:20 UTC | May 4, 13:55 UTC | 19h 35m |
| 2026-05-03 | PRVHB | - | May 3, 17:05 UTC | May 4, 13:55 UTC | 20h 50m |
| 2026-04-30 | PRVHB | - | Apr 30, 18:25 UTC | Apr 30, 19:30 UTC | 1h 5m |
| 2026-04-29 | PRVHB | - | Apr 29, 02:20 UTC | Apr 29, 02:50 UTC | 30m |
| 2026-04-28 | PRVHB | - | Apr 28, 18:55 UTC | Apr 28, 19:30 UTC | 35m |
| 2026-04-22 | PRVHB | - | Apr 22, 17:40 UTC | Apr 22, 18:10 UTC | 30m |
| 2026-04-20 | PRVHB | - | Apr 20, 18:10 UTC | Apr 20, 18:25 UTC | 15m |
| 2026-04-18 | PRVHB | - | Apr 18, 17:20 UTC | Apr 18, 18:00 UTC | 40m |
| 2026-04-18 | PRVHB | - | Apr 18, 11:30 UTC | Apr 18, 16:25 UTC | 4h 55m |
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 PR-VHB page for operator, model, and routing details .