BGM Group Ltd: diluted weighted-average shares
Diluted weighted-average shares for BGM Group Ltd. Inspect selected reporting periods, original units and SEC filing links; download the financial history.
All BGM Group Ltd financial histories
What this measure means
Weighted-average shares used for diluted earnings per share. Potential shares are included under the applicable dilution rules, not simply added to outstanding shares.
Exact concept: us-gaap:WeightedAverageNumberOfDilutedSharesOutstanding. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.
Coverage of this history
Selected reporting periods run from 2018-10-01 to 2025-09-30. The SEC response was captured on 2026-09-19.
Reading these values
This selected numerical history matches Basic weighted-average shares for the same reporting intervals and original units. The accounting definitions remain distinct. Equal values do not establish that the concepts are interchangeable or explain why they match; filing dates and accessions may differ. Compare the definitions and source filings before combining them.
Context from the filing
For BGM’s years ended September 30, 2023, 2024 and 2025, EPS uses net loss attributable to ordinary shareholders after noncontrolling interests, rather than consolidated or comprehensive loss. The filing excludes anti-dilutive potential shares and states there were no other diluted shares for these years. Its June 2024 five-for-one consolidation is already reflected. The prior auditor explicitly says it did not audit the subsequent adjustment to the 2023 share and EPS figures; this review preserves that limitation and does not certify those adjustments. Full share counts, USD EPS and September fiscal dates remain as reported. Read the source filing.
Selected filing history
| Period start | Period end | Value | Unit | Filed | Source filing |
|---|---|---|---|---|---|
| 2024-10-01 | 2025-09-30 | 113,261,317 | shares | 2026-07-21 | 20-F · 0001104659-26-085247 |
| 2023-10-01 | 2024-09-30 | 7,226,480 | shares | 2026-07-21 | 20-F · 0001104659-26-085247 |
| 2022-10-01 | 2023-09-30 | 7,226,480 | shares | 2026-07-21 | 20-F · 0001104659-26-085247 |
| 2021-10-01 | 2022-09-30 | 7,226,480 | shares | 2025-04-03 | 20-F/A · 0001410578-25-000636 |
| 2020-10-01 | 2021-09-30 | 34,089,286 | shares | 2024-02-15 | 20-F · 0001410578-24-000053 |
| 2019-10-01 | 2020-09-30 | 30,000,000 | shares | 2023-04-19 | 20-F · 0001410578-23-000745 |
| 2018-10-01 | 2019-09-30 | 30,000,000 | shares | 2022-10-13 | 20-F/A · 0001410578-22-002876 |
Related financial histories
- BGM Group Ltd: total assets
- BGM Group Ltd: total liabilities
- BGM Group Ltd: stockholders equity
- BGM Group Ltd: cash and cash equivalents
- BGM Group Ltd: net income or loss
- BGM Group Ltd: operating cash flow
- BGM Group Ltd: capital expenditure payments
- BGM Group Ltd: contract revenue excluding tax
- BGM Group Ltd: financing cash flow
- BGM Group Ltd: investing cash flow
- BGM Group Ltd: retained earnings or deficit
- BGM Group Ltd: basic weighted-average shares
- BGM Group Ltd: basic earnings per share
- BGM Group Ltd: diluted earnings per share
- BGM Group Ltd: income tax expense or benefit
- BGM Group Ltd: net property, plant and equipment
- BGM Group Ltd: operating income or loss
- BGM Group Ltd: current assets
- BGM Group Ltd: interest expense
- BGM Group Ltd: current liabilities
- BGM Group Ltd: current accounts payable
- BGM Group Ltd: net finite-lived intangible assets
- BGM Group Ltd: net current accounts receivable
- BGM Group Ltd: net inventory
- BGM Group Ltd: gross profit
- BGM Group Ltd: cost of revenue
- BGM Group Ltd: selling, general and administrative expense
- BGM Group Ltd: research and development expense
Inspect the source
- Entity
- BGM Group Ltd / CIK 0001779578
- Captured
- 2026-09-19T11:21:13.455Z
- SEC response SHA-256
33210dced8349befe86035f27f40b7d791195a7c7d46a49edee117719fcc79c3
Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON
Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.
Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.
Use this in research
A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.
These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.
Research methodology · Execution and cost assumptions · Check backtest overfitting
Build with the open-source tools
Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.
- Get an API key and run your first validation
- Connect the MCP server to your coding assistant
- Inspect the ALPHAC engine on GitHub
- Read the MCP server source and integration examples
Read the published dataset with Python
import json
from urllib.request import urlopen
with urlopen("https://canlicapital.com/company-data/0001779578.json") as response:
record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
print(concept["tag"], next(iter(concept["observations"])))