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

KVINESDAL STEIN AS

Org. no. 995428598 Limited company (AS) Kvinesdal Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 690,000
Operating profit NOK 350,000
Equity NOK 1.1m
Incorporated 2010
Share capital NOK 102,000

KVINESDAL STEIN AS is registered as a limited company in Kvinesdal, Agder with organisation number 995428598. 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 2010. Registered share capital is NOK 102,000, divided into 102 shares. The company's stated purpose is: “Utvinning, foredling og salg av stein, fyllmasse og tilhørende produkter og tjenester, maskinentreprenørarbeid og deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 690,000 in revenue and NOK 350,000 in operating profit.

Key figures · 2025

Revenue
NOK 690,000
Operating profit
NOK 350,000
Equity
NOK 1.1m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns KVINESDAL STEIN AS?

FRODE RAFOSS
KVINESDAL STEIN AS
NOK 690,000 rev. · NOK 350,000 profit

KVINESDAL STEIN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KVINESDAL STEIN AS

Who owns KVINESDAL STEIN AS?

FRODE RAFOSS is the largest registered owner, with 33.3%.

What is the revenue of KVINESDAL STEIN AS?

KVINESDAL STEIN AS had revenue of NOK 690,000 in 2025.

Who is the general manager of KVINESDAL STEIN AS?

Markus Hobbesland Solberg is registered as general manager of KVINESDAL STEIN AS.

Where is KVINESDAL STEIN AS based?

KVINESDAL STEIN AS has its business address in Kvinesdal.

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.