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
- 77
- Distinct callsigns
- 20
- Country
- JO
- Last broadcast
- 9h 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 |
| FAD7095 | - | 4 | 2026-06-08 |
| FAD6419 | Rog-Air | 4 | 2026-04-25 |
| FAD7093 | - | 3 | 2026-06-07 |
| FAD6083 | Rog-Air | 3 | 2026-05-14 |
| FAD6079 | - | 3 | 2026-05-12 |
| FAD6073 | - | 3 | 2026-05-10 |
| FAD9135 | - | 2 | 2026-06-18 |
| FAD9133 | - | 2 | 2026-06-17 |
| FAD7420 | Rog-Air | 2 | 2026-06-04 |
| FAD7414 | Rog-Air | 2 | 2026-06-05 |
| FAD7412 | Rog-Air | 2 | 2026-06-01 |
| FAD7404 | Rog-Air | 2 | 2026-06-02 |
| FAD7087 | - | 2 | 2026-06-12 |
| 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 |
| FAD9134 | - | 1 | 2026-07-18 |
Recent flights last 50
| Date | Flight | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|---|
| 2026-07-19 | FAD8819 | - | Jul 19, 09:55 UTC | Jul 19, 10:15 UTC | 20m |
| 2026-07-18 | FAD9134 | - | Jul 18, 01:20 UTC | Jul 18, 09:25 UTC | 8h 6m |
| 2026-06-30 | FAD8130 | - | Jun 30, 20:30 UTC | Jun 30, 20:40 UTC | 10m |
| 2026-06-18 | FAD9135 | - | Jun 18, 06:10 UTC | Jun 18, 15:10 UTC | 9h 0m |
| 2026-06-17 | FAD9135 | - | Jun 17, 18:35 UTC | Jun 18, 15:10 UTC | 20h 35m |
| 2026-06-17 | FAD9133 | - | Jun 17, 18:10 UTC | Jun 18, 15:10 UTC | 21h 0m |
| 2026-06-17 | FAD9133 | - | Jun 17, 09:15 UTC | Jun 18, 06:30 UTC | 21h 15m |
| 2026-06-16 | FAD7425 | - | Jun 16, 05:59 UTC | Jun 16, 07:15 UTC | 1h 15m |
| 2026-06-16 | FAD7424 | - | Jun 16, 02:24 UTC | Jun 16, 03:39 UTC | 1h 15m |
| 2026-06-13 | FAD7089 | - | Jun 13, 20:35 UTC | Jun 13, 21:25 UTC | 50m |
| 2026-06-12 | FAD7087 | - | Jun 12, 02:25 UTC | Jun 12, 12:50 UTC | 10h 25m |
| 2026-06-11 | FAD7087 | - | Jun 11, 17:20 UTC | Jun 12, 12:50 UTC | 19h 31m |
| 2026-06-10 | FAD7083 | - | Jun 10, 07:50 UTC | Jun 10, 16:35 UTC | 8h 45m |
| 2026-06-08 | FAD7095 | - | Jun 8, 12:55 UTC | Jun 9, 05:40 UTC | 16h 45m |
| 2026-06-08 | FAD7095 | - | Jun 8, 02:40 UTC | Jun 8, 22:00 UTC | 19h 20m |
| 2026-06-07 | FAD7095 | - | Jun 7, 18:35 UTC | Jun 8, 16:10 UTC | 21h 35m |
| 2026-06-07 | FAD7095 | - | Jun 7, 17:50 UTC | Jun 8, 16:10 UTC | 22h 20m |
| 2026-06-07 | FAD7094 | MED → LBD | Jun 7, 09:15 UTC | Jun 8, 05:35 UTC | 20h 20m |
| 2026-06-07 | FAD7093 | - | Jun 7, 00:55 UTC | Jun 7, 18:35 UTC | 17h 40m |
| 2026-06-06 | FAD7093 | - | Jun 6, 14:59 UTC | Jun 7, 09:50 UTC | 18h 50m |
| 2026-06-06 | FAD7093 | - | Jun 6, 07:00 UTC | Jun 7, 01:40 UTC | 18h 40m |
| 2026-06-06 | FAD7417 | - | Jun 6, 06:20 UTC | Jun 7, 01:40 UTC | 19h 20m |
| 2026-06-05 | FAD7414 | JED → ESB | Jun 5, 12:55 UTC | Jun 6, 03:20 UTC | 14h 25m |
| 2026-06-05 | FAD7414 | JED → ESB | Jun 5, 06:35 UTC | Jun 6, 03:20 UTC | 20h 45m |
| 2026-06-05 | FAD7427 | - | Jun 5, 05:25 UTC | Jun 6, 03:20 UTC | 21h 55m |
| 2026-06-04 | FAD7420 | JED → VAS | Jun 4, 03:25 UTC | Jun 4, 20:00 UTC | 16h 35m |
| 2026-06-03 | FAD7420 | JED → VAS | Jun 3, 20:35 UTC | Jun 4, 20:00 UTC | 23h 25m |
| 2026-06-03 | FAD7409 | - | Jun 3, 19:40 UTC | Jun 4, 16:40 UTC | 21h 0m |
| 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 |
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 .