BIZTRAC BETA
Site preparation

SIRDAL BETONG AS

Org. no. 997490126 Limited company (AS) Sirdal Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 674,000
Equity NOK −820,000
Incorporated 2011
Share capital NOK 355,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−820k kr).

SIRDAL BETONG AS is registered as a limited company in Sirdal, Agder with organisation number 997490126. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2011. Registered share capital is NOK 355,000, divided into 355 shares. The company's stated purpose is: “Drifte betongblanderi og drive entreprenørvirksomhet og transport og alt som hermed står i forbindelse, samt delta i andre virksomheter”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 674,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 674,000
Equity
NOK −820,000
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-141.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SIRDAL BETONG AS?

TORLEIV JOSDAL
SIRDAL BETONG AS
NOK 1.5m rev. · NOK 674,000 profit

SIRDAL BETONG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIRDAL BETONG AS

Who owns SIRDAL BETONG AS?

TORLEIV JOSDAL is the largest registered owner, with 50.7%.

What is the revenue of SIRDAL BETONG AS?

SIRDAL BETONG AS had revenue of NOK 1.5m in 2024.

Who is the general manager of SIRDAL BETONG AS?

Torleiv Josdal is registered as general manager of SIRDAL BETONG AS.

Where is SIRDAL BETONG AS based?

SIRDAL BETONG AS has its business address in Tonstad.

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.