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

MOLDREIM SKIFER AS

Org. no. 977030315 Limited company (AS) Stryn Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 10.1m
Operating profit NOK 285,000
Equity NOK 2.6m
Incorporated 1996
Share capital NOK 1.9m

MOLDREIM SKIFER AS is registered as a limited company in Stryn, Vestland with organisation number 977030315. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 1996. Registered share capital is NOK 1.9m, divided into 1919 shares. The company's stated purpose is: “Eige og leige ut foretningsbygg i Innvik, samt produksjon av skifer, samt verksemd med tilknytning til dette, her medrekna deltaking i andre selskap med liknande verksemd.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.1m in revenue and NOK 285,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.1m
Operating profit
NOK 285,000
Equity
NOK 2.6m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns MOLDREIM SKIFER AS?

UTVIK MASKIN AS
MOLDREIM SKIFER AS
NOK 10.1m rev. · NOK 285,000 profit

MOLDREIM SKIFER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOLDREIM SKIFER AS

Who owns MOLDREIM SKIFER AS?

UTVIK MASKIN AS is the largest registered owner, with 96.6%.

What is the revenue of MOLDREIM SKIFER AS?

MOLDREIM SKIFER AS had revenue of NOK 10.1m in 2024.

Who is the general manager of MOLDREIM SKIFER AS?

Arne Hage is registered as general manager of MOLDREIM SKIFER AS.

Where is MOLDREIM SKIFER AS based?

MOLDREIM SKIFER AS has its business address in Utvik.

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.