BIZTRAC BETA
Construction of residential and non-residential buildings

LØVHAMMER AS

Org. no. 991219722 Limited company (AS) Ålesund Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK 363,000
Equity NOK 482,000
Incorporated 2007
Employees 7
Share capital NOK 100,000

LØVHAMMER AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 991219722. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Oppføring, rehabilitering og salg av hus og fritidsboliger.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK 363,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK 363,000
Equity
NOK 482,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.2%
Satisfactory
Equity as a share of total capital

Who owns LØVHAMMER AS?

STIAN LØVIK EIDHAMMER
LØVHAMMER AS
NOK 7.6m rev. · NOK 363,000 profit

LØVHAMMER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØVHAMMER AS own?

LØVHAMMER AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LØVHAMMER AS

Who owns LØVHAMMER AS?

STIAN LØVIK EIDHAMMER is the largest registered owner, with 100.0%.

What is the revenue of LØVHAMMER AS?

LØVHAMMER AS had revenue of NOK 7.6m in 2024.

Who is the general manager of LØVHAMMER AS?

Stian Løvik Eidhammer is registered as general manager of LØVHAMMER AS.

Where is LØVHAMMER AS based?

LØVHAMMER AS has its business address in Ørskog.

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.