sensors Mode-S transponder
E480DB
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PR-GGK · BOEING 737-800
- Hex
- E480DB
- Octal
- 71100333
- Decimal
- 14,975,195
- Country
- BR
- Tail
- PR-GGK
- Type
- B738
- Flights observed
- 75
- Distinct callsigns
- 20
- Country
- BR
- Last broadcast
- 1h ago
Current position
Country allocation
The ICAO 24-bit address E480DB 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 |
|---|---|---|---|
| GLO9618 | - | 14 | 2026-05-15 |
| GLO9610 | - | 10 | 2026-05-29 |
| GLO9603 | - | 8 | 2026-05-07 |
| GLO9617 | - | 6 | 2026-05-19 |
| GLO9616 | Gol Linhas Aéreas Inteligentes | 5 | 2026-05-19 |
| GLO9637 | Gol Linhas Aéreas Inteligentes | 3 | 2026-05-29 |
| GLO9632 | Gol Linhas Aéreas Inteligentes | 3 | 2026-05-27 |
| GLO9628 | - | 3 | 2026-05-19 |
| GLO9624 | Gol Linhas Aéreas Inteligentes | 3 | 2026-05-26 |
| GLO9623 | - | 2 | 2026-05-05 |
| GLO9611 | Gol Linhas Aéreas Inteligentes | 2 | 2026-05-18 |
| GLO9604 | - | 2 | 2026-05-23 |
| GLO9601 | - | 2 | 2026-05-22 |
| GLO9600 | Gol Linhas Aéreas Inteligentes | 2 | 2026-05-26 |
| GLO9640 | Gol Linhas Aéreas Inteligentes | 1 | 2026-04-21 |
| GLO9636 | Gol Linhas Aéreas Inteligentes | 1 | 2026-05-16 |
| GLO9635 | Gol Linhas Aéreas Inteligentes | 1 | 2026-04-27 |
| GLO9634 | Gol Linhas Aéreas Inteligentes | 1 | 2026-04-27 |
| GLO9626 | - | 1 | 2026-05-17 |
| GLO9613 | - | 1 | 2026-05-13 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-29 | GLO9610 | - | May 29, 19:00 UTC | May 30, 06:00 UTC | 11h 0m |
| 2026-05-29 | GLO9637 | BSB → GRU | May 29, 10:25 UTC | May 29, 14:55 UTC | 4h 30m |
| 2026-05-29 | GLO9610 | - | May 29, 05:10 UTC | May 29, 07:20 UTC | 2h 10m |
| 2026-05-28 | GLO9610 | - | May 28, 19:05 UTC | May 28, 22:00 UTC | 2h 55m |
| 2026-05-28 | GLO9637 | BSB → GRU | May 28, 10:15 UTC | May 28, 15:00 UTC | 4h 45m |
| 2026-05-27 | GLO9610 | - | May 27, 19:05 UTC | May 28, 07:25 UTC | 12h 20m |
| 2026-05-27 | GLO9632 | GRU → REC | May 27, 07:50 UTC | May 27, 15:35 UTC | 7h 45m |
| 2026-05-26 | GLO9624 | GRU → JPA | May 26, 16:55 UTC | May 27, 00:44 UTC | 7h 50m |
| 2026-05-26 | GLO9600 | GRU → GYN | May 26, 07:59 UTC | May 26, 13:04 UTC | 5h 5m |
| 2026-05-23 | GLO9604 | - | May 23, 08:50 UTC | May 23, 13:20 UTC | 4h 30m |
| 2026-05-22 | GLO9601 | - | May 22, 07:50 UTC | May 22, 12:40 UTC | 4h 50m |
| 2026-05-20 | GLO9610 | - | May 20, 19:05 UTC | May 21, 08:05 UTC | 13h 0m |
| 2026-05-20 | GLO9608 | - | May 20, 09:45 UTC | May 20, 15:10 UTC | 5h 25m |
| 2026-05-19 | GLO9628 | - | May 19, 19:50 UTC | May 20, 06:20 UTC | 10h 31m |
| 2026-05-19 | GLO9617 | - | May 19, 14:15 UTC | May 19, 15:30 UTC | 1h 15m |
| 2026-05-19 | GLO9616 | GRU → VIX | May 19, 11:10 UTC | May 19, 12:15 UTC | 1h 5m |
| 2026-05-18 | GLO9611 | BEL → GRU | May 18, 13:05 UTC | May 18, 14:45 UTC | 1h 40m |
| 2026-05-18 | GLO9611 | BEL → GRU | May 18, 08:20 UTC | May 18, 11:25 UTC | 3h 5m |
| 2026-05-17 | GLO9626 | - | May 17, 17:50 UTC | May 18, 02:10 UTC | 8h 20m |
| 2026-05-16 | GLO9628 | - | May 16, 19:45 UTC | May 17, 06:15 UTC | 10h 30m |
| 2026-05-16 | GLO9636 | GRU → BSB | May 16, 08:20 UTC | May 16, 14:55 UTC | 6h 35m |
| 2026-05-15 | GLO9618 | - | May 15, 14:50 UTC | May 15, 17:55 UTC | 3h 5m |
| 2026-05-15 | GLO9618 | - | May 15, 08:50 UTC | May 15, 13:05 UTC | 4h 15m |
| 2026-05-14 | GLO9618 | - | May 14, 15:25 UTC | May 14, 18:20 UTC | 2h 55m |
| 2026-05-14 | GLO9618 | - | May 14, 08:45 UTC | May 14, 12:55 UTC | 4h 10m |
| 2026-05-13 | GLO9613 | - | May 13, 09:40 UTC | May 13, 16:10 UTC | 6h 30m |
| 2026-05-12 | GLO9628 | - | May 12, 20:05 UTC | May 13, 06:20 UTC | 10h 15m |
| 2026-05-12 | GLO9632 | GRU → REC | May 12, 08:05 UTC | May 12, 15:30 UTC | 7h 25m |
| 2026-05-09 | GLO9637 | BSB → GRU | May 9, 10:10 UTC | May 9, 15:15 UTC | 5h 5m |
| 2026-05-08 | GLO9610 | - | May 8, 19:05 UTC | May 9, 07:30 UTC | 12h 25m |
| 2026-05-08 | GLO9617 | - | May 8, 12:00 UTC | May 8, 13:10 UTC | 1h 10m |
| 2026-05-08 | GLO9616 | GRU → VIX | May 8, 08:40 UTC | May 8, 09:54 UTC | 1h 15m |
| 2026-05-07 | GLO9612 | GRU → SSA | May 7, 10:00 UTC | May 7, 16:10 UTC | 6h 10m |
| 2026-05-07 | GLO9603 | - | May 7, 03:30 UTC | May 7, 06:25 UTC | 2h 55m |
| 2026-05-06 | GLO9603 | - | May 6, 20:45 UTC | May 6, 23:05 UTC | 2h 20m |
| 2026-05-06 | GLO9618 | - | May 6, 14:40 UTC | May 6, 18:05 UTC | 3h 24m |
| 2026-05-06 | GLO9618 | - | May 6, 08:35 UTC | May 6, 12:50 UTC | 4h 15m |
| 2026-05-05 | GLO9610 | - | May 5, 18:55 UTC | May 6, 03:00 UTC | 8h 5m |
| 2026-05-05 | GLO9623 | - | May 5, 08:00 UTC | May 5, 15:30 UTC | 7h 30m |
| 2026-05-02 | GLO9618 | - | May 2, 15:10 UTC | May 2, 18:05 UTC | 2h 55m |
| 2026-05-02 | GLO9618 | - | May 2, 12:40 UTC | May 2, 13:00 UTC | 20m |
| 2026-05-02 | GLO9618 | - | May 2, 08:50 UTC | May 2, 09:40 UTC | 50m |
| 2026-05-01 | GLO9618 | - | May 1, 14:40 UTC | May 1, 17:45 UTC | 3h 5m |
| 2026-05-01 | GLO9618 | - | May 1, 12:30 UTC | May 1, 12:50 UTC | 20m |
| 2026-05-01 | GLO9618 | - | May 1, 08:25 UTC | May 1, 09:20 UTC | 55m |
| 2026-04-29 | GLO9610 | - | Apr 29, 19:20 UTC | Apr 30, 08:15 UTC | 12h 54m |
| 2026-04-28 | GLO9610 | - | Apr 28, 19:30 UTC | Apr 29, 08:15 UTC | 12h 45m |
| 2026-04-28 | GLO9632 | GRU → REC | Apr 28, 07:55 UTC | Apr 28, 15:25 UTC | 7h 30m |
| 2026-04-27 | GLO9635 | CGB → GRU | Apr 27, 13:50 UTC | Apr 27, 15:30 UTC | 1h 40m |
| 2026-04-27 | GLO9634 | GRU → CGB | Apr 27, 10:25 UTC | Apr 27, 11:00 UTC | 35m |
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-GGK page for operator, model, and routing details .