BIZTRAC BETA
Construction of residential and non-residential buildings

SANDSBRÅTEN BYGG AS

Org. no. 998082927 Limited company (AS) Sigdal Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 12.0m
Operating profit NOK 1.6m
Equity NOK 5.9m
Incorporated 2012
Employees 7
Share capital NOK 30,000

SANDSBRÅTEN BYGG AS is registered as a limited company in Sigdal, Buskerud with organisation number 998082927. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Oppsett av nybygg og påbygg, vedlikehold og restaurering av eksisterende bygg og vaktmestertjenester, herunder snøbrøyting.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.0m in revenue and NOK 1.6m in operating profit.

Key figures · 2025

Revenue
NOK 12.0m
Operating profit
NOK 1.6m
Equity
NOK 5.9m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns SANDSBRÅTEN BYGG AS?

BREDE SANDSBRÅTEN
SANDSBRÅTEN BYGG AS
NOK 12.0m rev. · NOK 1.6m profit

SANDSBRÅTEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDSBRÅTEN BYGG AS

Who owns SANDSBRÅTEN BYGG AS?

BREDE SANDSBRÅTEN is the largest registered owner, with 100.0%.

What is the revenue of SANDSBRÅTEN BYGG AS?

SANDSBRÅTEN BYGG AS had revenue of NOK 12.0m in 2025.

Who is the general manager of SANDSBRÅTEN BYGG AS?

Brede Sandsbråten is registered as general manager of SANDSBRÅTEN BYGG AS.

Where is SANDSBRÅTEN BYGG AS based?

SANDSBRÅTEN BYGG AS has its business address in Prestfoss.

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.