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

ØKERNLY BARNEHAGE AS

Org. no. 930678171 Limited company (AS) Sarpsborg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 20.3m
Operating profit NOK 775,000
Equity NOK 726,000
Incorporated 2022
Employees 27
Share capital NOK 30,000

ØKERNLY BARNEHAGE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 930678171. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2022 and has 27 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Barnehagedrift i avdelingen Økernly barnehage.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.3m in revenue and NOK 775,000 in operating profit.

Key figures · 2025

Revenue
NOK 20.3m
▲ +4 %
Operating profit
NOK 775,000
▲ +92 %
Equity
NOK 726,000
▲ +41 %
Est. value
NOK 3.5m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
16.5%
Very good
Return on total assets
Solidity
10.9%
Satisfactory
Equity as a share of total capital

Who owns ØKERNLY BARNEHAGE AS?

ØKERNLY BARNEHAGE AS
NOK 20.3m rev. · NOK 775,000 profit

ØKERNLY BARNEHAGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØKERNLY BARNEHAGE AS

Who owns ØKERNLY BARNEHAGE AS?

NEDRE GLOMMEN HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of ØKERNLY BARNEHAGE AS?

ØKERNLY BARNEHAGE AS had revenue of NOK 20.3m in 2025.

Who is the general manager of ØKERNLY BARNEHAGE AS?

Eirik Husby is registered as general manager of ØKERNLY BARNEHAGE AS.

Where is ØKERNLY BARNEHAGE AS based?

ØKERNLY BARNEHAGE AS has its business address in Sarpsborg.

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.