BIZTRAC BETA
Construction of residential and non-residential buildings

SAD BYGG AS

Org. no. 922415846 Limited company (AS) Sykkylven Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 97,000
Equity NOK 317,000
Incorporated 2019
Share capital NOK 30,000

SAD BYGG AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 922415846. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Oppføring av bygninger og andre produkter/tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 97,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 97,000
Equity
NOK 317,000
Est. value
NOK 504,000

Financial health · 2024

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

Who owns SAD BYGG AS?

DARIUSZ JOZEF SADOWSKI
SAD BYGG AS
NOK 1.8m rev. · NOK 97,000 profit

SAD BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SAD BYGG AS

Who owns SAD BYGG AS?

DARIUSZ JOZEF SADOWSKI is the largest registered owner, with 50.0%.

What is the revenue of SAD BYGG AS?

SAD BYGG AS had revenue of NOK 1.8m in 2024.

Who is the general manager of SAD BYGG AS?

Slawomir Sadowski is registered as general manager of SAD BYGG AS.

Where is SAD BYGG AS based?

SAD BYGG AS has its business address in Straumgjerde.

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.