BIZTRAC BETA
Construction of residential and non-residential buildings

LERVIKE AS

Org. no. 994259369 Limited company (AS) Sunndal Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 27.1m
Operating profit NOK 2.2m
Equity NOK 6.8m
Incorporated 2009
Employees 10
Share capital NOK 266,000

LERVIKE AS is registered as a limited company in Sunndal, Møre og Romsdal with organisation number 994259369. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2009 and has 10 registered employees. Registered share capital is NOK 266,000, divided into 266 shares. The company's stated purpose is: “Nybygg og restaurering av eldre bygninger basert på tradisjonelt håndverk, produksjon og foredling av trevirke for samme, og tilgrensende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.1m in revenue and NOK 2.2m in operating profit.

Key figures · 2024

Revenue
NOK 27.1m
Operating profit
NOK 2.2m
Equity
NOK 6.8m
Est. value
NOK 10.2m

Financial health · 2024

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

Who owns LERVIKE AS?

ERLING VIKE
LERVIKE AS
NOK 27.1m rev. · NOK 2.2m profit

LERVIKE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LERVIKE AS own?

LERVIKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LERVIKE AS

Who owns LERVIKE AS?

ERLING VIKE is the largest registered owner, with 37.6%.

What is the revenue of LERVIKE AS?

LERVIKE AS had revenue of NOK 27.1m in 2024.

Who is the general manager of LERVIKE AS?

Rolf Trygve Lervik is registered as general manager of LERVIKE AS.

Where is LERVIKE AS based?

LERVIKE AS has its business address in Øksendal.

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.