sensors Mode-S transponder
E4961C
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-FPG · EMBRAER EMB545 Praetor 500
- Hex
- E4961C
- Octal
- 71113034
- Decimal
- 14,980,636
- Country
- BR
- Tail
- PS-FPG
- Type
- E545
- Flights observed
- 52
- Distinct callsigns
- 1
- Country
- BR
- Last broadcast
- 1d ago
Last known position
Country allocation
The ICAO 24-bit address E4961C 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 |
|---|---|---|---|
| PSFPG | - | 52 | 2026-05-28 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-28 | PSFPG | - | May 28, 19:05 UTC | May 28, 19:35 UTC | 30m |
| 2026-05-28 | PSFPG | - | May 28, 10:10 UTC | May 28, 11:05 UTC | 55m |
| 2026-05-27 | PSFPG | - | May 27, 15:05 UTC | May 28, 11:05 UTC | 20h 0m |
| 2026-05-27 | PSFPG | - | May 27, 14:35 UTC | May 28, 11:05 UTC | 20h 30m |
| 2026-05-27 | PSFPG | - | May 27, 13:20 UTC | May 27, 14:10 UTC | 50m |
| 2026-05-23 | PSFPG | - | May 23, 23:25 UTC | May 23, 23:55 UTC | 30m |
| 2026-05-23 | PSFPG | - | May 23, 10:50 UTC | May 23, 21:00 UTC | 10h 11m |
| 2026-05-21 | PSFPG | - | May 21, 10:30 UTC | May 21, 20:00 UTC | 9h 30m |
| 2026-05-20 | PSFPG | - | May 20, 14:55 UTC | May 21, 09:55 UTC | 19h 0m |
| 2026-05-16 | PSFPG | - | May 16, 10:35 UTC | May 16, 11:01 UTC | 25m |
| 2026-05-15 | PSFPG | - | May 15, 21:30 UTC | May 15, 21:50 UTC | 20m |
| 2026-05-15 | PSFPG | - | May 15, 12:00 UTC | May 15, 20:25 UTC | 8h 24m |
| 2026-05-15 | PSFPG | - | May 15, 11:05 UTC | May 15, 11:45 UTC | 40m |
| 2026-05-13 | PSFPG | - | May 13, 13:15 UTC | May 13, 13:45 UTC | 30m |
| 2026-05-13 | PSFPG | - | May 13, 11:35 UTC | May 13, 12:25 UTC | 50m |
| 2026-05-12 | PSFPG | - | May 12, 13:05 UTC | May 13, 12:25 UTC | 23h 20m |
| 2026-05-12 | PSFPG | - | May 12, 12:55 UTC | May 12, 13:25 UTC | 30m |
| 2026-05-12 | PSFPG | - | May 12, 11:45 UTC | May 12, 12:35 UTC | 50m |
| 2026-05-11 | PSFPG | - | May 11, 15:05 UTC | May 12, 12:35 UTC | 21h 31m |
| 2026-05-11 | PSFPG | - | May 11, 13:30 UTC | May 11, 13:50 UTC | 20m |
| 2026-05-10 | PSFPG | - | May 10, 12:00 UTC | May 10, 12:30 UTC | 30m |
| 2026-05-10 | PSFPG | - | May 10, 09:00 UTC | May 10, 09:35 UTC | 35m |
| 2026-05-09 | PSFPG | - | May 9, 11:55 UTC | May 10, 09:35 UTC | 21h 40m |
| 2026-05-07 | PSFPG | CGH → CGH | May 7, 17:20 UTC | May 7, 23:24 UTC | 6h 4m |
| 2026-05-07 | PSFPG | - | May 7, 10:20 UTC | May 7, 15:15 UTC | 4h 55m |
| 2026-05-06 | PSFPG | CGH → CGH | May 6, 18:10 UTC | May 7, 15:15 UTC | 21h 5m |
| 2026-05-06 | PSFPG | - | May 6, 12:10 UTC | May 6, 12:55 UTC | 45m |
| 2026-05-03 | PSFPG | - | May 3, 07:05 UTC | May 3, 09:20 UTC | 2h 15m |
| 2026-04-30 | PSFPG | - | Apr 30, 16:10 UTC | Apr 30, 18:25 UTC | 2h 15m |
| 2026-04-30 | PSFPG | - | Apr 30, 06:55 UTC | Apr 30, 08:00 UTC | 1h 5m |
| 2026-04-29 | PSFPG | - | Apr 29, 11:00 UTC | Apr 29, 11:35 UTC | 35m |
| 2026-04-27 | PSFPG | - | Apr 27, 21:30 UTC | Apr 27, 22:05 UTC | 35m |
| 2026-04-27 | PSFPG | - | Apr 27, 13:05 UTC | Apr 27, 13:20 UTC | 15m |
| 2026-04-27 | PSFPG | - | Apr 27, 11:10 UTC | Apr 27, 11:50 UTC | 40m |
| 2026-04-24 | PSFPG | - | Apr 24, 14:35 UTC | Apr 24, 15:05 UTC | 30m |
| 2026-04-24 | PSFPG | - | Apr 24, 13:25 UTC | Apr 24, 14:05 UTC | 40m |
| 2026-04-23 | PSFPG | - | Apr 23, 14:10 UTC | Apr 23, 14:35 UTC | 25m |
| 2026-04-22 | PSFPG | - | Apr 22, 22:10 UTC | Apr 23, 13:40 UTC | 15h 30m |
| 2026-04-22 | PSFPG | - | Apr 22, 10:25 UTC | Apr 22, 21:45 UTC | 11h 20m |
| 2026-04-22 | PSFPG | CGH → CGH | Apr 22, 09:45 UTC | Apr 22, 09:50 UTC | 5m |
| 2026-04-22 | PSFPG | - | Apr 22, 09:00 UTC | Apr 22, 09:40 UTC | 40m |
| 2026-04-17 | PSFPG | - | Apr 17, 11:45 UTC | Apr 17, 12:15 UTC | 30m |
| 2026-04-17 | PSFPG | CGH → CGH | Apr 17, 10:30 UTC | Apr 17, 10:35 UTC | 5m |
| 2026-04-16 | PSFPG | - | Apr 16, 20:30 UTC | Apr 16, 21:10 UTC | 40m |
| 2026-04-15 | PSFPG | - | Apr 15, 10:00 UTC | Apr 15, 10:30 UTC | 30m |
| 2026-04-15 | PSFPG | CGH → CGH | Apr 15, 09:30 UTC | Apr 15, 09:35 UTC | 5m |
| 2026-04-14 | PSFPG | - | Apr 14, 11:35 UTC | Apr 14, 12:25 UTC | 50m |
| 2026-04-14 | PSFPG | - | Apr 14, 09:45 UTC | Apr 14, 10:10 UTC | 25m |
| 2026-04-13 | PSFPG | - | Apr 13, 21:50 UTC | Apr 13, 22:35 UTC | 45m |
| 2026-04-13 | PSFPG | - | Apr 13, 17:00 UTC | Apr 13, 17:45 UTC | 45m |
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 PS-FPG page for operator, model, and routing details .