BIZTRAC BETA
Construction of residential and non-residential buildings

STENDAHL BYGG AS

Org. no. 999048595 Limited company (AS) Trondheim Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 192,000
Operating profit NOK 130,000
Equity NOK 30,000
Incorporated 2012
Share capital NOK 30,000

STENDAHL BYGG AS is registered as a limited company in Trondheim, Trøndelag with organisation number 999048595. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Snekker- og entreprenørvirksomhet, og annen virksomhet som naturlig står i forbindelse med dette, samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 192,000 in revenue and NOK 130,000 in operating profit.

Key figures · 2025

Revenue
NOK 192,000
Operating profit
NOK 130,000
Equity
NOK 30,000
Est. value
NOK 372,000

Financial health · 2025

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

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

Who owns STENDAHL BYGG AS?

MALODAL AS
STENDAHL BYGG AS
NOK 192,000 rev. · NOK 130,000 profit

STENDAHL BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STENDAHL BYGG AS

Who owns STENDAHL BYGG AS?

MALODAL AS is the largest registered owner, with 100.0%.

What is the revenue of STENDAHL BYGG AS?

STENDAHL BYGG AS had revenue of NOK 192,000 in 2025.

Who is the general manager of STENDAHL BYGG AS?

Jørgen Hjelpdal is registered as general manager of STENDAHL BYGG AS.

Where is STENDAHL BYGG AS based?

STENDAHL BYGG 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.