sensors Mode-S transponder
E48184
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PT-OKP · CESSNA 550 Citation S2
- Hex
- E48184
- Octal
- 71100604
- Decimal
- 14,975,364
- Country
- BR
- Tail
- PT-OKP
- Type
- C550
- Flights observed
- 56
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- Jul 26, 18:40 UTC
Last known position
Country allocation
The ICAO 24-bit address E48184 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 |
|---|---|---|---|
| PTOKP | - | 56 | 2026-07-25 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-25 | PTOKP | - | Jul 25, 23:05 UTC | Jul 26, 18:40 UTC | 19h 36m |
| 2026-07-25 | PTOKP | - | Jul 25, 22:30 UTC | Jul 26, 18:40 UTC | 20h 11m |
| 2026-07-25 | PTOKP | - | Jul 25, 09:40 UTC | Jul 25, 10:30 UTC | 50m |
| 2026-07-24 | PTOKP | - | Jul 24, 13:55 UTC | Jul 25, 10:30 UTC | 20h 35m |
| 2026-07-18 | PTOKP | - | Jul 18, 02:00 UTC | Jul 18, 10:35 UTC | 8h 36m |
| 2026-07-17 | PTOKP | - | Jul 17, 10:44 UTC | Jul 17, 11:00 UTC | 15m |
| 2026-07-06 | PTOKP | - | Jul 6, 11:30 UTC | Jul 6, 11:55 UTC | 25m |
| 2026-07-06 | PTOKP | - | Jul 6, 03:15 UTC | Jul 6, 03:40 UTC | 25m |
| 2026-07-05 | PTOKP | - | Jul 5, 11:00 UTC | Jul 5, 11:45 UTC | 45m |
| 2026-07-03 | PTOKP | - | Jul 3, 21:25 UTC | Jul 3, 22:00 UTC | 35m |
| 2026-07-02 | PTOKP | - | Jul 2, 07:05 UTC | Jul 2, 07:40 UTC | 35m |
| 2026-07-02 | PTOKP | - | Jul 2, 00:40 UTC | Jul 2, 01:10 UTC | 30m |
| 2026-06-30 | PTOKP | - | Jun 30, 09:35 UTC | Jun 30, 10:35 UTC | 1h 0m |
| 2026-06-20 | PTOKP | - | Jun 20, 20:14 UTC | Jun 20, 20:45 UTC | 30m |
| 2026-06-18 | PTOKP | - | Jun 18, 19:40 UTC | Jun 18, 20:05 UTC | 25m |
| 2026-06-14 | PTOKP | - | Jun 14, 09:10 UTC | Jun 14, 09:55 UTC | 45m |
| 2026-06-14 | PTOKP | - | Jun 14, 03:05 UTC | Jun 14, 03:50 UTC | 45m |
| 2026-06-09 | PTOKP | - | Jun 9, 17:55 UTC | Jun 9, 18:30 UTC | 35m |
| 2026-06-05 | PTOKP | - | Jun 5, 19:00 UTC | Jun 5, 19:30 UTC | 30m |
| 2026-06-01 | PTOKP | - | Jun 1, 08:30 UTC | Jun 1, 09:00 UTC | 30m |
| 2026-05-30 | PTOKP | - | May 30, 23:40 UTC | May 31, 00:05 UTC | 25m |
| 2026-05-30 | PTOKP | - | May 30, 02:40 UTC | May 30, 03:40 UTC | 1h 0m |
| 2026-05-27 | PTOKP | - | May 27, 08:05 UTC | May 27, 11:35 UTC | 3h 30m |
| 2026-05-26 | PTOKP | - | May 26, 22:05 UTC | May 26, 22:39 UTC | 35m |
| 2026-05-26 | PTOKP | - | May 26, 15:00 UTC | May 26, 16:30 UTC | 1h 30m |
| 2026-05-26 | PTOKP | - | May 26, 11:15 UTC | May 26, 12:50 UTC | 1h 35m |
| 2026-05-15 | PTOKP | IMP → FOR | May 15, 06:05 UTC | May 15, 08:05 UTC | 2h 0m |
| 2026-05-13 | PTOKP | - | May 13, 23:40 UTC | May 13, 23:55 UTC | 15m |
| 2026-05-13 | PTOKP | - | May 13, 22:10 UTC | May 13, 22:45 UTC | 35m |
| 2026-05-13 | PTOKP | IMP → FOR | May 13, 10:30 UTC | May 13, 12:25 UTC | 1h 55m |
| 2026-05-13 | PTOKP | - | May 13, 09:25 UTC | May 13, 09:45 UTC | 20m |
| 2026-05-12 | PTOKP | - | May 12, 23:30 UTC | May 13, 01:40 UTC | 2h 10m |
| 2026-05-11 | PTOKP | - | May 11, 11:15 UTC | May 11, 11:45 UTC | 30m |
| 2026-05-10 | PTOKP | - | May 10, 22:35 UTC | May 10, 23:39 UTC | 1h 5m |
| 2026-05-10 | PTOKP | - | May 10, 02:50 UTC | May 10, 23:39 UTC | 20h 50m |
| 2026-05-10 | PTOKP | - | May 10, 01:14 UTC | May 10, 02:45 UTC | 1h 30m |
| 2026-05-03 | PTOKP | - | May 3, 07:45 UTC | May 3, 08:15 UTC | 30m |
| 2026-05-02 | PTOKP | - | May 2, 23:55 UTC | May 3, 00:30 UTC | 35m |
| 2026-05-01 | PTOKP | - | May 1, 10:10 UTC | May 1, 10:25 UTC | 15m |
| 2026-05-01 | PTOKP | - | May 1, 03:50 UTC | May 1, 04:15 UTC | 25m |
| 2026-04-29 | PTOKP | - | Apr 29, 19:40 UTC | Apr 30, 07:25 UTC | 11h 44m |
| 2026-04-28 | PTOKP | - | Apr 28, 21:25 UTC | Apr 29, 06:39 UTC | 9h 15m |
| 2026-04-26 | PTOKP | - | Apr 26, 09:10 UTC | Apr 26, 09:25 UTC | 15m |
| 2026-04-23 | PTOKP | - | Apr 23, 19:35 UTC | Apr 23, 20:10 UTC | 35m |
| 2026-04-19 | PTOKP | - | Apr 19, 06:50 UTC | Apr 19, 07:15 UTC | 25m |
| 2026-04-18 | PTOKP | - | Apr 18, 08:00 UTC | Apr 18, 08:45 UTC | 45m |
| 2026-04-17 | PTOKP | - | Apr 17, 23:25 UTC | Apr 18, 00:35 UTC | 1h 10m |
| 2026-04-17 | PTOKP | - | Apr 17, 23:10 UTC | Apr 17, 23:20 UTC | 10m |
| 2026-04-17 | PTOKP | - | Apr 17, 04:10 UTC | Apr 17, 04:35 UTC | 26m |
| 2026-04-16 | PTOKP | - | Apr 16, 23:20 UTC | Apr 16, 23:30 UTC | 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 PT-OKP page for operator, model, and routing details .