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

ØSTFOLD BETONGSAGING AS

Org. no. 956634784 Limited company (AS) Sarpsborg Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 11.7m
Operating profit NOK 1.1m
Equity NOK 4.4m
Incorporated 1990
Employees 11
Share capital NOK 102,000

Signals

1 flags
  • Nylig endring 2026-06-18 Avregistrert registrert 2026-06-18.

ØSTFOLD BETONGSAGING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 956634784. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 1990 and has 11 registered employees. Registered share capital is NOK 102,000, divided into 1020 shares. The company's stated purpose is: “Betongsaging-, betongboring-, rivningsarbeider-, kantsten og beleggningssten, samt arbeider som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 11.7m
Operating profit
NOK 1.1m
Equity
NOK 4.4m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns ØSTFOLD BETONGSAGING AS?

ANDERS RINGSRØD
ØSTFOLD BETONGSAGING AS
NOK 11.7m rev. · NOK 1.1m profit

ØSTFOLD BETONGSAGING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØSTFOLD BETONGSAGING AS

Who owns ØSTFOLD BETONGSAGING AS?

ANDERS RINGSRØD is the largest registered owner, with 40.0%.

What is the revenue of ØSTFOLD BETONGSAGING AS?

ØSTFOLD BETONGSAGING AS had revenue of NOK 11.7m in 2025.

Where is ØSTFOLD BETONGSAGING AS based?

ØSTFOLD BETONGSAGING AS has its business address in Sarpsborg.

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.