BIZTRAC BETA
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

VISNES KALK AS

Org. no. 979489498 Limited company (AS) Hustadvika Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 103.2m
Operating profit NOK 6.1m
Equity NOK 45.8m
Incorporated 1997
Employees 38
Share capital NOK 10.0m

VISNES KALK AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 979489498. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 1997 and has 38 registered employees. Registered share capital is NOK 10.0m, divided into 10000 shares. The company's stated purpose is: “Bergverksvirksomhet og det som naturlig står i forbindelse, hermed deltagelse i andre foretak med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 103.2m in revenue and NOK 6.1m in operating profit.

Key figures · 2024

Revenue
NOK 103.2m
Operating profit
NOK 6.1m
Equity
NOK 45.8m
Est. value
NOK 40.0m

Financial health · 2024

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

Who owns VISNES KALK AS?

VISNES KALK OG MARMORBRUDD AS
VISNES KALK AS
NOK 103.2m rev. · NOK 6.1m profit

VISNES KALK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISNES KALK AS

Who owns VISNES KALK AS?

VISNES KALK OG MARMORBRUDD AS is the largest registered owner, with 100.0%.

What is the revenue of VISNES KALK AS?

VISNES KALK AS had revenue of NOK 103.2m in 2024.

Who is the general manager of VISNES KALK AS?

Lars Emil Storvik Eide is registered as general manager of VISNES KALK AS.

Where is VISNES KALK AS based?

VISNES KALK AS has its business address in Lyngstad.

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.