BIZTRAC BETA
Day spa, sauna and steam bath activities

ISAAN AS

Org. no. 923847669 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 169,000
Operating profit NOK 29,000
Equity NOK 18,000
Incorporated 2019
Share capital NOK 30,000

ISAAN AS is registered as a limited company in Drammen, Buskerud with organisation number 923847669. The business is classified under day spa, sauna and steam bath activities (NACE 96.230). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Massasje, kroppsbehandlinger, hudpleie, samt andre produkter/tjenester som naturlig hører sammen med dette. Herunder å delta i andre selskap med lignende virksomhet, samt kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 169,000 in revenue and NOK 29,000 in operating profit.

Key figures · 2025

Revenue
NOK 169,000
Operating profit
NOK 29,000
Equity
NOK 18,000
Est. value
NOK 111,000

Financial health · 2025

Liquidity
0.98
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.8%
Weak
Equity as a share of total capital

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

Who owns ISAAN AS?

ODD-ARILD JOHANSEN AS
ISAAN AS
NOK 169,000 rev. · NOK 29,000 profit

ISAAN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ISAAN AS

Who owns ISAAN AS?

ODD-ARILD JOHANSEN AS is the largest registered owner, with 66.7%.

What is the revenue of ISAAN AS?

ISAAN AS had revenue of NOK 169,000 in 2025.

Who is the general manager of ISAAN AS?

Suphak Khamsombat Johansen is registered as general manager of ISAAN AS.

Where is ISAAN AS based?

ISAAN AS has its business address in Mjøndalen.

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.