SEC reporting owner

Reske James R SEC insider disclosures

Explore Reske James R's reporting-owner identity, issuer relationships, purchases, sales and SEC filing receipts.

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

Reporting owner CIK
0001435648
Issuers
2
Coverage
verified

Inspect this reporting owner's activity

Step 1 of 3

Recent SEC transactions

Reske James R: source evidence dated 2026-10-07T00:29:11.873Z.

Publicly available
2026-10-06
Trade date
2026-10-05
Issuer ticker
FCF
Code
S
Shares
200
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 0001435648-26-000033
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.

UNITED COMMUNITY FINANCIAL CORP0000707886UCFCYesNo
FIRST COMMONWEALTH FINANCIAL CORP /PA/0000712537FCFYesNo

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-10-062026-10-05FCFS200Not reported
2026-10-062026-10-05FCFS366Not reported
2026-10-062026-10-05FCFS100Not reported
2026-10-062026-10-05FCFS401Not reported
2026-10-062026-10-05FCFS699Not reported
2026-10-062026-10-05FCFS306Not reported
2026-09-052026-09-04FCFS90Not reported
2026-09-052026-09-04FCFS160Not reported
2026-09-052026-09-04FCFS160Not reported
2026-09-052026-09-04FCFS70Not reported
2026-09-052026-09-04FCFS120Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS170Not reported
2026-09-052026-09-04FCFS340Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS112Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS80Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS100Not reported
2026-09-052026-09-04FCFS70Not reported
2026-08-072026-08-05FCFS90Not reported
2026-08-072026-08-05FCFS200Not reported
2026-08-072026-08-05FCFS109Not reported
2026-08-072026-08-05FCFS69Not reported
2026-08-072026-08-05FCFS112Not reported
2026-08-072026-08-05FCFS312Not reported
2026-08-072026-08-05FCFS500Not reported
2026-08-072026-08-05FCFS200Not reported
2026-08-072026-08-05FCFS90Not reported
2026-08-072026-08-05FCFS100Not reported
2026-08-072026-08-05FCFS200Not reported
2026-08-072026-08-05FCFS90Not reported
2026-07-082026-07-06FCFS140Not reported
2026-07-082026-07-06FCFS70Not reported
2026-07-082026-07-06FCFS70Not reported
2026-07-082026-07-06FCFS100Not reported
2026-07-082026-07-06FCFS220Not reported
2026-07-082026-07-06FCFS280Not reported
2026-07-082026-07-06FCFS90Not reported
2026-07-082026-07-06FCFS90Not reported
2026-07-082026-07-06FCFS190Not reported
2026-07-082026-07-06FCFS180Not reported
2026-07-082026-07-06FCFS50Not reported
2026-07-082026-07-06FCFS32Not reported
2026-07-082026-07-06FCFS40Not reported
2026-07-082026-07-06FCFS60Not reported
2026-07-082026-07-06FCFS50Not 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.