BIZTRAC BETA
Construction of residential and non-residential buildings

STUGUDAL BYGG AS

Org. no. 916776462 Limited company (AS) Tydal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −11,000
Equity NOK 161,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

STUGUDAL BYGG AS is registered as a limited company in Tydal, Trøndelag with organisation number 916776462. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Bygge -og anleggsvirksomhet, samt virksomhet forbundet med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −11,000
Equity
NOK 161,000
Est. value
NOK 694,000

Financial health · 2025

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

Who owns STUGUDAL BYGG AS?

KONSTANTIN UDALOV
STUGUDAL BYGG AS
NOK 1.8m rev. · NOK −11,000 profit

STUGUDAL BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STUGUDAL BYGG AS

Who owns STUGUDAL BYGG AS?

KONSTANTIN UDALOV is the largest registered owner, with 100.0%.

What is the revenue of STUGUDAL BYGG AS?

STUGUDAL BYGG AS had revenue of NOK 1.8m in 2025.

Who is the general manager of STUGUDAL BYGG AS?

Konstantin Udalov is registered as general manager of STUGUDAL BYGG AS.

Where is STUGUDAL BYGG AS based?

STUGUDAL BYGG AS has its business address in Tydal.

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.