BIZTRAC BETA
Rental and operating of own or leased real estate

HAFSLUND EIENDOM AS

Org. no. 929283422 Limited company (AS) Sarpsborg Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 192,000
Operating profit NOK 111,000
Equity NOK −59,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−59k kr).

HAFSLUND EIENDOM AS is registered as a limited company in Sarpsborg, Østfold with organisation number 929283422. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utleie og forvaltning av fast eiendom, investering i aksjer og andre selskaper, samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 192,000 in revenue and NOK 111,000 in operating profit.

Key figures · 2024

Revenue
NOK 192,000
Operating profit
NOK 111,000
Equity
NOK −59,000
Est. value
NOK 762,000

Financial health · 2024

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

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

Who owns HAFSLUND EIENDOM AS?

ZABIEULLAH AZIZI
HAFSLUND EIENDOM AS
NOK 192,000 rev. · NOK 111,000 profit

HAFSLUND EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAFSLUND EIENDOM AS

Who owns HAFSLUND EIENDOM AS?

ZABIEULLAH AZIZI is the largest registered owner, with 50.0%.

What is the revenue of HAFSLUND EIENDOM AS?

HAFSLUND EIENDOM AS had revenue of NOK 192,000 in 2024.

Where is HAFSLUND EIENDOM AS based?

HAFSLUND EIENDOM AS has its business address in Sarpsborg.

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.