BIZTRAC BETA
Day spa, sauna and steam bath activities

AROMASOL LØRENSKOG AS

Org. no. 992812311 Limited company (AS) Holmestrand Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 353,000
Operating profit NOK 63,000
Equity NOK 636,000
Incorporated 2008
Share capital NOK 100,000

AROMASOL LØRENSKOG AS is registered as a limited company in Holmestrand, Vestfold with organisation number 992812311. The business is classified under day spa, sauna and steam bath activities (NACE 96.230). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drifte et solstudio beliggende i Lørenskog kommune.”. The most recent filed accounts, for the 2024 financial year, show NOK 353,000 in revenue and NOK 63,000 in operating profit.

Key figures · 2024

Revenue
NOK 353,000
Operating profit
NOK 63,000
Equity
NOK 636,000
Est. value
NOK 836,000

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
382.9%
Very good
Equity as a share of total capital

Who owns AROMASOL LØRENSKOG AS?

JAN OTTO ERIKSEN
AROMASOL LØRENSKOG AS
NOK 353,000 rev. · NOK 63,000 profit

AROMASOL LØRENSKOG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AROMASOL LØRENSKOG AS er morselskap for 1 datterselskap:

Frequently asked questions about AROMASOL LØRENSKOG AS

Who owns AROMASOL LØRENSKOG AS?

JAN OTTO ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of AROMASOL LØRENSKOG AS?

AROMASOL LØRENSKOG AS had revenue of NOK 353,000 in 2024.

Who is the general manager of AROMASOL LØRENSKOG AS?

Jan Otto Eriksen is registered as general manager of AROMASOL LØRENSKOG AS.

Where is AROMASOL LØRENSKOG AS based?

AROMASOL LØRENSKOG AS has its business address in Sande I Vestfold.

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.