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

FØRLAND BARNEHAGE EIENDOM AS

Org. no. 991127224 Limited company (AS) Haugesund Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 1.0m
Equity NOK 1.2m
Incorporated 2007
Share capital NOK 100,000

FØRLAND BARNEHAGE EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 991127224. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bygge, eie og drive barnehage av god kvalitet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 1.0m in operating profit.

Former names: FØRLAND BARNEHAGE AS

Key figures · 2025

Revenue
NOK 1.7m
▼ −4 %
Operating profit
NOK 1.0m
▼ −7 %
Equity
NOK 1.2m
▲ +79 %
Est. value
NOK 3.6m

Financial health · 2025

Liquidity
4.45
Very good
Current assets ÷ current liabilities
Profitability
8.9%
Satisfactory
Return on total assets
Solidity
9.0%
Weak
Equity as a share of total capital

Who owns FØRLAND BARNEHAGE EIENDOM AS?

FØRLAND BARNEHAGE EIENDOM AS
NOK 1.7m rev. · NOK 1.0m profit

FØRLAND BARNEHAGE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

FØRLAND BARNEHAGE EIENDOM AS er morselskap for 210 datterselskaper:

Frequently asked questions about FØRLAND BARNEHAGE EIENDOM AS

Who owns FØRLAND BARNEHAGE EIENDOM AS?

SFR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FØRLAND BARNEHAGE EIENDOM AS?

FØRLAND BARNEHAGE EIENDOM AS had revenue of NOK 1.7m in 2025.

Where is FØRLAND BARNEHAGE EIENDOM AS based?

FØRLAND BARNEHAGE EIENDOM AS has its business address in Haugesund.

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.