sensors Mode-S transponder
E49EF3
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-GRF · BOEING 737 MAX 8
- Hex
- E49EF3
- Octal
- 71117363
- Decimal
- 14,982,899
- Country
- BR
- Tail
- PS-GRF
- Type
- B38M
- Flights observed
- 300
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- 48m ago
Current position
Country allocation
The ICAO 24-bit address E49EF3 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 |
|---|---|---|---|
| GLO7635 | - | 8 | 2026-07-05 |
| GLO7634 | Gol Linhas Aéreas Inteligentes | 7 | 2026-06-01 |
| GLO9520 | Gol Linhas Aéreas Inteligentes | 6 | 2026-06-28 |
| GLO9521 | Gol Linhas Aéreas Inteligentes | 5 | 2026-06-29 |
| GLO1733 | Gol Linhas Aéreas Inteligentes | 5 | 2026-05-06 |
| GLO7631 | Gol Linhas Aéreas Inteligentes | 4 | 2026-04-27 |
| GLO2009 | - | 4 | 2026-06-19 |
| GLO1419 | - | 4 | 2026-07-05 |
| GLO1123 | Gol Linhas Aéreas Inteligentes | 4 | 2026-06-04 |
| GLO9442 | - | 3 | 2026-07-04 |
| GLO7749 | - | 3 | 2026-07-08 |
| GLO7748 | - | 3 | 2026-06-20 |
| GLO2008 | Gol Linhas Aéreas Inteligentes | 3 | 2026-04-17 |
| GLO1772 | - | 3 | 2026-07-02 |
| GLO1756 | - | 3 | 2026-07-13 |
| GLO1731 | Gol Linhas Aéreas Inteligentes | 3 | 2026-05-25 |
| GLO1637 | Gol Linhas Aéreas Inteligentes | 3 | 2026-06-09 |
| GLO1615 | - | 3 | 2026-07-03 |
| GLO1112 | - | 3 | 2026-06-23 |
| TAI382 | - | 2 | 2026-07-11 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-13 | GLO1756 | - | Jul 13, 12:45 UTC | Jul 14, 08:45 UTC | 20h 0m |
| 2026-07-13 | GLO1756 | - | Jul 13, 07:30 UTC | Jul 14, 01:55 UTC | 18h 25m |
| 2026-07-13 | GLO1756 | - | Jul 13, 04:50 UTC | Jul 14, 01:55 UTC | 21h 5m |
| 2026-07-13 | GLO8243 | - | Jul 13, 04:40 UTC | Jul 14, 01:55 UTC | 21h 15m |
| 2026-07-12 | TAI383 | BOG → BOG | Jul 12, 09:40 UTC | Jul 12, 16:55 UTC | 7h 15m |
| 2026-07-11 | TAI382 | - | Jul 11, 19:00 UTC | Jul 12, 06:45 UTC | 11h 45m |
| 2026-07-11 | TAI366 | BOG → BOG | Jul 11, 09:45 UTC | Jul 11, 16:40 UTC | 6h 55m |
| 2026-07-11 | TAI365 | - | Jul 11, 05:31 UTC | Jul 11, 07:00 UTC | 1h 30m |
| 2026-07-11 | TAI589 | - | Jul 11, 02:20 UTC | Jul 11, 03:15 UTC | 55m |
| 2026-07-11 | TAI588 | - | Jul 11, 00:00 UTC | Jul 11, 00:20 UTC | 20m |
| 2026-07-10 | TAI382 | - | Jul 10, 19:20 UTC | Jul 10, 21:00 UTC | 1h 40m |
| 2026-07-10 | GLO8242 | - | Jul 10, 08:25 UTC | Jul 10, 17:25 UTC | 9h 0m |
| 2026-07-09 | GLO7607 | - | Jul 9, 23:50 UTC | Jul 10, 00:15 UTC | 25m |
| 2026-07-09 | GLO7606 | - | Jul 9, 20:25 UTC | Jul 9, 22:20 UTC | 1h 55m |
| 2026-07-09 | GLO1256 | CGH → FLN | Jul 9, 18:15 UTC | Jul 9, 19:00 UTC | 45m |
| 2026-07-09 | GLO1749 | - | Jul 9, 08:35 UTC | Jul 9, 15:55 UTC | 7h 20m |
| 2026-07-08 | GLO1748 | - | Jul 8, 20:20 UTC | Jul 9, 01:50 UTC | 5h 30m |
| 2026-07-08 | GLO1628 | - | Jul 8, 14:35 UTC | Jul 8, 19:10 UTC | 4h 35m |
| 2026-07-08 | GLO7749 | - | Jul 8, 02:50 UTC | Jul 8, 13:15 UTC | 10h 25m |
| 2026-07-07 | GLO9448 | - | Jul 7, 09:20 UTC | Jul 7, 22:45 UTC | 13h 25m |
| 2026-07-07 | GLO1885 | - | Jul 7, 06:50 UTC | Jul 7, 08:00 UTC | 1h 10m |
| 2026-07-07 | GLO1396 | - | Jul 7, 01:00 UTC | Jul 7, 01:50 UTC | 50m |
| 2026-07-06 | GLO1513 | - | Jul 6, 19:20 UTC | Jul 6, 22:30 UTC | 3h 10m |
| 2026-07-06 | GLO1510 | - | Jul 6, 15:20 UTC | Jul 6, 18:20 UTC | 3h 0m |
| 2026-07-06 | GLO1309 | - | Jul 6, 09:40 UTC | Jul 6, 13:50 UTC | 4h 10m |
| 2026-07-05 | GLO1419 | - | Jul 5, 21:10 UTC | Jul 6, 01:00 UTC | 3h 50m |
| 2026-07-05 | GLO7635 | - | Jul 5, 02:25 UTC | Jul 5, 15:55 UTC | 13h 30m |
| 2026-07-04 | GLO9442 | - | Jul 4, 12:00 UTC | Jul 4, 23:05 UTC | 11h 5m |
| 2026-07-04 | GLO1553 | - | Jul 4, 06:35 UTC | Jul 4, 09:50 UTC | 3h 15m |
| 2026-07-03 | GLO1268 | - | Jul 3, 23:35 UTC | Jul 4, 02:30 UTC | 2h 55m |
| 2026-07-03 | GLO1651 | - | Jul 3, 20:35 UTC | Jul 3, 22:00 UTC | 1h 25m |
| 2026-07-03 | GLO1348 | GRU → CGR | Jul 3, 18:35 UTC | Jul 3, 19:40 UTC | 1h 5m |
| 2026-07-03 | GLO1615 | - | Jul 3, 15:50 UTC | Jul 3, 16:55 UTC | 1h 5m |
| 2026-07-03 | GLO1995 | - | Jul 3, 07:15 UTC | Jul 3, 07:35 UTC | 20m |
| 2026-07-02 | GLO1772 | - | Jul 2, 17:55 UTC | Jul 3, 02:50 UTC | 8h 55m |
| 2026-07-02 | GLO1457 | - | Jul 2, 12:15 UTC | Jul 2, 16:15 UTC | 4h 0m |
| 2026-07-02 | GLO1545 | - | Jul 2, 01:55 UTC | Jul 2, 10:10 UTC | 8h 15m |
| 2026-07-01 | GLO1624 | - | Jul 1, 10:30 UTC | Jul 2, 00:05 UTC | 13h 35m |
| 2026-06-30 | GLO1419 | - | Jun 30, 21:30 UTC | Jul 1, 01:30 UTC | 4h 0m |
| 2026-06-30 | GLO1934 | - | Jun 30, 19:30 UTC | Jun 30, 20:15 UTC | 45m |
| 2026-06-30 | GLO2173 | - | Jun 30, 15:35 UTC | Jun 30, 15:50 UTC | 15m |
| 2026-06-30 | GLO1778 | - | Jun 30, 12:15 UTC | Jun 30, 13:15 UTC | 1h 0m |
| 2026-06-29 | GLO9521 | MIA → BSB | Jun 29, 16:50 UTC | Jun 30, 13:15 UTC | 20h 25m |
| 2026-06-29 | GLO9521 | MIA → BSB | Jun 29, 14:50 UTC | Jun 30, 13:15 UTC | 22h 25m |
| 2026-06-29 | GLO9521 | MIA → BSB | Jun 29, 14:44 UTC | Jun 30, 12:45 UTC | 22h 1m |
| 2026-06-28 | GLO9520 | BSB → MIA | Jun 28, 15:09 UTC | Jun 29, 09:34 UTC | 18h 25m |
| 2026-06-27 | GLO9520 | BSB → MIA | Jun 27, 15:14 UTC | Jun 28, 09:34 UTC | 18h 20m |
| 2026-06-26 | GLO9521 | MIA → BSB | Jun 26, 15:45 UTC | Jun 27, 09:34 UTC | 17h 50m |
| 2026-06-25 | GLO9520 | BSB → MIA | Jun 25, 15:04 UTC | Jun 26, 09:39 UTC | 18h 35m |
| 2026-06-24 | GLO9520 | BSB → MIA | Jun 24, 14:50 UTC | Jun 25, 09:34 UTC | 18h 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-GRF page for operator, model, and routing details .