David M. Shane - 19 May 2026 Form 4 Insider Report for Binah Capital Group, Inc. (BCG)

Source evidence Original filing metadata and source links for verification. 4 source fields
SEC form
4
Accepted by SEC
20 May 2026, 17:01:29 UTC
Prior SEC filing
01 Jul 2025
Source filing
View source filing
Reporting owner 1 detail
Reporting owner signature
/s/ David M. Shane

Key filing fact

David M. Shane filed Form 4 for Binah Capital Group, Inc. (BCG) on 20 May 2026.

Key facts

  • This page summarizes David M. Shane's Form 4 filing for Binah Capital Group, Inc. (BCG).
  • 1 reported transaction and 0 derivative rows are listed below.
  • Accepted by SEC: 20 May 2026, 17:01.

Change

  • Previous filing in this sequence was filed on 01 Jul 2025.
  • Current net transaction value: +$4,980.

Research use

  • This tells you what this filing adds before you inspect full transaction and derivative tables.
  • You can trace every row back to the original SEC filing document.

Evidence

Filed on Form 4

Ownership activity is grounded in SEC Form 4 disclosures.

View source filing

Reporting Owners (1)

CIK 0002016391 Primary reporting owner

Shane David M.

Relationship
Chief Financial Officer, Director
Address
80 STATE STREET, ALBANY
Signature
/s/ David M. Shane
Signature date
20 May 2026

Reported non-derivative transactions

Shares, units, or other non-derivative securities reported in this filing.

BCG transaction

Common Stock

Purchase

Transaction value
$4,980
Shares
+3,000
Change %
Price
$1.66
Shares after
3,000
Date
19 May 2026
Ownership
Direct
* marks a reported price that did not pass the local price check.
We use cookies and similar technologies to provide certain features, enhance the user experience and, if you allow them, measure engagement and deliver advertising. Analytics and marketing storage stay off until you grant consent. By clicking on "Agree and continue", you declare your consent to the use of the selected optional cookies. Manage preferences to update or revoke optional consent for future visits. For more information, see our Privacy Policy .