BIZTRAC BETA
Rental and operating of own or leased real estate

LØVSØY INDUSTRIHUS AS

Org. no. 986215298 Limited company (AS) Haram Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 206,000
Operating profit NOK 58,000
Equity NOK −311,000
Incorporated 2003
Share capital NOK 1.3m

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−311k kr).

LØVSØY INDUSTRIHUS AS is registered as a limited company in Haram, Møre og Romsdal with organisation number 986215298. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 1.3m, divided into 665 shares. The company's stated purpose is: “Eie, drive og tilrettelegge for aktivitet i Løvsøy Industrihus AS.”. The most recent filed accounts, for the 2024 financial year, show NOK 206,000 in revenue and NOK 58,000 in operating profit.

Key figures · 2024

Revenue
NOK 206,000
Operating profit
NOK 58,000
Equity
NOK −311,000
Est. value
NOK 448,000

Financial health · 2025

Liquidity
19.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-218.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LØVSØY INDUSTRIHUS AS?

ÅLESUND KOMMUNE UNDER SLETTING FRA 01.01.2024
LØVSØY INDUSTRIHUS AS
NOK 206,000 rev. · NOK 58,000 profit

LØVSØY INDUSTRIHUS AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about LØVSØY INDUSTRIHUS AS

Who owns LØVSØY INDUSTRIHUS AS?

ÅLESUND KOMMUNE UNDER SLETTING FRA 01.01.2024 is the largest registered owner, with 37.6%.

What is the revenue of LØVSØY INDUSTRIHUS AS?

LØVSØY INDUSTRIHUS AS had revenue of NOK 206,000 in 2024.

Where is LØVSØY INDUSTRIHUS AS based?

LØVSØY INDUSTRIHUS AS has its business address in Kjerstad.

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.