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

SÆVARHAGEN EIENDOM BHG AS

Org. no. 990224846 Limited company (AS) Stord Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 1.5m
Equity NOK 2.2m
Incorporated 2006
Share capital NOK 115,000

SÆVARHAGEN EIENDOM BHG AS is registered as a limited company in Stord, Vestland with organisation number 990224846. The business is classified under pre-primary education (NACE 85.100). The company was incorporated in 2006. Registered share capital is NOK 115,000, divided into 100 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 1.5m in operating profit.

Former names: NORDBYGDO BARNEHAGE AS, SÆVARHAGEN BARNEHAGE AS, SÆVARHAGEN FUS BARNEHAGE AS

Key figures · 2025

Revenue
NOK 2.1m
▲ +3 %
Operating profit
NOK 1.5m
▲ +3 %
Equity
NOK 2.2m
▲ +93 %
Est. value
NOK 5.6m

Financial health · 2025

Liquidity
3.98
Very good
Current assets ÷ current liabilities
Profitability
14.9%
Good
Return on total assets
Solidity
18.4%
Good
Equity as a share of total capital

Who owns SÆVARHAGEN EIENDOM BHG AS?

SÆVARHAGEN EIENDOM BHG AS
NOK 2.1m rev. · NOK 1.5m profit

SÆVARHAGEN EIENDOM BHG AS has 1 registered shareholder:

All shareholders and roles →

Group structure

SÆVARHAGEN EIENDOM BHG AS er morselskap for 210 datterselskaper:

Frequently asked questions about SÆVARHAGEN EIENDOM BHG AS

Who owns SÆVARHAGEN EIENDOM BHG AS?

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

What is the revenue of SÆVARHAGEN EIENDOM BHG AS?

SÆVARHAGEN EIENDOM BHG AS had revenue of NOK 2.1m in 2025.

Where is SÆVARHAGEN EIENDOM BHG AS based?

SÆVARHAGEN EIENDOM BHG AS has its business address in Stord.

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.