BIZTRAC BETA
Pre-primary education

FJELLDAL BARNEHAGE AS

Org. no. 991530894 Limited company (AS) Sarpsborg Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 11.9m
Operating profit NOK 222,000
Equity NOK 2.9m
Incorporated 2007
Employees 16
Share capital NOK 400,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FJELLDAL BARNEHAGE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 991530894. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2007 and has 16 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Barnehagedrift med dertil tilhørende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.9m in revenue and NOK 222,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.9m
Operating profit
NOK 222,000
Equity
NOK 2.9m
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns FJELLDAL BARNEHAGE AS?

NEDRE GLOMMEN HOLDING AS
FJELLDAL BARNEHAGE AS
NOK 11.9m rev. · NOK 222,000 profit

FJELLDAL BARNEHAGE AS has 2 registered shareholders:

All shareholders and roles →

Group structure

FJELLDAL BARNEHAGE AS er morselskap for 4 datterselskaper:

Frequently asked questions about FJELLDAL BARNEHAGE AS

Who owns FJELLDAL BARNEHAGE AS?

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

What is the revenue of FJELLDAL BARNEHAGE AS?

FJELLDAL BARNEHAGE AS had revenue of NOK 11.9m in 2024.

Where is FJELLDAL BARNEHAGE AS based?

FJELLDAL BARNEHAGE AS has its business address in Borgenhaugen.

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.