BIZTRAC BETA
Collection of hazardous waste

BERGMESTEREN RAUDSAND AS

Org. no. 988408999 Limited company (AS) Molde Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 37.4m
Operating profit NOK 13.2m
Equity NOK 28.9m
Incorporated 2005
Share capital NOK 3.9m

BERGMESTEREN RAUDSAND AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 988408999. The business is classified under collection of hazardous waste (NACE 38.120). The company was incorporated in 2005. Registered share capital is NOK 3.9m, divided into 150 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt alt som står i forbindelse med dette, herunder drift av deponianlegg og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 37.4m in revenue and NOK 13.2m in operating profit.

Key figures · 2024

Revenue
NOK 37.4m
Operating profit
NOK 13.2m
Equity
NOK 28.9m
Est. value
NOK 53.7m

Financial health · 2024

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.6%
Good
Equity as a share of total capital

Who owns BERGMESTEREN RAUDSAND AS?

VEIDEKKE INDUSTRI AS
BERGMESTEREN RAUDSAND AS
NOK 37.4m rev. · NOK 13.2m profit

BERGMESTEREN RAUDSAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGMESTEREN RAUDSAND AS

Who owns BERGMESTEREN RAUDSAND AS?

VEIDEKKE INDUSTRI AS is the largest registered owner, with 100.0%.

What is the revenue of BERGMESTEREN RAUDSAND AS?

BERGMESTEREN RAUDSAND AS had revenue of NOK 37.4m in 2024.

Who is the general manager of BERGMESTEREN RAUDSAND AS?

Lars Merakerås is registered as general manager of BERGMESTEREN RAUDSAND AS.

Where is BERGMESTEREN RAUDSAND AS based?

BERGMESTEREN RAUDSAND AS has its business address in Raudsand.

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.