Brian Oreilly - 20 Jul 2021 Form 4 Insider Report for Spok Holdings, Inc (SPOK)

Source evidence Original filing metadata and source links for verification. 4 source fields
SEC form
4
Accepted by SEC
21 Jul 2021, 16:20:01 UTC
Prior SEC filing
02 Jul 2021
Source filing
View source filing
Reporting owner 1 detail
Reporting owner signature
/Brian O'Reilly/

Key filing fact

Brian Oreilly filed Form 4 for Spok Holdings, Inc (SPOK) on 21 Jul 2021.

Key facts

  • This page summarizes Brian Oreilly's Form 4 filing for Spok Holdings, Inc (SPOK).
  • 1 reported transaction and 0 derivative rows are listed below.
  • Accepted by SEC: 21 Jul 2021, 16:20.

Change

  • Previous filing in this sequence was filed on 02 Jul 2021.
  • Current net transaction value: +$14,997.

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

Reported non-derivative transactions

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

SPOK transaction

Common Stock

Award

Transaction value
$14,997
Shares
+1,639
Change %
+1.7%
Price
$9.15
Shares after
97,533
Date
20 Jul 2021
Ownership
Direct
* marks a reported price that did not pass the local price check.

Additional SEC filing notes

Filing notes and footnotes

Section 16 status

Brian Oreilly is no longer subject to Section 16 filing requirements. Form 4 or Form 5 obligations may still apply in specific circumstances.

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 .