biztrac. BETA
COMPANY REGISTER PROFILE
996917541 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Hairdressing and barber activities

BODIL - FRISØRSALONG AS

Org. no. 996917541 Limited company (AS) Nesodden Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 816,000
Equity NOK 7.3m
Incorporated 2011
Share capital NOK 370,000

BODIL - FRISØRSALONG AS is registered as a limited company in Nesodden, Akershus with organisation number 996917541. The business is classified under hairdressing and barber activities (NACE 96.210). The company was incorporated in 2011. Registered share capital is NOK 370,000, divided into 370 shares. The company's stated purpose is: “Drive frisørvirksomhet på Nesodden.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 816,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
▲ +12 %
Operating profit
NOK 816,000
▼ −20 %
Equity
NOK 7.3m
▲ +14 %
Est. value
NOK 7.0m

Financial health · 2025

Liquidity
18.60
Very good
Current assets ÷ current liabilities
Profitability
14.6%
Good
Return on total assets
Solidity
95.5%
Very good
Equity as a share of total capital

Who owns BODIL - FRISØRSALONG AS?

BODIL - FRISØRSALONG AS
NOK 3.0m rev. · NOK 816,000 profit

BODIL - FRISØRSALONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BODIL - FRISØRSALONG AS

Who owns BODIL - FRISØRSALONG AS?

Bodil Marie Bjørnstad is the largest registered owner, with 100.0%.

What is the revenue of BODIL - FRISØRSALONG AS?

BODIL - FRISØRSALONG AS had revenue of NOK 3.0m in 2025.

Who is the general manager of BODIL - FRISØRSALONG AS?

Bodil Marie Bjørnstad is registered as general manager of BODIL - FRISØRSALONG AS.

Where is BODIL - FRISØRSALONG AS based?

BODIL - FRISØRSALONG AS has its business address in Nesoddtangen.

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

Report a problem

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