Not currently tracked · last seen 5d ago
- Flights observed
- 32
- Avg flight time
- 58m
- Typical route
- -
- Last seen
- 5d ago
Last known area
Recent flights last 32
| Date | Route | Takeoff | Landing | Duration |
|---|---|---|---|---|
| 2026-07-08 | - | Jul 8, 16:35 UTC | Jul 8, 16:55 UTC | 20m |
| 2026-07-05 | - | Jul 5, 18:45 UTC | Jul 5, 20:05 UTC | 1h 20m |
| 2026-07-02 | - | Jul 2, 20:55 UTC | Jul 2, 21:00 UTC | 5m |
| 2026-06-30 | - | Jun 30, 18:10 UTC | Jun 30, 18:35 UTC | 25m |
| 2026-06-28 | - | Jun 28, 18:34 UTC | Jun 28, 19:55 UTC | 1h 20m |
| 2026-06-24 | - | Jun 24, 20:44 UTC | Jun 24, 21:09 UTC | 25m |
| 2026-06-24 | - | Jun 24, 16:19 UTC | Jun 24, 16:40 UTC | 20m |
| 2026-06-23 | - | Jun 23, 19:10 UTC | Jun 23, 19:44 UTC | 35m |
| 2026-06-23 | - | Jun 23, 15:50 UTC | Jun 23, 16:29 UTC | 40m |
| 2026-06-22 | - | Jun 22, 19:54 UTC | Jun 22, 20:34 UTC | 40m |
| 2026-06-19 | - | Jun 19, 19:25 UTC | Jun 19, 19:49 UTC | 25m |
| 2026-06-19 | YYJ → BFI | Jun 19, 18:05 UTC | Jun 19, 18:59 UTC | 55m |
| 2026-06-18 | - | Jun 18, 16:50 UTC | Jun 18, 17:55 UTC | 1h 5m |
| 2026-06-14 | - | Jun 14, 15:15 UTC | Jun 14, 16:40 UTC | 1h 25m |
| 2026-06-11 | - | Jun 11, 16:30 UTC | Jun 11, 18:00 UTC | 1h 30m |
| 2026-06-04 | - | Jun 4, 16:05 UTC | Jun 4, 17:10 UTC | 1h 5m |
| 2026-06-02 | - | Jun 2, 21:40 UTC | Jun 2, 22:55 UTC | 1h 15m |
| 2026-06-01 | - | Jun 1, 22:20 UTC | Jun 1, 22:30 UTC | 10m |
| 2026-06-01 | - | Jun 1, 18:30 UTC | Jun 1, 19:00 UTC | 30m |
| 2026-05-30 | - | May 30, 16:40 UTC | May 30, 17:30 UTC | 50m |
| 2026-05-27 | - | May 27, 20:10 UTC | May 27, 21:00 UTC | 50m |
| 2026-05-24 | - | May 24, 19:45 UTC | May 24, 21:15 UTC | 1h 30m |
| 2026-05-22 | - | May 22, 21:00 UTC | May 23, 01:25 UTC | 4h 25m |
| 2026-05-22 | - | May 22, 16:55 UTC | May 22, 19:10 UTC | 2h 15m |
| 2026-05-21 | - | May 21, 22:50 UTC | May 21, 23:00 UTC | 10m |
| 2026-04-17 | - | Apr 17, 23:25 UTC | Apr 18, 00:25 UTC | 1h 0m |
| 2026-04-17 | - | Apr 17, 21:25 UTC | Apr 17, 23:20 UTC | 1h 55m |
| 2026-04-17 | - | Apr 17, 20:35 UTC | Apr 17, 21:20 UTC | 45m |
| 2026-04-17 | - | Apr 17, 19:25 UTC | Apr 17, 19:50 UTC | 25m |
| 2026-04-17 | - | Apr 17, 17:30 UTC | Apr 17, 19:20 UTC | 1h 50m |
| 2026-04-16 | - | Apr 16, 21:45 UTC | Apr 16, 22:05 UTC | 20m |
| 2026-04-15 | - | Apr 15, 17:05 UTC | Apr 15, 17:15 UTC | 10m |
Specifications
| Registration | N935WS |
| Operator | RIVETING DRAMA LLC |
| Mode-S code | ACFA41 · 53175101 (octal) |
Looking for transponder-level data? View the Mode-S ACFA41 page for country allocation, callsign history, and ADS-B signal details.
N935WS frequently asked
Who operates N935WS?
N935WS is operated by RIVETING DRAMA LLC.
What is the Mode-S transponder code for N935WS?
N935WS broadcasts on Mode-S (ICAO 24-bit) address ACFA41 (octal 53175101). View the transponder page.
Where is N935WS right now?
N935WS is not currently being tracked; last seen 5d ago.