BIZTRAC BETA
Other specialised construction activities n.e.c.

BJELLAND BETONGSAGING AS

Org. no. 921294786 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 778,000
Equity NOK 1.1m
Incorporated 2018
Share capital NOK 600,000

BJELLAND BETONGSAGING AS is registered as a limited company in Stavanger, Rogaland with organisation number 921294786. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2018. Registered share capital is NOK 600,000, divided into 600 shares. The company's stated purpose is: “Betongsaging og annet som naturlig faller sammen med dette, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 778,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 778,000
Equity
NOK 1.1m
Est. value
NOK 2.8m

Financial health · 2025

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.1%
Good
Equity as a share of total capital

Who owns BJELLAND BETONGSAGING AS?

ERLEND RYBBERDT BJELLAND
BJELLAND BETONGSAGING AS
NOK 4.0m rev. · NOK 778,000 profit

BJELLAND BETONGSAGING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BJELLAND BETONGSAGING AS own?

BJELLAND BETONGSAGING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJELLAND BETONGSAGING AS

Who owns BJELLAND BETONGSAGING AS?

ERLEND RYBBERDT BJELLAND is the largest registered owner, with 25.0%.

What is the revenue of BJELLAND BETONGSAGING AS?

BJELLAND BETONGSAGING AS had revenue of NOK 4.0m in 2025.

Where is BJELLAND BETONGSAGING AS based?

BJELLAND BETONGSAGING AS has its business address in Fogn.

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.