BIZTRAC BETA
Rental and operating of own or leased real estate

HODEVERKET EIENDOM AS

Org. no. 921878559 Limited company (AS) Sandnes Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 698,000
Operating profit NOK 340,000
Equity NOK 1.6m
Incorporated 2018
Share capital NOK 765,000

HODEVERKET EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 921878559. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 765,000, divided into 25500 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse, og å drive utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 698,000 in revenue and NOK 340,000 in operating profit.

Key figures · 2025

Revenue
NOK 698,000
Operating profit
NOK 340,000
Equity
NOK 1.6m
Est. value
NOK 1.6m

Financial health · 2025

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

Who owns HODEVERKET EIENDOM AS?

HODEVERKET HOLDING AS
HODEVERKET EIENDOM AS
NOK 698,000 rev. · NOK 340,000 profit

HODEVERKET EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HODEVERKET EIENDOM AS

Who owns HODEVERKET EIENDOM AS?

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

What is the revenue of HODEVERKET EIENDOM AS?

HODEVERKET EIENDOM AS had revenue of NOK 698,000 in 2025.

Who is the general manager of HODEVERKET EIENDOM AS?

Julie Sønnervik is registered as general manager of HODEVERKET EIENDOM AS.

Where is HODEVERKET EIENDOM AS based?

HODEVERKET EIENDOM AS has its business address in Sandnes.

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.