BIZTRAC BETA
Retail sale of books

HILLESLAND EIENDOM AS

Org. no. 887620342 Limited company (AS) Karmøy Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 492,000
Equity NOK 704,000
Incorporated 2004
Share capital NOK 250,000

HILLESLAND EIENDOM AS is registered as a limited company in Karmøy, Rogaland with organisation number 887620342. The business is classified under retail sale of books (NACE 47.610). The company was incorporated in 2004. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Investering, drift, utviklling og salg av fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 492,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 492,000
Equity
NOK 704,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns HILLESLAND EIENDOM AS?

HILLESLAND HOLDING AS
HILLESLAND EIENDOM AS
NOK 1.1m rev. · NOK 492,000 profit

HILLESLAND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HILLESLAND EIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about HILLESLAND EIENDOM AS

Who owns HILLESLAND EIENDOM AS?

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

What is the revenue of HILLESLAND EIENDOM AS?

HILLESLAND EIENDOM AS had revenue of NOK 1.1m in 2025.

Who is the general manager of HILLESLAND EIENDOM AS?

Magnus Størkersen Hillesland is registered as general manager of HILLESLAND EIENDOM AS.

Where is HILLESLAND EIENDOM AS based?

HILLESLAND EIENDOM AS has its business address in Skudeneshavn.

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.