sensors Mode-S transponder
E4A4C7
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-GFI · BOEING 737-800
- Hex
- E4A4C7
- Octal
- 71122307
- Decimal
- 14,984,391
- Country
- BR
- Tail
- PS-GFI
- Type
- B738
- Flights observed
- 56
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- 7h ago
Current position
Country allocation
The ICAO 24-bit address E4A4C7 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 20 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| GLO9603 | - | 7 | 2026-05-21 |
| GLO9632 | Gol Linhas Aéreas Inteligentes | 6 | 2026-05-28 |
| GLO9609 | - | 6 | 2026-04-29 |
| GLO9626 | - | 5 | 2026-05-19 |
| GLO9608 | - | 5 | 2026-04-29 |
| GLO9605 | - | 5 | 2026-05-29 |
| GLO9604 | - | 5 | 2026-05-27 |
| GLO9625 | Gol Linhas Aéreas Inteligentes | 3 | 2026-06-02 |
| GLO9617 | - | 2 | 2026-05-13 |
| GLO9616 | Gol Linhas Aéreas Inteligentes | 2 | 2026-05-13 |
| GLO9636 | Gol Linhas Aéreas Inteligentes | 1 | 2026-05-19 |
| GLO9627 | - | 1 | 2026-04-24 |
| GLO9624 | Gol Linhas Aéreas Inteligentes | 1 | 2026-04-30 |
| GLO9619 | - | 1 | 2026-05-04 |
| GLO9613 | - | 1 | 2026-05-21 |
| GLO9611 | Gol Linhas Aéreas Inteligentes | 1 | 2026-05-30 |
| GLO9601 | - | 1 | 2026-06-02 |
| GLO9600 | Gol Linhas Aéreas Inteligentes | 1 | 2026-04-30 |
| GLO1969 | Gol Linhas Aéreas Inteligentes | 1 | 2026-05-04 |
| G39637 | Gol Linhas Aéreas Inteligentes | 1 | 2026-05-12 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-02 | GLO9625 | SLZ → GRU | Jun 2, 16:55 UTC | Jun 3, 01:15 UTC | 8h 20m |
| 2026-06-02 | GLO9601 | - | Jun 2, 07:50 UTC | Jun 2, 13:30 UTC | 5h 40m |
| 2026-05-30 | GLO9611 | BEL → GRU | May 30, 07:50 UTC | May 30, 18:45 UTC | 10h 55m |
| 2026-05-29 | GLO9625 | SLZ → GRU | May 29, 16:55 UTC | May 30, 00:55 UTC | 8h 0m |
| 2026-05-29 | GLO9605 | - | May 29, 08:55 UTC | May 29, 13:45 UTC | 4h 50m |
| 2026-05-28 | GLO9632 | GRU → REC | May 28, 08:00 UTC | May 28, 15:40 UTC | 7h 40m |
| 2026-05-27 | GLO9604 | - | May 27, 08:50 UTC | May 27, 13:30 UTC | 4h 40m |
| 2026-05-26 | GLO9605 | - | May 26, 08:50 UTC | May 26, 13:29 UTC | 4h 40m |
| 2026-05-21 | GLO9613 | - | May 21, 09:35 UTC | May 21, 16:10 UTC | 6h 35m |
| 2026-05-21 | GLO9603 | - | May 21, 03:20 UTC | May 21, 06:20 UTC | 3h 0m |
| 2026-05-20 | GLO9603 | - | May 20, 20:45 UTC | May 20, 23:15 UTC | 2h 30m |
| 2026-05-20 | GLO9632 | GRU → REC | May 20, 08:00 UTC | May 20, 15:35 UTC | 7h 35m |
| 2026-05-19 | GLO9626 | - | May 19, 18:00 UTC | May 20, 02:05 UTC | 8h 5m |
| 2026-05-19 | GLO9636 | GRU → BSB | May 19, 10:50 UTC | May 19, 15:00 UTC | 4h 10m |
| 2026-05-16 | GLO9632 | GRU → REC | May 16, 08:01 UTC | May 16, 15:20 UTC | 7h 20m |
| 2026-05-15 | GLO9626 | - | May 15, 17:50 UTC | May 16, 02:10 UTC | 8h 20m |
| 2026-05-15 | GLO9632 | GRU → REC | May 15, 07:50 UTC | May 15, 15:30 UTC | 7h 39m |
| 2026-05-14 | GLO9626 | - | May 14, 18:05 UTC | May 15, 02:00 UTC | 7h 55m |
| 2026-05-14 | GLO9632 | GRU → REC | May 14, 08:00 UTC | May 14, 15:25 UTC | 7h 25m |
| 2026-05-13 | GLO9625 | SLZ → GRU | May 13, 17:00 UTC | May 14, 00:50 UTC | 7h 50m |
| 2026-05-13 | GLO9617 | - | May 13, 12:30 UTC | May 13, 14:05 UTC | 1h 35m |
| 2026-05-13 | GLO9616 | GRU → VIX | May 13, 09:00 UTC | May 13, 10:00 UTC | 1h 0m |
| 2026-05-12 | G39637 | BSB → GRU | May 12, 08:15 UTC | May 12, 17:45 UTC | 9h 30m |
| 2026-05-07 | GLO9617 | - | May 7, 12:30 UTC | May 7, 13:45 UTC | 1h 15m |
| 2026-05-07 | GLO9616 | GRU → VIX | May 7, 09:20 UTC | May 7, 10:25 UTC | 1h 5m |
| 2026-05-06 | GLO9604 | - | May 6, 13:40 UTC | May 6, 18:15 UTC | 4h 34m |
| 2026-05-04 | GLO1969 | POA → GRU | May 4, 10:10 UTC | May 4, 16:45 UTC | 6h 35m |
| 2026-05-04 | GLO9619 | - | May 4, 07:55 UTC | May 4, 09:00 UTC | 1h 5m |
| 2026-05-01 | GLO9603 | - | May 1, 20:45 UTC | May 2, 06:10 UTC | 9h 25m |
| 2026-04-30 | GLO9624 | GRU → JPA | Apr 30, 16:55 UTC | May 1, 01:55 UTC | 9h 0m |
| 2026-04-30 | GLO9600 | GRU → GYN | Apr 30, 08:05 UTC | Apr 30, 13:10 UTC | 5h 5m |
| 2026-04-29 | GLO9609 | - | Apr 29, 14:45 UTC | Apr 29, 15:20 UTC | 35m |
| 2026-04-29 | GLO9608 | - | Apr 29, 09:15 UTC | Apr 29, 09:55 UTC | 40m |
| 2026-04-28 | GLO9609 | - | Apr 28, 15:00 UTC | Apr 28, 15:50 UTC | 50m |
| 2026-04-28 | GLO9608 | - | Apr 28, 10:10 UTC | Apr 28, 10:45 UTC | 35m |
| 2026-04-25 | GLO9609 | - | Apr 25, 15:15 UTC | Apr 25, 15:50 UTC | 35m |
| 2026-04-25 | GLO9608 | - | Apr 25, 09:45 UTC | Apr 25, 10:15 UTC | 30m |
| 2026-04-24 | GLO9627 | - | Apr 24, 01:15 UTC | Apr 24, 03:00 UTC | 1h 45m |
| 2026-04-23 | GLO9626 | - | Apr 23, 17:55 UTC | Apr 23, 18:50 UTC | 55m |
| 2026-04-23 | GLO9632 | GRU → REC | Apr 23, 07:55 UTC | Apr 23, 15:35 UTC | 7h 40m |
| 2026-04-22 | GLO9626 | - | Apr 22, 18:00 UTC | Apr 23, 02:15 UTC | 8h 15m |
| 2026-04-22 | GLO9609 | - | Apr 22, 13:35 UTC | Apr 22, 15:30 UTC | 1h 55m |
| 2026-04-22 | GLO9608 | - | Apr 22, 08:50 UTC | Apr 22, 09:30 UTC | 40m |
| 2026-04-21 | GLO9609 | - | Apr 21, 09:40 UTC | Apr 21, 15:25 UTC | 5h 45m |
| 2026-04-18 | GLO9609 | - | Apr 18, 14:00 UTC | Apr 18, 15:35 UTC | 1h 35m |
| 2026-04-18 | GLO9608 | - | Apr 18, 08:45 UTC | Apr 18, 09:30 UTC | 45m |
| 2026-04-16 | GLO9605 | - | Apr 16, 13:50 UTC | Apr 16, 14:30 UTC | 40m |
| 2026-04-16 | GLO9604 | - | Apr 16, 09:39 UTC | Apr 16, 10:29 UTC | 50m |
| 2026-04-16 | GLO9603 | - | Apr 16, 05:24 UTC | Apr 16, 06:10 UTC | 45m |
| 2026-04-16 | GLO9603 | - | Apr 16, 03:24 UTC | Apr 16, 04:54 UTC | 1h 30m |
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-GFI page for operator, model, and routing details .