BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

Veblungsnes Sandtak A/S

Org. no. 917096147 Limited company (AS) Rauma Incorporated 1968 Active
Ownership graph ↗
Revenue 2024 NOK 16.2m
Operating profit NOK 2.0m
Equity NOK 9.9m
Incorporated 1968
Employees 13
Share capital NOK 732,000

Veblungsnes Sandtak A/S is registered as a limited company in Rauma, Møre og Romsdal with organisation number 917096147. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 1968 and has 13 registered employees. Registered share capital is NOK 732,000. The company's stated purpose is: “Drive og erverve sandtak og fast eiendom, rederi- virksomhet, sementvareproduksjon og handel.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 16.2m
Operating profit
NOK 2.0m
Equity
NOK 9.9m
Est. value
NOK 10.7m

Financial health · 2024

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

Who owns Veblungsnes Sandtak A/S?

JOHN KROGSÆTER
Veblungsnes Sandtak A/S
NOK 16.2m rev. · NOK 2.0m profit

Veblungsnes Sandtak A/S has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about Veblungsnes Sandtak A/S

Who owns Veblungsnes Sandtak A/S?

JOHN KROGSÆTER is the largest registered owner, with 45.9%.

What is the revenue of Veblungsnes Sandtak A/S?

Veblungsnes Sandtak A/S had revenue of NOK 16.2m in 2024.

Who is the general manager of Veblungsnes Sandtak A/S?

John Krogsæter is registered as general manager of Veblungsnes Sandtak A/S.

Where is Veblungsnes Sandtak A/S based?

Veblungsnes Sandtak A/S has its business address in Veblungsnes.

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.