BIZTRAC BETA
Buying and selling of own real estate

SAKKESTAD EIENDOM AS

Org. no. 813009072 Limited company (AS) Haugesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −539,000
Equity NOK 375,000
Incorporated 2013
Share capital NOK 30,000

Signals

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

SAKKESTAD EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 813009072. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og forvaltning av eiendom samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −539,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −539,000
Equity
NOK 375,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns SAKKESTAD EIENDOM AS?

SAKKESTAD HOLDING AS
SAKKESTAD EIENDOM AS
NOK 2.0m rev. · NOK −539,000 profit

SAKKESTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAKKESTAD EIENDOM AS

Who owns SAKKESTAD EIENDOM AS?

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

What is the revenue of SAKKESTAD EIENDOM AS?

SAKKESTAD EIENDOM AS had revenue of NOK 2.0m in 2024.

Who is the general manager of SAKKESTAD EIENDOM AS?

Rune Sakkestad is registered as general manager of SAKKESTAD EIENDOM AS.

Where is SAKKESTAD EIENDOM AS based?

SAKKESTAD EIENDOM AS has its business address in Haugesund.

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.