BIZTRAC BETA
Development of building projects

HEIMSTAD UTVIKLING AS

Org. no. 921065949 Limited company (AS) Asker Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 35,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16k kr).

HEIMSTAD UTVIKLING AS is registered as a limited company in Asker, Akershus with organisation number 921065949. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investering og utvikling av eiendom, samt investering i annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 35,000
Est. value
NOK 143,000

Financial health · 2024

Liquidity
0.95
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HEIMSTAD UTVIKLING AS?

TERJE HEIMSTAD
HEIMSTAD UTVIKLING AS
NOK 0 rev. · NOK −16,000 profit

HEIMSTAD UTVIKLING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HEIMSTAD UTVIKLING AS own?

HEIMSTAD UTVIKLING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HEIMSTAD UTVIKLING AS

Who owns HEIMSTAD UTVIKLING AS?

TERJE HEIMSTAD is the largest registered owner, with 35.0%.

What is the revenue of HEIMSTAD UTVIKLING AS?

HEIMSTAD UTVIKLING AS had revenue of NOK 0 in 2024.

Where is HEIMSTAD UTVIKLING AS based?

HEIMSTAD UTVIKLING AS has its business address in Røyken.

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.