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

HARDANGERSKIFER AS

Org. no. 968125001 Limited company (AS) Ullensvang Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 21.9m
Operating profit NOK 948,000
Equity NOK 8.3m
Incorporated 1993
Employees 13
Share capital NOK 200,000

HARDANGERSKIFER AS is registered as a limited company in Ullensvang, Vestland with organisation number 968125001. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 1993 and has 13 registered employees. Registered share capital is NOK 200,000. The company's stated purpose is: “Ta ut, foredle og selge skifer og steinprodukter samt hva der med står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.9m in revenue and NOK 948,000 in operating profit.

Key figures · 2024

Revenue
NOK 21.9m
Operating profit
NOK 948,000
Equity
NOK 8.3m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns HARDANGERSKIFER AS?

SAMLAND & SKARSTEIN HOLDING AS
HARDANGERSKIFER AS
NOK 21.9m rev. · NOK 948,000 profit

HARDANGERSKIFER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HARDANGERSKIFER AS

Who owns HARDANGERSKIFER AS?

SAMLAND & SKARSTEIN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HARDANGERSKIFER AS?

HARDANGERSKIFER AS had revenue of NOK 21.9m in 2024.

Who is the general manager of HARDANGERSKIFER AS?

Hallvard Hoås Samland is registered as general manager of HARDANGERSKIFER AS.

Where is HARDANGERSKIFER AS based?

HARDANGERSKIFER AS has its business address in Herand.

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.