BIZTRAC BETA
Development of building projects

AASE GAARD AS

Org. no. 989347292 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK −14.1m
Equity NOK 45.5m
Incorporated 2006
Share capital NOK 2.1m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14,1 mill kr).

AASE GAARD AS is registered as a limited company in Oslo, Oslo with organisation number 989347292. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2006. Registered share capital is NOK 2.1m, divided into 200 shares. The company's stated purpose is: “Eie, leie, utleie, utvikle, forvalte, drifte og investere i fast eiendom eller selskaper som eier fast eiendom, samt andre aktiviteter forbundet med dette, herunder oppta lån fra selskaper i samme konsern for å finansiere virksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK −14.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK −14.1m
Equity
NOK 45.5m
Est. value
NOK 34.4m

Financial health · 2024

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

Who owns AASE GAARD AS?

SELVAAG BOLIG ROGALAND AS
AASE GAARD AS
NOK 4.2m rev. · NOK −14.1m profit

AASE GAARD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AASE GAARD AS er morselskap for 2 datterselskaper:

Frequently asked questions about AASE GAARD AS

Who owns AASE GAARD AS?

SELVAAG BOLIG ROGALAND AS is the largest registered owner, with 100.0%.

What is the revenue of AASE GAARD AS?

AASE GAARD AS had revenue of NOK 4.2m in 2024.

Where is AASE GAARD AS based?

AASE GAARD AS has its business address in Oslo.

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.