Michael Snavely - 20 May 2024 Form 4 Insider Report for Phunware, Inc. (PHUN)

Source evidence Original filing metadata and source links for verification. 5 source fields
SEC form
4
Accepted by SEC
24 May 2024, 12:54:28 UTC
Prior SEC filing
15 Mar 2024
Next SEC filing
12 Jun 2024
Source filing
View source filing
Reporting owner 1 detail
Reporting owner signature
/s/ J. Brendhan Botkin, Attorney-in-Fact

Key filing fact

Michael Snavely filed Form 4 for Phunware, Inc. (PHUN) on 24 May 2024.

Key facts

  • This page summarizes Michael Snavely's Form 4 filing for Phunware, Inc. (PHUN).
  • 1 reported transaction and 0 derivative rows are listed below.
  • Accepted by SEC: 24 May 2024, 12:54.

Change

  • Previous filing in this sequence was filed on 15 Mar 2024.
  • Current net transaction value: +$19,500.

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.

PHUN transaction

Common Stock

Purchase

Transaction value
$19,500
Shares
+3,000
Change %
+13%
Price
$6.50
Shares after
26,143
Date
20 May 2024
Ownership
Direct
Footnotes
F1
* marks a reported price that did not pass the local price check.

Additional SEC filing notes

Filing notes and footnotes

Explanation of responses 1 footnote

Footnote F1

The price reported in Table I, box 4 above reflects the actual per share sales price of the shares purchased.

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 .