BIZTRAC BETA
Hairdressing and barber activities

LØVENSTAD FRISØR AS

Org. no. 926131915 Limited company (AS) Rælingen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 381,000
Equity NOK 186,000
Incorporated 2020
Share capital NOK 30,000

LØVENSTAD FRISØR AS is registered as a limited company in Rælingen, Akershus with organisation number 926131915. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drift av frisørsalong, samt annen virksomhet som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og 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 2024 financial year, show NOK 1.8m in revenue and NOK 381,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 381,000
Equity
NOK 186,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.1%
Good
Equity as a share of total capital

Who owns LØVENSTAD FRISØR AS?

NINA KJÆR
LØVENSTAD FRISØR AS
NOK 1.8m rev. · NOK 381,000 profit

LØVENSTAD FRISØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØVENSTAD FRISØR AS

Who owns LØVENSTAD FRISØR AS?

NINA KJÆR is the largest registered owner, with 100.0%.

What is the revenue of LØVENSTAD FRISØR AS?

LØVENSTAD FRISØR AS had revenue of NOK 1.8m in 2024.

Who is the general manager of LØVENSTAD FRISØR AS?

Nina Kjær is registered as general manager of LØVENSTAD FRISØR AS.

Where is LØVENSTAD FRISØR AS based?

LØVENSTAD FRISØR AS has its business address in Løvenstad.

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.