BIZTRAC BETA
Retail sale of hardware, building materials, paints and glass

LERVIK AS

Org. no. 842722012 Limited company (AS) Heim Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 33.0m
Operating profit NOK 4.2m
Equity NOK 13.2m
Incorporated 1987
Employees 5
Share capital NOK 66,000

LERVIK AS is registered as a limited company in Heim, Trøndelag with organisation number 842722012. The business is classified under retail sale of hardware, building materials, paints and glass (NACE 47.520). The company was incorporated in 1987 and has 5 registered employees. Registered share capital is NOK 66,000, divided into 100 shares. The company's stated purpose is: “Omsetning av trelast og byggningsartikler og alt hva dermed står i forbindelse, samt ved aksjetegning og/eller på annen måte å delta i andre foretagender. ”. The most recent filed accounts, for the 2024 financial year, show NOK 33.0m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 33.0m
Operating profit
NOK 4.2m
Equity
NOK 13.2m
Est. value
NOK 21.5m

Financial health · 2024

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

Who owns LERVIK AS?

AM LERVIK AS
LERVIK AS
NOK 33.0m rev. · NOK 4.2m profit

LERVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LERVIK AS own?

LERVIK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LERVIK AS

Who owns LERVIK AS?

AM LERVIK AS is the largest registered owner, with 50.0%.

What is the revenue of LERVIK AS?

LERVIK AS had revenue of NOK 33.0m in 2024.

Who is the general manager of LERVIK AS?

Einar Lervik is registered as general manager of LERVIK AS.

Where is LERVIK AS based?

LERVIK AS has its business address in Kyrksæterøra.

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.