BIZTRAC BETA
Wholesale of perfume and cosmetics

ORGANIC LIFESTYLE AS

Org. no. 924913304 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK −6,000
Equity NOK 58,000
Incorporated 2020
Share capital NOK 45,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

ORGANIC LIFESTYLE AS is registered as a limited company in Asker, Akershus with organisation number 924913304. The business is classified under wholesale of perfume and cosmetics (NACE 46.450). The company was incorporated in 2020. Registered share capital is NOK 45,000, divided into 1500 shares. The company's stated purpose is: “Forretningsdrift og hva som derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK −6,000
Equity
NOK 58,000
Est. value
NOK 60,000

Financial health · 2024

Liquidity
54.83
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
98.2%
Weak
Equity as a share of total capital

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

Who owns ORGANIC LIFESTYLE AS?

REISO INVEST AS
ORGANIC LIFESTYLE AS
NOK 100,000 rev. · NOK −6,000 profit

ORGANIC LIFESTYLE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ORGANIC LIFESTYLE AS

Who owns ORGANIC LIFESTYLE AS?

REISO INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of ORGANIC LIFESTYLE AS?

ORGANIC LIFESTYLE AS had revenue of NOK 100,000 in 2024.

Who is the general manager of ORGANIC LIFESTYLE AS?

Atle Eikeland is registered as general manager of ORGANIC LIFESTYLE AS.

Where is ORGANIC LIFESTYLE AS based?

ORGANIC LIFESTYLE AS has its business address in Slemmestad.

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.