BIZTRAC BETA
Other building completion and finishing

SR BETONGBORING/SAGING AS

Org. no. 996385701 Limited company (AS) Trondheim Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 23,000
Equity NOK 61,000
Incorporated 2011
Employees 11
Share capital NOK 100,000

SR BETONGBORING/SAGING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 996385701. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2011 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bygg og anlegg, betongboring/saging”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 23,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 23,000
Equity
NOK 61,000
Est. value
NOK 106,000

Financial health · 2025

Liquidity
0.50
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.4%
Weak
Equity as a share of total capital

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

Who owns SR BETONGBORING/SAGING AS?

STEINAR RØDSTEN
SR BETONGBORING/SAGING AS
NOK 5.7m rev. · NOK 23,000 profit

SR BETONGBORING/SAGING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SR BETONGBORING/SAGING AS

Who owns SR BETONGBORING/SAGING AS?

STEINAR RØDSTEN is the largest registered owner, with 100.0%.

What is the revenue of SR BETONGBORING/SAGING AS?

SR BETONGBORING/SAGING AS had revenue of NOK 5.7m in 2024.

Who is the general manager of SR BETONGBORING/SAGING AS?

Steinar Rødsten is registered as general manager of SR BETONGBORING/SAGING AS.

Where is SR BETONGBORING/SAGING AS based?

SR BETONGBORING/SAGING AS has its business address in Trondheim.

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.