SEC reporting owner

Voskanian Shaunt SEC insider disclosures

Explore Voskanian Shaunt's reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

As of 2026-10-07T00:29:11.873Z

Reporting owner CIK
0002073591
Issuers
1
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Voskanian Shaunt: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-08-07
Trade date
2026-08-05
Issuer ticker
FIG
Code
S
Shares
30,000
Reported value
Not reported
What you should see

The displayed owner or issuer and source fields identify the receipt to verify; keep reporting and availability dates separate.

Step 2 of 3

Which issuer and transaction does this person appear in?

Match the reviewed owner identity, issuer and transaction code. Directory eligibility does not turn every filing into a strategy signal.

SEC accession 0002073591-26-000032
What you should see

Use the linked SEC receipts and company profiles to verify what became public and when.

Step 3 of 3

Browse insider directory

Use the linked SEC receipts and company profiles to verify what became public and when.

Browse insider directory
What you should see

Keep reporting dates and units beside the answer, and inspect its original citations.

Issuer relationships

A reporting-owner CIK identifies the filer across issuer relationships and name aliases. A filer may be an individual or an organization; the filing role is the relevant evidence.

Scroll sideways to compare all columns. Select a heading to sort.

Figma, Inc.0001579878FIGYesNo

Recent SEC transactions

See the complete recent sec transactions

Code P identifies a purchase, S a sale and A an award. Awards and open-market purchases describe different events. Use the public availability date when deciding when a researcher could have known about the transaction.

Scroll sideways to compare all columns. Select a heading to sort.

2026-08-072026-08-05FIGS30,000Not reported
2026-08-072026-08-04FIGS7,726Not reported
2026-08-072026-08-04FIGS4,099Not reported
2026-08-072026-08-04FIGS1,000Not reported
2026-07-172026-07-14FIGS11,219Not reported
2026-07-092026-07-06FIGS8,629Not reported
2026-06-062026-06-03FIGS20,281Not reported
2026-06-062026-06-03FIGS67,229Not reported
2026-03-252026-03-20FIGA324,939Not reported
2026-02-282026-02-25FIGS8,554Not reported
2026-02-052026-02-02FIGS2,188Not reported
2026-02-052026-02-02FIGS1,640Not reported
2026-01-072026-01-05FIGS2,200Not reported
2026-01-072026-01-05FIGS6,249Not reported
2026-01-072026-01-02FIGS1,936Not reported
2026-01-072026-01-02FIGS1,997Not reported
2025-12-062025-12-03FIGS3,745Not reported
2025-12-062025-12-03FIGS2,560Not reported
2025-12-042025-12-01FIGS6,076Not reported
2025-11-142025-11-10FIGS18,768Not reported
2025-11-142025-11-10FIGS37,678Not reported
2025-11-142025-11-10FIGS30,265Not reported
2025-11-142025-11-10FIGS8,800Not reported
2025-11-142025-11-10FIGS145,641Not reported
2025-11-142025-11-10FIGS162,183Not reported
2025-11-062025-11-03FIGS26,741Not reported
2025-08-062025-08-01FIGS90,000Not reported

Up to 50 transactions from the recent two-year owner window.

Source evidence and strategy eligibility

The transactions below come from filings; a historical tracker separately simulates following eligible events. Joint filers can report the same transaction, and an owner can have filings at multiple companies. Public availability, amendment lineage and verified coverage determine which events a historical tracker may use.

The current directory marks this owner's filing coverage verified.

Aurora · AI research assistant

Try this in Aurora

Edit the request, then open it in Aurora. You choose when to send it.