BIZTRAC BETA
HAVERSTAD-EIENDOM AS is registered as “Bankrupt” with the Brønnøysund Register Centre.
Buying and selling of own real estate

HAVERSTAD-EIENDOM AS

Org. no. 919178183 Limited company (AS) Oslo Incorporated 2017 Bankrupt
Ownership graph ↗
Revenue 2024 NOK 14.9m
Operating profit NOK 2.2m
Equity NOK 100,000
Incorporated 2017
Share capital NOK 100,000

Signals

2 flags
  • Konkurs Selskapet er registrert konkurs i Enhetsregisteret.
  • Nylig endring 2026-07-18 Konkurs registrert 2026-07-18.

HAVERSTAD-EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 919178183. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er kjøp og salg av fast eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.9m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 14.9m
Operating profit
NOK 2.2m
Equity
NOK 100,000
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns HAVERSTAD-EIENDOM AS?

HAVERSTAD UTVIKLING AS
HAVERSTAD-EIENDOM AS
NOK 14.9m rev. · NOK 2.2m profit

HAVERSTAD-EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAVERSTAD-EIENDOM AS

Who owns HAVERSTAD-EIENDOM AS?

HAVERSTAD UTVIKLING AS is the largest registered owner, with 100.0%.

What is the revenue of HAVERSTAD-EIENDOM AS?

HAVERSTAD-EIENDOM AS had revenue of NOK 14.9m in 2024.

Where is HAVERSTAD-EIENDOM AS based?

HAVERSTAD-EIENDOM 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.