BIZTRAC BETA
Pre-primary education

SOLREGN FAMILIEBARNEHAGE AS

Org. no. 999522254 Limited company (AS) Malvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 28,000
Equity NOK 450,000
Incorporated 2012
Employees 8
Share capital NOK 30,000

SOLREGN FAMILIEBARNEHAGE AS is registered as a limited company in Malvik, Trøndelag with organisation number 999522254. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Familiebarnehage med pass og stell av barn. Og annet som naturlig er forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 28,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 28,000
Equity
NOK 450,000
Est. value
NOK 416,000

Financial health · 2024

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

Who owns SOLREGN FAMILIEBARNEHAGE AS?

HEIDI ALEKSANDERSEN
SOLREGN FAMILIEBARNEHAGE AS
NOK 2.2m rev. · NOK 28,000 profit

SOLREGN FAMILIEBARNEHAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLREGN FAMILIEBARNEHAGE AS

Who owns SOLREGN FAMILIEBARNEHAGE AS?

HEIDI ALEKSANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of SOLREGN FAMILIEBARNEHAGE AS?

SOLREGN FAMILIEBARNEHAGE AS had revenue of NOK 2.2m in 2024.

Who is the general manager of SOLREGN FAMILIEBARNEHAGE AS?

Heidi Aleksandersen is registered as general manager of SOLREGN FAMILIEBARNEHAGE AS.

Where is SOLREGN FAMILIEBARNEHAGE AS based?

SOLREGN FAMILIEBARNEHAGE AS has its business address in Saksvik.

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.