sensors Mode-S transponder
046C56
ICAO 24-bit transponder address
- Hex
- 046C56
- Octal
- 01066126
- Decimal
- 289,878
No current signal · last broadcast 4d ago
- Flights observed
- 98
- Distinct callsigns
- 1
- Country
- -
- Last broadcast
- 4d ago
Last known position
Callsign history 1 distinct
| Callsign | Airline | Flights | Last seen |
|---|---|---|---|
| LN90LJ | - | 98 | 2026-07-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-09 | LN90LJ | - | Jul 9, 21:45 UTC | Jul 9, 23:25 UTC | 1h 40m |
| 2026-07-09 | LN90LJ | - | Jul 9, 18:10 UTC | Jul 9, 19:30 UTC | 1h 20m |
| 2026-07-09 | LN90LJ | - | Jul 9, 13:35 UTC | Jul 9, 15:05 UTC | 1h 30m |
| 2026-07-08 | LN90LJ | - | Jul 8, 03:00 UTC | Jul 8, 03:35 UTC | 35m |
| 2026-07-07 | LN90LJ | TPA → MIA | Jul 7, 19:05 UTC | Jul 8, 00:20 UTC | 5h 15m |
| 2026-07-07 | LN90LJ | - | Jul 7, 05:00 UTC | Jul 7, 05:35 UTC | 35m |
| 2026-07-07 | LN90LJ | SIG → FLL | Jul 7, 00:55 UTC | Jul 7, 03:15 UTC | 2h 20m |
| 2026-07-06 | LN90LJ | - | Jul 6, 22:20 UTC | Jul 6, 22:30 UTC | 10m |
| 2026-07-06 | LN90LJ | - | Jul 6, 19:50 UTC | Jul 6, 20:40 UTC | 50m |
| 2026-07-03 | LN90LJ | - | Jul 3, 03:50 UTC | Jul 3, 04:25 UTC | 35m |
| 2026-07-03 | LN90LJ | - | Jul 3, 02:45 UTC | Jul 3, 03:10 UTC | 25m |
| 2026-07-03 | LN90LJ | - | Jul 3, 00:00 UTC | Jul 3, 00:40 UTC | 40m |
| 2026-07-02 | LN90LJ | TMB → TPA | Jul 2, 22:15 UTC | Jul 2, 23:00 UTC | 45m |
| 2026-07-02 | LN90LJ | - | Jul 2, 19:40 UTC | Jul 2, 21:15 UTC | 1h 35m |
| 2026-07-02 | LN90LJ | - | Jul 2, 17:00 UTC | Jul 2, 17:30 UTC | 30m |
| 2026-07-02 | LN90LJ | - | Jul 2, 14:50 UTC | Jul 2, 15:10 UTC | 20m |
| 2026-07-02 | LN90LJ | - | Jul 2, 11:45 UTC | Jul 2, 12:25 UTC | 40m |
| 2026-06-30 | LN90LJ | - | Jun 30, 23:35 UTC | Jul 1, 00:10 UTC | 35m |
| 2026-06-30 | LN90LJ | - | Jun 30, 21:50 UTC | Jun 30, 22:15 UTC | 25m |
| 2026-06-30 | LN90LJ | - | Jun 30, 20:05 UTC | Jun 30, 20:40 UTC | 35m |
| 2026-06-29 | LN90LJ | - | Jun 29, 22:44 UTC | Jun 29, 23:25 UTC | 40m |
| 2026-06-29 | LN90LJ | - | Jun 29, 19:54 UTC | Jun 29, 21:19 UTC | 1h 25m |
| 2026-06-29 | LN90LJ | - | Jun 29, 16:35 UTC | Jun 29, 17:59 UTC | 1h 25m |
| 2026-06-26 | LN90LJ | - | Jun 26, 04:10 UTC | Jun 26, 04:45 UTC | 35m |
| 2026-06-26 | LN90LJ | - | Jun 26, 00:45 UTC | Jun 26, 01:20 UTC | 35m |
| 2026-06-25 | LN90LJ | - | Jun 25, 18:45 UTC | Jun 25, 19:29 UTC | 45m |
| 2026-06-23 | LN90LJ | TMB → TPA | Jun 23, 22:10 UTC | Jun 23, 22:49 UTC | 40m |
| 2026-06-23 | LN90LJ | - | Jun 23, 19:59 UTC | Jun 23, 20:24 UTC | 25m |
| 2026-06-23 | LN90LJ | - | Jun 23, 18:34 UTC | Jun 23, 18:55 UTC | 20m |
| 2026-06-23 | LN90LJ | TPA → TMB | Jun 23, 11:24 UTC | Jun 23, 16:29 UTC | 5h 5m |
| 2026-05-19 | LN90LJ | - | May 19, 03:15 UTC | May 19, 03:50 UTC | 35m |
| 2026-05-19 | LN90LJ | - | May 19, 02:20 UTC | May 19, 02:45 UTC | 25m |
| 2026-05-18 | LN90LJ | - | May 18, 23:40 UTC | May 19, 00:20 UTC | 40m |
| 2026-05-18 | LN90LJ | - | May 18, 20:40 UTC | May 18, 21:35 UTC | 55m |
| 2026-05-18 | LN90LJ | - | May 18, 17:35 UTC | May 18, 19:10 UTC | 1h 34m |
| 2026-05-18 | LN90LJ | - | May 18, 14:10 UTC | May 18, 14:50 UTC | 40m |
| 2026-05-14 | LN90LJ | - | May 14, 22:10 UTC | May 14, 22:50 UTC | 40m |
| 2026-05-14 | LN90LJ | TPA → FLL | May 14, 11:20 UTC | May 14, 20:45 UTC | 9h 25m |
| 2026-05-14 | LN90LJ | - | May 14, 02:25 UTC | May 14, 03:00 UTC | 35m |
| 2026-05-14 | LN90LJ | - | May 14, 01:30 UTC | May 14, 02:00 UTC | 30m |
| 2026-05-13 | LN90LJ | - | May 13, 23:25 UTC | May 13, 23:45 UTC | 20m |
| 2026-05-13 | LN90LJ | - | May 13, 15:50 UTC | May 13, 22:15 UTC | 6h 25m |
| 2026-05-12 | LN90LJ | - | May 12, 21:35 UTC | May 13, 16:00 UTC | 18h 25m |
| 2026-05-12 | LN90LJ | - | May 12, 21:15 UTC | May 13, 16:00 UTC | 18h 45m |
| 2026-05-03 | LN90LJ | - | May 3, 16:40 UTC | May 3, 17:20 UTC | 40m |
| 2026-05-03 | LN90LJ | - | May 3, 14:10 UTC | May 3, 14:35 UTC | 25m |
| 2026-05-03 | LN90LJ | - | May 3, 11:35 UTC | May 3, 12:05 UTC | 30m |
| 2026-05-02 | LN90LJ | - | May 2, 22:45 UTC | May 3, 01:10 UTC | 2h 25m |
| 2026-05-02 | LN90LJ | - | May 2, 13:40 UTC | May 2, 21:05 UTC | 7h 25m |
| 2026-04-30 | LN90LJ | - | Apr 30, 00:25 UTC | Apr 30, 01:05 UTC | 40m |
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.
Mode-S 046C56 frequently asked
What is Mode-S code 046C56?
046C56 is an ICAO 24-bit transponder address.
Is 046C56 broadcasting right now?
No active broadcast right now. Last signal was 4d ago.
Hex, octal, and decimal Mode-S codes: what's the difference?
The same 24-bit identifier expressed in different bases: hex 046C56, octal 01066126, decimal 289,878.
What flights does 046C56 operate?
Mode-S 046C56 has broadcast 1 distinct callsign, including LN90LJ.