sensors Mode-S transponder
742AC2
ICAO 24-bit transponder address · allocated to Jordan
Currently assigned to JY-JVB · AIRBUS A-330-200
- Hex
- 742AC2
- Octal
- 35025302
- Decimal
- 7,613,122
- Country
- JO
- Tail
- JY-JVB
- Type
- A332
- Flights observed
- 50
- Distinct callsigns
- 20
- Country
- JO
- Last broadcast
- 6h ago
Last known position
Country allocation
The ICAO 24-bit address 742AC2 falls within the block assigned to Jordan (JO) by ICAO Annex 10, Volume III. Every aircraft registered in Jordan 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 |
|---|---|---|---|
| FAD6410 | - | 5 | 2026-04-20 |
| FAD6419 | Rog-Air | 4 | 2026-04-25 |
| FAD6083 | Rog-Air | 3 | 2026-05-14 |
| FAD6079 | - | 3 | 2026-05-12 |
| FAD6073 | - | 3 | 2026-05-10 |
| FAD7412 | Rog-Air | 2 | 2026-06-01 |
| FAD7404 | Rog-Air | 2 | 2026-06-02 |
| FAD6422 | - | 2 | 2026-04-25 |
| FAD6089 | - | 2 | 2026-05-16 |
| FAD6086 | - | 2 | 2026-05-15 |
| FAD6085 | - | 2 | 2026-05-14 |
| FAD6074 | - | 2 | 2026-05-09 |
| FAD8521 | - | 1 | 2026-04-15 |
| FAD7423 | - | 1 | 2026-06-01 |
| FAD7419 | - | 1 | 2026-06-01 |
| FAD7418 | Rog-Air | 1 | 2026-05-31 |
| FAD7409 | - | 1 | 2026-06-03 |
| FAD7408 | Rog-Air | 1 | 2026-06-03 |
| FAD7406 | Rog-Air | 1 | 2026-06-02 |
| FAD6500 | - | 1 | 2026-05-09 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-06-03 | FAD7409 | - | Jun 3, 19:40 UTC | Jun 4, 09:10 UTC | 13h 30m |
| 2026-06-03 | FAD7408 | JED → YEI | Jun 3, 06:35 UTC | Jun 3, 18:20 UTC | 11h 45m |
| 2026-06-02 | FAD7406 | JED → YEI | Jun 2, 19:25 UTC | Jun 3, 04:35 UTC | 9h 10m |
| 2026-06-02 | FAD7404 | JED → YEI | Jun 2, 01:20 UTC | Jun 2, 17:00 UTC | 15h 40m |
| 2026-06-01 | FAD7404 | JED → YEI | Jun 1, 18:35 UTC | Jun 2, 17:00 UTC | 22h 25m |
| 2026-06-01 | FAD7412 | JED → ESB | Jun 1, 18:25 UTC | Jun 2, 16:30 UTC | 22h 5m |
| 2026-06-01 | FAD7412 | JED → ESB | Jun 1, 14:25 UTC | Jun 2, 07:00 UTC | 16h 35m |
| 2026-06-01 | FAD7423 | - | Jun 1, 02:35 UTC | Jun 2, 02:30 UTC | 23h 55m |
| 2026-06-01 | FAD7419 | - | Jun 1, 02:00 UTC | Jun 1, 19:45 UTC | 17h 45m |
| 2026-05-31 | FAD7418 | JED → ADB | May 31, 21:45 UTC | May 31, 23:20 UTC | 1h 35m |
| 2026-05-20 | FAD6460 | - | May 20, 04:55 UTC | May 20, 05:20 UTC | 25m |
| 2026-05-17 | FAD6091 | - | May 17, 07:10 UTC | May 17, 07:45 UTC | 35m |
| 2026-05-16 | FAD6089 | - | May 16, 11:21 UTC | May 17, 07:45 UTC | 20h 25m |
| 2026-05-15 | FAD6089 | - | May 15, 16:35 UTC | May 16, 11:55 UTC | 19h 21m |
| 2026-05-15 | FAD6087 | - | May 15, 16:00 UTC | May 16, 11:55 UTC | 19h 56m |
| 2026-05-15 | FAD6086 | - | May 15, 07:15 UTC | May 16, 02:30 UTC | 19h 14m |
| 2026-05-14 | FAD6086 | - | May 14, 20:35 UTC | May 15, 16:40 UTC | 20h 4m |
| 2026-05-14 | FAD6085 | - | May 14, 20:25 UTC | May 15, 16:40 UTC | 20h 14m |
| 2026-05-14 | FAD6085 | - | May 14, 11:20 UTC | May 15, 07:55 UTC | 20h 35m |
| 2026-05-14 | FAD6083 | DYU → JED | May 14, 01:25 UTC | May 14, 21:05 UTC | 19h 40m |
| 2026-05-13 | FAD6083 | DYU → JED | May 13, 16:35 UTC | May 14, 11:55 UTC | 19h 20m |
| 2026-05-13 | FAD6083 | DYU → JED | May 13, 16:00 UTC | May 14, 11:55 UTC | 19h 55m |
| 2026-05-12 | FAD6079 | - | May 12, 10:10 UTC | May 12, 10:55 UTC | 45m |
| 2026-05-11 | FAD6079 | - | May 11, 14:35 UTC | May 12, 10:55 UTC | 20h 21m |
| 2026-05-11 | FAD6079 | - | May 11, 14:25 UTC | May 12, 10:55 UTC | 20h 31m |
| 2026-05-10 | FAD6073 | - | May 10, 21:00 UTC | May 11, 15:05 UTC | 18h 5m |
| 2026-05-10 | FAD6073 | - | May 10, 10:40 UTC | May 11, 07:45 UTC | 21h 5m |
| 2026-05-10 | FAD6073 | - | May 10, 00:34 UTC | May 10, 21:40 UTC | 21h 5m |
| 2026-05-10 | FAD6075 | - | May 10, 00:09 UTC | May 10, 21:40 UTC | 21h 30m |
| 2026-05-09 | FAD6074 | - | May 9, 13:45 UTC | May 10, 11:05 UTC | 21h 20m |
| 2026-05-09 | FAD6074 | - | May 9, 04:15 UTC | May 10, 00:49 UTC | 20h 35m |
| 2026-05-09 | FAD6500 | - | May 9, 00:30 UTC | May 9, 01:00 UTC | 30m |
| 2026-05-06 | FAD6109 | - | May 6, 01:30 UTC | May 6, 11:25 UTC | 9h 55m |
| 2026-04-28 | FAD6440 | - | Apr 28, 10:30 UTC | Apr 28, 17:05 UTC | 6h 35m |
| 2026-04-25 | FAD6422 | - | Apr 25, 21:45 UTC | Apr 26, 12:30 UTC | 14h 45m |
| 2026-04-25 | FAD6422 | - | Apr 25, 14:55 UTC | Apr 26, 12:30 UTC | 21h 35m |
| 2026-04-25 | FAD6430 | - | Apr 25, 10:20 UTC | Apr 26, 03:30 UTC | 17h 10m |
| 2026-04-25 | FAD6419 | YEI → MED | Apr 25, 04:45 UTC | Apr 26, 03:30 UTC | 22h 45m |
| 2026-04-25 | FAD6419 | YEI → MED | Apr 25, 00:35 UTC | Apr 25, 23:15 UTC | 22h 40m |
| 2026-04-24 | FAD6419 | YEI → MED | Apr 24, 10:35 UTC | Apr 25, 10:30 UTC | 23h 55m |
| 2026-04-24 | FAD6419 | YEI → MED | Apr 24, 09:15 UTC | Apr 25, 06:20 UTC | 21h 5m |
| 2026-04-24 | FAD6418 | - | Apr 24, 04:35 UTC | Apr 25, 02:00 UTC | 21h 25m |
| 2026-04-20 | FAD6410 | - | Apr 20, 06:15 UTC | Apr 20, 12:20 UTC | 6h 5m |
| 2026-04-19 | FAD6410 | - | Apr 19, 14:35 UTC | Apr 20, 12:20 UTC | 21h 45m |
| 2026-04-19 | FAD6410 | - | Apr 19, 13:35 UTC | Apr 20, 12:20 UTC | 22h 45m |
| 2026-04-19 | FAD6410 | - | Apr 19, 10:35 UTC | Apr 20, 07:50 UTC | 21h 15m |
| 2026-04-19 | FAD6410 | - | Apr 19, 09:45 UTC | Apr 20, 07:50 UTC | 22h 5m |
| 2026-04-18 | FAD6381 | - | Apr 18, 22:55 UTC | Apr 19, 15:00 UTC | 16h 5m |
| 2026-04-18 | FAD6380 | - | Apr 18, 06:45 UTC | Apr 18, 07:20 UTC | 35m |
| 2026-04-15 | FAD8521 | - | Apr 15, 21:20 UTC | Apr 15, 21:30 UTC | 10m |
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 JY-JVB page for operator, model, and routing details .