BIZTRAC BETA
Site preparation

TØMRERMESTER SAGBRÅTEN AS

Org. no. 913508580 Limited company (AS) Lier Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 6.6m
Operating profit NOK 336,000
Equity NOK 373,000
Incorporated 2014
Employees 6
Share capital NOK 35,000

TØMRERMESTER SAGBRÅTEN AS is registered as a limited company in Lier, Buskerud with organisation number 913508580. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014 and has 6 registered employees. Registered share capital is NOK 35,000, divided into 35 shares. The company's stated purpose is: “Maskinentreprenør, oppføring og rehabilitering av bygg herunder betongarbeider. Herunder deltakelse i andre selskap med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK 336,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
Operating profit
NOK 336,000
Equity
NOK 373,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns TØMRERMESTER SAGBRÅTEN AS?

ROLF SAGBRÅTEN
TØMRERMESTER SAGBRÅTEN AS
NOK 6.6m rev. · NOK 336,000 profit

TØMRERMESTER SAGBRÅTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TØMRERMESTER SAGBRÅTEN AS

Who owns TØMRERMESTER SAGBRÅTEN AS?

ROLF SAGBRÅTEN is the largest registered owner, with 100.0%.

What is the revenue of TØMRERMESTER SAGBRÅTEN AS?

TØMRERMESTER SAGBRÅTEN AS had revenue of NOK 6.6m in 2025.

Who is the general manager of TØMRERMESTER SAGBRÅTEN AS?

Rolf Sagbråten is registered as general manager of TØMRERMESTER SAGBRÅTEN AS.

Where is TØMRERMESTER SAGBRÅTEN AS based?

TØMRERMESTER SAGBRÅTEN AS has its business address in Lier.

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.