Lavide Holding N.V. (LVIDE.AS)
Every figure this model derived for LVIDE.AS, 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 2025-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 | 1,003 | PurchaseOfPropertyPlantAndEquipmentClassifiedAsInvestingActivities |
2025-12-31 |
| cash | 182,389 | CashAndCashEquivalents |
2026-01-01 |
| current assets | 192,523 | CurrentAssets |
2026-01-01 |
| current liabilities | 1,178,444 | CurrentLiabilities |
2026-01-01 |
| equity | -985,068 | EquityAttributableToOwnersOfParent |
2026-01-01 |
| ocf | -1,225,822 | CashFlowsFromUsedInOperatingActivities |
2025-12-31 |
| revenue | 0 | Revenue |
2025-12-31 |
The ratios
The figures themselves rather than their scores — what somebody looking up LVIDE.AS on one particular measure came for.
| Ratio | Value |
|---|---|
| current ratio | 0.16 |
| current ratio reported | 0.16 |
| ev owner earnings | -2.48 |
What to be careful about
What this model itself distrusts about LVIDE.AS's figures. Written by the derivation as it ran, not added afterwards.
- revenue is annual, not TTM
- operating income is annual, not TTM
- no current stock compensation tagged; treated as zero, so owner earnings are overstated
- share count is from 2025-12-31 (260 days old, dei cover page); a stock split since then would make the market cap wrong. Set `market_cap` in overrides.yaml to be sure.
- 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 debt and no profit, so interest cover cannot be measured; scored on cash runway instead: 0M of net cash against a 1M annual burn is 0.1 years
- 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 0 of 5 inputs could be computed (operating margin, roic, sbc discipline, owner earnings, cash operating margin not tagged), so the score is not meaningful. Its weight is spread over the other dimensions
- valuation rests on 1 of 2 inputs; not tagged: ev sales
- 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
- 3 of 5 dimensions could not be measured (quality, durability, growth -- 60% of the model), so this row is not comparable with the others; its total rests on what was left