BIZTRAC BETA
Construction of residential and non-residential buildings

SD BYGG & EIENDOM AS

Org. no. 918871969 Limited company (AS) Sogndal Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 951,000
Operating profit NOK 31,000
Equity NOK 114,000
Incorporated 2017
Share capital NOK 30,000

SD BYGG & EIENDOM AS is registered as a limited company in Sogndal, Vestland with organisation number 918871969. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Snekker/tømrer arbeid, rehabilitering av bygg, oppføring av bygg for andre, kjøp og salg av eiendom. Oppsetting av boliger. Og alt som er forbundet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 951,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2025

Revenue
NOK 951,000
Operating profit
NOK 31,000
Equity
NOK 114,000
Est. value
NOK 137,000

Financial health · 2025

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

Who owns SD BYGG & EIENDOM AS?

STEINAR DAHL
SD BYGG & EIENDOM AS
NOK 951,000 rev. · NOK 31,000 profit

SD BYGG & EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SD BYGG & EIENDOM AS

Who owns SD BYGG & EIENDOM AS?

STEINAR DAHL is the largest registered owner, with 100.0%.

What is the revenue of SD BYGG & EIENDOM AS?

SD BYGG & EIENDOM AS had revenue of NOK 951,000 in 2025.

Who is the general manager of SD BYGG & EIENDOM AS?

Steinar Dahl is registered as general manager of SD BYGG & EIENDOM AS.

Where is SD BYGG & EIENDOM AS based?

SD BYGG & EIENDOM AS has its business address in Sogndal.

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.