BIZTRAC BETA
Rental and operating of own or leased real estate

HARDER EIENDOM AS

Org. no. 929199596 Limited company (AS) Harstad Incorporated 1980 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 547,000
Equity NOK 4.1m
Incorporated 1980
Employees 5
Share capital NOK 100,000

HARDER EIENDOM AS is registered as a limited company in Harstad, Troms with organisation number 929199596. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1980 and has 5 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Utleie av eiendommer samt annen virksomhet som har sammenheng med dette, eventuelt også deltakelse/samarbeid med andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 547,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 547,000
Equity
NOK 4.1m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns HARDER EIENDOM AS?

TORGEIR HARDERSEN
HARDER EIENDOM AS
NOK 1.6m rev. · NOK 547,000 profit

HARDER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HARDER EIENDOM AS own?

HARDER EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Group structure

HARDER EIENDOM AS er morselskap for 1 datterselskap:

Frequently asked questions about HARDER EIENDOM AS

Who owns HARDER EIENDOM AS?

TORGEIR HARDERSEN is the largest registered owner, with 100.0%.

What is the revenue of HARDER EIENDOM AS?

HARDER EIENDOM AS had revenue of NOK 1.6m in 2025.

Where is HARDER EIENDOM AS based?

HARDER EIENDOM AS has its business address in Harstad.

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.