Nasdaq Sends AMASS Brands and Plum Acquisition Corp. IV Listing Compliance Notices
Nasdaq notified AMASS Brands of a bid price below $1.00 and Plum Acquisition Corp. IV of a holder-count shortfall, according to SEC filings.
- published
- in the api
- on the website
on the website stories appear 15 minutes after publication, in the api at once. connect the api →
what happened
On October 9, 2026, AMASS Brands received a notice from Nasdaq saying its common stock had traded below the $1.00 minimum bid price for 30 consecutive business days (August 26 to October 8), breaching Nasdaq Listing Rule 5450(a)(1). The notice takes no immediate effect. To regain compliance, the company has until April 7, 2027 to close at or above $1.00 for 10 consecutive trading days. If it meets applicable criteria, it may gain an additional 180 days by transferring to the Nasdaq Capital Market.
On October 7, 2026, Plum Acquisition Corp. IV received a Nasdaq notice that it is out of compliance with Listing Rule 5450(a)(2), which requires at least 400 total holders. The notice does not affect trading. The company has 45 days to submit a compliance plan. If the plan is accepted, it may receive up to 180 days. If not, the company has appeal rights.
According to Newsmetry API, which relies on documents filed with the SEC, this summary was generated with AI and may contain inaccuracies.
why it matters
For investors, such notices mainly start a formal process rather than immediately changing a security's status. They do, however, point to issues with share price or shareholder base that are worth weighing when assessing risk.
tags
instruments
sources
- AMASS Brands Disclosed Failure to Satisfy a Continued Listing Rule or Standard — Newsmetry API, 14 October 2026 at 20:33 UTC
- Plum Acquisition Corp. IV Disclosed Failure to Satisfy a Continued Listing Rule or Standard — Newsmetry API, 14 October 2026 at 21:23 UTC
prepared by the newsmetry newsroom with ai assistance from the sources listed below. not investment advice.
on the website stories appear 15 minutes after publication, in the api at once.
get stories in real time ↗