ATERIAN PLC (ATN.L)
Every figure this model derived for ATN.L, the value it took, and the element in the company's own XBRL it was read from — so any of it can be checked against the filing rather than taken on trust. As at 2023-12-31.
The figures, and where each came from
This is the part no other screener shows. Each figure below names the XBRL element it was read from, so it can be checked against the filing itself.
| Figure | Value | XBRL tag | As at |
|---|---|---|---|
| capex | 5,000 | PurchaseOfPropertyPlantAndEquipmentClassifiedAsInvestingActivities |
2023-12-31 |
| cash | 73,000 | CashAndCashEquivalents |
2024-01-01 |
| current assets | 630,000 | CurrentAssets |
2024-01-01 |
| current liabilities | 793,000 | CurrentLiabilities |
2024-01-01 |
| equity | 3,418,000 | Equity |
2024-01-01 |
| interest expense | 54,000 | FinanceCosts |
2023-12-31 |
| ocf | -1,158,000 | CashFlowsFromUsedInOperatingActivities |
2023-12-31 |
| revenue | 0 | Revenue |
2023-12-31 |
| sbc | 1,000 | AdjustmentsForSharebasedPayments |
2023-12-31 |
The ratios
The figures themselves rather than their scores — what somebody looking up ATN.L on one particular measure came for.
| Ratio | Value |
|---|---|
| current ratio | 0.79 |
| current ratio reported | 0.79 |
| interest cover | -18.67 |
| roic | -23.81 |
What to be careful about
What this model itself distrusts about ATN.L's figures. Written by the derivation as it ran, not added afterwards.
- newest fact in the filing is 2024-01-01 (2y old); this company's data is not usable and the scores below should be ignored
- revenue is annual, not TTM
- operating income is annual, not TTM
- revenue period ends 2023-12-31 (992 days ago) - the tag chain found nothing recent, so treat this row as unscored
- no market cap; set `market_cap` in overrides.yaml
- no usable diluted share count, so growth is measured on total revenue rather than per share; a company issuing shares to fund that growth reads better than it is
- no forward EPS estimate; growth rests on filings only. Analyst consensus is not published in XBRL, so it has to be fetched from a data provider or set by hand in overrides.yaml as `eps_growth_2y`
- quality DROPPED from the total: only 1 of 5 inputs could be computed (operating margin, sbc discipline, owner earnings, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- valuation DROPPED from the total: only 0 of 2 inputs could be computed (ev sales, ev owner earnings not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- durability DROPPED from the total: only 0 of 4 inputs could be computed (worst year, contracted coverage, gross margin stability, cash flow stability not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- growth DROPPED from the total: only 0 of 4 inputs could be computed (revenue growth, sustained growth, margin trend, margin recent not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- 4 of 5 dimensions could not be measured (quality, valuation, durability, growth -- 85% of the model), so this row is not comparable with the others; its total rests on what was left