BIZTRAC BETA
Construction of residential and non-residential buildings

K LERVIK AS

Org. no. 970943188 Limited company (AS) Heim Incorporated 1994 Active
Ownership graph ↗
Revenue 2025 NOK 24.8m
Operating profit NOK 1.6m
Equity NOK 6.3m
Incorporated 1994
Employees 17
Share capital NOK 168,000

K LERVIK AS is registered as a limited company in Heim, Trøndelag with organisation number 970943188. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1994 and has 17 registered employees. Registered share capital is NOK 168,000, divided into 84 shares. The company's stated purpose is: “Byggevirksomhet og handel, samt hva hermed står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 24.8m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 24.8m
Operating profit
NOK 1.6m
Equity
NOK 6.3m
Est. value
NOK 8.8m

Financial health · 2025

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

Who owns K LERVIK AS?

MMTK HOLDING AS
K LERVIK AS
NOK 24.8m rev. · NOK 1.6m profit

K LERVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does K LERVIK AS own?

K LERVIK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about K LERVIK AS

Who owns K LERVIK AS?

MMTK HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of K LERVIK AS?

K LERVIK AS had revenue of NOK 24.8m in 2025.

Who is the general manager of K LERVIK AS?

Gudmund Lervik is registered as general manager of K LERVIK AS.

Where is K LERVIK AS based?

K LERVIK AS has its business address in Vågland.

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.