sensors Mode-S transponder
E4A061
ICAO 24-bit transponder address · allocated to Brazil
Currently assigned to PS-TLF · BOEING 737-400
- Hex
- E4A061
- Octal
- 71120141
- Decimal
- 14,983,265
- Country
- BR
- Tail
- PS-TLF
- Type
- B734
- Flights observed
- 46
- Distinct callsigns
- 8
- Country
- BR
- Last broadcast
- 1h ago
Last known position
Country allocation
The ICAO 24-bit address E4A061 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 8 distinct
Recent flights last 46
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-05-13 | TTL5688 | - | May 13, 04:05 UTC | May 13, 04:55 UTC | 50m |
| 2026-05-12 | TTL5689 | - | May 12, 11:30 UTC | May 12, 11:40 UTC | 10m |
| 2026-05-12 | TTL5689 | - | May 12, 09:55 UTC | May 12, 10:25 UTC | 30m |
| 2026-05-12 | TTL5684 | - | May 12, 04:10 UTC | May 12, 04:45 UTC | 35m |
| 2026-05-09 | TOT5685 | - | May 9, 07:30 UTC | May 9, 08:30 UTC | 1h 0m |
| 2026-05-09 | TTL5688 | - | May 9, 04:00 UTC | May 9, 04:55 UTC | 55m |
| 2026-05-09 | - | - | May 9, 02:55 UTC | May 9, 03:05 UTC | 10m |
| 2026-05-08 | TTL5689 | - | May 8, 10:35 UTC | May 8, 10:44 UTC | 10m |
| 2026-05-08 | TTL5689 | - | May 8, 09:09 UTC | May 8, 09:39 UTC | 30m |
| 2026-05-08 | TTL5688 | - | May 8, 04:09 UTC | May 8, 05:00 UTC | 50m |
| 2026-05-08 | TTL5688 | - | May 8, 02:44 UTC | May 8, 02:59 UTC | 15m |
| 2026-05-07 | TTL5689 | - | May 7, 10:20 UTC | May 7, 10:55 UTC | 35m |
| 2026-05-07 | TTL5688 | - | May 7, 03:50 UTC | May 7, 04:45 UTC | 55m |
| 2026-05-06 | TTL5689 | - | May 6, 11:30 UTC | May 6, 11:40 UTC | 10m |
| 2026-05-06 | TTL5689 | - | May 6, 09:45 UTC | May 6, 10:20 UTC | 35m |
| 2026-05-06 | TTL5688 | - | May 6, 04:00 UTC | May 6, 04:55 UTC | 55m |
| 2026-05-06 | TTL5688 | - | May 6, 02:50 UTC | May 6, 03:00 UTC | 10m |
| 2026-05-05 | 360 | - | May 5, 09:10 UTC | May 5, 09:45 UTC | 35m |
| 2026-05-05 | TOT5688 | - | May 5, 04:00 UTC | May 5, 05:05 UTC | 1h 5m |
| 2026-04-30 | TTL5689 | - | Apr 30, 12:00 UTC | Apr 30, 12:30 UTC | 30m |
| 2026-04-30 | TTL5684 | - | Apr 30, 04:10 UTC | Apr 30, 04:50 UTC | 40m |
| 2026-04-29 | TTL5684 | - | Apr 29, 08:40 UTC | Apr 30, 04:50 UTC | 20h 10m |
| 2026-04-29 | TTL5684 | - | Apr 29, 03:55 UTC | Apr 29, 04:29 UTC | 35m |
| 2026-04-28 | TTL5684 | - | Apr 28, 08:20 UTC | Apr 29, 04:29 UTC | 20h 10m |
| 2026-04-28 | TTL5685 | - | Apr 28, 07:25 UTC | Apr 29, 04:29 UTC | 21h 5m |
| 2026-04-28 | TTL5684 | - | Apr 28, 04:10 UTC | Apr 28, 04:50 UTC | 40m |
| 2026-04-25 | TTL5685 | - | Apr 25, 07:55 UTC | Apr 25, 08:40 UTC | 45m |
| 2026-04-25 | TTL5684 | - | Apr 25, 04:05 UTC | Apr 25, 04:40 UTC | 35m |
| 2026-04-24 | TTL5684 | - | Apr 24, 08:20 UTC | Apr 25, 04:40 UTC | 20h 20m |
| 2026-04-24 | TTL5684 | - | Apr 24, 08:05 UTC | Apr 25, 04:40 UTC | 20h 35m |
| 2026-04-24 | TTL5688 | - | Apr 24, 04:15 UTC | Apr 24, 05:00 UTC | 45m |
| 2026-04-24 | TTL5688 | - | Apr 24, 02:45 UTC | Apr 24, 02:55 UTC | 10m |
| 2026-04-23 | TTL5689 | - | Apr 23, 10:05 UTC | Apr 23, 10:40 UTC | 35m |
| 2026-04-23 | TTL5688 | - | Apr 23, 04:05 UTC | Apr 23, 05:00 UTC | 55m |
| 2026-04-18 | TTL5689 | - | Apr 18, 09:45 UTC | Apr 18, 10:00 UTC | 15m |
| 2026-04-18 | TTL5689 | - | Apr 18, 08:05 UTC | Apr 18, 09:00 UTC | 55m |
| 2026-04-18 | TTL5688 | - | Apr 18, 04:45 UTC | Apr 18, 04:55 UTC | 10m |
| 2026-04-18 | TTL5688 | - | Apr 18, 04:05 UTC | Apr 18, 04:55 UTC | 50m |
| 2026-04-17 | 5689 | - | Apr 17, 08:35 UTC | Apr 17, 09:10 UTC | 35m |
| 2026-04-17 | TTL5684 | - | Apr 17, 04:25 UTC | Apr 17, 04:50 UTC | 26m |
| 2026-04-16 | TTL5685 | - | Apr 16, 08:24 UTC | Apr 16, 08:50 UTC | 25m |
| 2026-04-16 | TTL5684 | - | Apr 16, 04:10 UTC | Apr 16, 04:40 UTC | 30m |
| 2026-04-15 | TTL5685 | - | Apr 15, 07:45 UTC | Apr 15, 08:30 UTC | 45m |
| 2026-04-15 | TTL5684 | - | Apr 15, 05:00 UTC | Apr 15, 05:10 UTC | 10m |
| 2026-04-15 | TTL5684 | - | Apr 15, 04:25 UTC | Apr 15, 04:50 UTC | 25m |
| 2026-04-14 | TTL5685 | - | Apr 14, 09:30 UTC | Apr 14, 10:30 UTC | 1h 0m |
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-TLF page for operator, model, and routing details .