BIZTRAC BETA
Pre-primary education

LANGØY FRILUFTSBARNEHAGE AS

Org. no. 995663953 Limited company (AS) Øygarden Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK −91,000
Equity NOK 377,000
Incorporated 2010
Employees 22
Share capital NOK 100,000

Signals

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

LANGØY FRILUFTSBARNEHAGE AS is registered as a limited company in Øygarden, Vestland with organisation number 995663953. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2010 and has 22 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av barnehage.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK −91,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK −91,000
Equity
NOK 377,000
Est. value
NOK 6.2m

Financial health · 2024

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

Who owns LANGØY FRILUFTSBARNEHAGE AS?

LISE LAUVIK
LANGØY FRILUFTSBARNEHAGE AS
NOK 6.8m rev. · NOK −91,000 profit

LANGØY FRILUFTSBARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGØY FRILUFTSBARNEHAGE AS

Who owns LANGØY FRILUFTSBARNEHAGE AS?

LISE LAUVIK is the largest registered owner, with 100.0%.

What is the revenue of LANGØY FRILUFTSBARNEHAGE AS?

LANGØY FRILUFTSBARNEHAGE AS had revenue of NOK 6.8m in 2024.

Who is the general manager of LANGØY FRILUFTSBARNEHAGE AS?

Lise Lauvik is registered as general manager of LANGØY FRILUFTSBARNEHAGE AS.

Where is LANGØY FRILUFTSBARNEHAGE AS based?

LANGØY FRILUFTSBARNEHAGE AS has its business address in Fjell.

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.