BIZTRAC BETA
Support activities for animal production

HARAM LANDBRUK AS

Org. no. 896575902 Limited company (AS) Haram Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 944,000
Operating profit NOK 687,000
Equity NOK 1.3m
Incorporated 2011
Share capital NOK 100,000

HARAM LANDBRUK AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 896575902. The business is classified under support activities for animal production (NACE 01.620). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Entreprenør innen landbruk, drift og anlegg, herunder dyretransport, massetransport, fôrproduksjon med meir.”. The most recent filed accounts, for the 2025 financial year, show NOK 944,000 in revenue and NOK 687,000 in operating profit.

Key figures · 2025

Revenue
NOK 944,000
Operating profit
NOK 687,000
Equity
NOK 1.3m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns HARAM LANDBRUK AS?

RUNE HARAM HOLDING AS
HARAM LANDBRUK AS
NOK 944,000 rev. · NOK 687,000 profit

HARAM LANDBRUK AS has 2 registered shareholders:

All shareholders and roles →

Group structure

HARAM LANDBRUK AS er morselskap for 3 datterselskaper:

Frequently asked questions about HARAM LANDBRUK AS

Who owns HARAM LANDBRUK AS?

RUNE HARAM HOLDING AS is the largest registered owner, with 90.1%.

What is the revenue of HARAM LANDBRUK AS?

HARAM LANDBRUK AS had revenue of NOK 944,000 in 2025.

Who is the general manager of HARAM LANDBRUK AS?

Erling Olav Longva Haram is registered as general manager of HARAM LANDBRUK AS.

Where is HARAM LANDBRUK AS based?

HARAM LANDBRUK AS has its business address in Haramsøy.

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.