BIZTRAC BETA
Day spa, sauna and steam bath activities

LAMNAO SPA AS

Org. no. 918710868 Limited company (AS) Ringerike Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 277,000
Operating profit NOK −342,000
Equity NOK −1.1m
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−342k kr).

LAMNAO SPA AS is registered as a limited company in Ringerike, Buskerud with organisation number 918710868. The business is classified under day spa, sauna and steam bath activities (NACE 96.230). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby spabehandling og terapeutisk massasje.”. The most recent filed accounts, for the 2025 financial year, show NOK 277,000 in revenue and NOK −342,000 in operating profit.

Key figures · 2025

Revenue
NOK 277,000
Operating profit
NOK −342,000
Equity
NOK −1.1m

Financial health · 2025

Liquidity
0.23
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-913.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LAMNAO SPA AS?

LAMNAO WONGKO
LAMNAO SPA AS
NOK 277,000 rev. · NOK −342,000 profit

LAMNAO SPA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LAMNAO SPA AS

Who owns LAMNAO SPA AS?

LAMNAO WONGKO is the largest registered owner, with 100.0%.

What is the revenue of LAMNAO SPA AS?

LAMNAO SPA AS had revenue of NOK 277,000 in 2025.

Who is the general manager of LAMNAO SPA AS?

Lamnao Wongko is registered as general manager of LAMNAO SPA AS.

Where is LAMNAO SPA AS based?

LAMNAO SPA AS has its business address in Hønefoss.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.