biztrac. BETA
COMPANY REGISTER PROFILE
898679772 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Pre-primary education

SPANGEREID NATURBARNEHAGE AS

Org. no. 898679772 Limited company (AS) Lindesnes Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 305,000
Equity NOK 1.7m
Incorporated 2012
Employees 14
Share capital NOK 30,000

SPANGEREID NATURBARNEHAGE AS is registered as a limited company in Lindesnes, Agder with organisation number 898679772. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2012 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Barnehagedrift og derved alt som står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 305,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
▲ +9 %
Operating profit
NOK 305,000
▲ +94 %
Equity
NOK 1.7m
▲ +11 %
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
1.96
Good
Current assets ÷ current liabilities
Profitability
8.4%
Satisfactory
Return on total assets
Solidity
43.3%
Very good
Equity as a share of total capital

Who owns SPANGEREID NATURBARNEHAGE AS?

SPANGEREID NATURBARNEHAGE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SPANGEREID NATURBARNEHAGE AS

Who owns SPANGEREID NATURBARNEHAGE AS?

Sissel Hadland is the largest registered owner, with 32.5%.

What is the revenue of SPANGEREID NATURBARNEHAGE AS?

SPANGEREID NATURBARNEHAGE AS had revenue of NOK 6.7m in 2025.

Who is the general manager of SPANGEREID NATURBARNEHAGE AS?

Sissel Hadland is registered as general manager of SPANGEREID NATURBARNEHAGE AS.

Where is SPANGEREID NATURBARNEHAGE AS based?

SPANGEREID NATURBARNEHAGE AS has its business address in Lindesnes.

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.