BIZTRAC BETA
Pre-primary education

NYLAND STUDENTBARNEHAGE AS

Org. no. 930541222 Limited company (AS) Alta Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 13.0m
Operating profit NOK 41,000
Equity NOK 194,000
Incorporated 2022
Employees 33
Share capital NOK 30,000

NYLAND STUDENTBARNEHAGE AS is registered as a limited company in Alta, Finnmark with organisation number 930541222. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2022 and has 33 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive barnehage, samt det som naturlig står i forbindelse med dette. Formålet er ikke å oppnå kapitalavkastning, og det skal ikke utdeles utbytte. Eventuelt årsoverskudd skal godskrives egenkapitalen i selskapet.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.0m in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.0m
Operating profit
NOK 41,000
Equity
NOK 194,000
Est. value
NOK 340,000

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.2%
Weak
Equity as a share of total capital

Who owns NYLAND STUDENTBARNEHAGE AS?

No shareholders are registered for NYLAND STUDENTBARNEHAGE AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about NYLAND STUDENTBARNEHAGE AS

What is the revenue of NYLAND STUDENTBARNEHAGE AS?

NYLAND STUDENTBARNEHAGE AS had revenue of NOK 13.0m in 2025.

Who is the general manager of NYLAND STUDENTBARNEHAGE AS?

Marit Bakken Iversen is registered as general manager of NYLAND STUDENTBARNEHAGE AS.

Where is NYLAND STUDENTBARNEHAGE AS based?

NYLAND STUDENTBARNEHAGE AS has its business address in Alta.

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.