BIZTRAC BETA
Civil engineering activities

UGELSTAD HOLDING AS

Org. no. 815131622 Limited company (AS) Trondheim Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −22,000
Equity NOK −112,000
Incorporated 2015
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−112k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

UGELSTAD HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 815131622. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering- og konsulenttjenester samt annen nærliggende virksomhet. Selskapet kan også erverve aksjer i andre selskap.”.

Key figures · 2025

Operating profit
NOK −22,000
Equity
NOK −112,000

Financial health · 2025

Liquidity
0.04
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-264.1%
Weak
Equity as a share of total capital

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

Who owns UGELSTAD HOLDING AS?

CHRISTIAN VOLDEN UGELSTAD
UGELSTAD HOLDING AS
· NOK −22,000 profit

UGELSTAD HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does UGELSTAD HOLDING AS own?

UGELSTAD HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about UGELSTAD HOLDING AS

Who owns UGELSTAD HOLDING AS?

CHRISTIAN VOLDEN UGELSTAD is the largest registered owner, with 50.0%.

Who is the general manager of UGELSTAD HOLDING AS?

Christian Volden Ugelstad is registered as general manager of UGELSTAD HOLDING AS.

Where is UGELSTAD HOLDING AS based?

UGELSTAD HOLDING 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.