BIZTRAC BETA
Construction of residential and non-residential buildings

KVERNMO AS

Org. no. 983049052 Limited company (AS) Verdal Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 74.7m
Operating profit NOK 1.6m
Equity NOK 10.2m
Incorporated 2001
Employees 35
Share capital NOK 100,000

KVERNMO AS is registered as a limited company in Verdal, Trøndelag with organisation number 983049052. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2001 and has 35 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Entreprenørvirksomhet, handel og utleie og hva dermed står i forbindelse, herunder ved aksjeinnskudd eller på annen måte delta i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 74.7m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 74.7m
Operating profit
NOK 1.6m
Equity
NOK 10.2m
Est. value
NOK 10.3m

Financial health · 2025

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

Who owns KVERNMO AS?

RUMIN INVEST AS
KVERNMO AS
NOK 74.7m rev. · NOK 1.6m profit

KVERNMO AS has 8 registered shareholders:

All shareholders and roles →

Which companies does KVERNMO AS own?

KVERNMO AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KVERNMO AS

Who owns KVERNMO AS?

RUMIN INVEST AS is the largest registered owner, with 20.0%.

What is the revenue of KVERNMO AS?

KVERNMO AS had revenue of NOK 74.7m in 2025.

Who is the general manager of KVERNMO AS?

Inga Eline Granlund is registered as general manager of KVERNMO AS.

Where is KVERNMO AS based?

KVERNMO AS has its business address in Verdal.

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.