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

SYLTEMOA SANDTAK AS

Org. no. 976482425 Limited company (AS) Fjord Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 25.0m
Operating profit NOK 964,000
Equity NOK 16.2m
Incorporated 1996
Employees 7
Share capital NOK 100,000

SYLTEMOA SANDTAK AS is registered as a limited company in Fjord, Møre og Romsdal with organisation number 976482425. 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 1996 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Drive sanduttak, betongproduksjon og det som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 25.0m in revenue and NOK 964,000 in operating profit.

Key figures · 2024

Revenue
NOK 25.0m
Operating profit
NOK 964,000
Equity
NOK 16.2m
Est. value
NOK 11.6m

Financial health · 2024

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

Who owns SYLTEMOA SANDTAK AS?

PETER JARL MELCHIOR
SYLTEMOA SANDTAK AS
NOK 25.0m rev. · NOK 964,000 profit

SYLTEMOA SANDTAK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SYLTEMOA SANDTAK AS own?

SYLTEMOA SANDTAK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SYLTEMOA SANDTAK AS

Who owns SYLTEMOA SANDTAK AS?

PETER JARL MELCHIOR is the largest registered owner, with 100.0%.

What is the revenue of SYLTEMOA SANDTAK AS?

SYLTEMOA SANDTAK AS had revenue of NOK 25.0m in 2024.

Where is SYLTEMOA SANDTAK AS based?

SYLTEMOA SANDTAK AS has its business address in Valldal.

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.