biztrac. BETA
COMPANY REGISTER PROFILE
965247874 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

HAGABRÅTEN EIENDOM AS

Org. no. 965247874 Limited company (AS) Bærum Incorporated 1992 Active
Ownership graph ↗
Operating profit NOK −26,000
Equity NOK 7.1m
Incorporated 1992
Share capital NOK 300,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).

HAGABRÅTEN EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 965247874. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 1992. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Kjøp/salg og drift av fast eiendom, derunder utleie-, handel- og finansieringsvirksomhet samt deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −26,000
▲ +93 %
Equity
NOK 7.1m
▲ +19 %
Est. value
NOK 9.0m

Financial health · 2025

Liquidity
-3.57
Not satisfactory
Current assets ÷ current liabilities
Profitability
14.2%
Good
Return on total assets
Solidity
59.0%
Very good
Equity as a share of total capital

Who owns HAGABRÅTEN EIENDOM AS?

HAGABRÅTEN EIENDOM AS
· NOK −26,000 profit

HAGABRÅTEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HAGABRÅTEN EIENDOM AS own?

HAGABRÅTEN EIENDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HAGABRÅTEN EIENDOM AS

Who owns HAGABRÅTEN EIENDOM AS?

STIAN STRAND HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of HAGABRÅTEN EIENDOM AS?

Stian Strand is registered as general manager of HAGABRÅTEN EIENDOM AS.

Where is HAGABRÅTEN EIENDOM AS based?

HAGABRÅTEN EIENDOM AS has its business address in Skui.

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.