BIZTRAC BETA
Manufacture of ready-mixed concrete

BETONG OG SAND AS

Org. no. 958992521 Limited company (AS) Farsund Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 11.6m
Operating profit NOK 225,000
Equity NOK 1.8m
Incorporated 1990
Employees 7
Share capital NOK 100,000

BETONG OG SAND AS is registered as a limited company in Farsund, Agder with organisation number 958992521. The business is classified under manufacture of ready-mixed concrete (NACE 23.630). The company was incorporated in 1990 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Betongblandeverk, samt selge sand, pukk og subbus samt drive entreprenørvirksomhet, herunder kjøp og salg av eiendommer og anleggsmaskiner, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.6m in revenue and NOK 225,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.6m
Operating profit
NOK 225,000
Equity
NOK 1.8m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns BETONG OG SAND AS?

OLAV FRESTAD
BETONG OG SAND AS
NOK 11.6m rev. · NOK 225,000 profit

BETONG OG SAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BETONG OG SAND AS

Who owns BETONG OG SAND AS?

OLAV FRESTAD is the largest registered owner, with 100.0%.

What is the revenue of BETONG OG SAND AS?

BETONG OG SAND AS had revenue of NOK 11.6m in 2024.

Who is the general manager of BETONG OG SAND AS?

Olav Frestad is registered as general manager of BETONG OG SAND AS.

Where is BETONG OG SAND AS based?

BETONG OG SAND AS has its business address in Vanse.

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.