BIZTRAC BETA
Other real estate activities on a fee or contract basis

UGLEM HOLDING AS

Org. no. 917144729 Limited company (AS) Trondheim Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 20,000
Equity NOK 1.1m
Incorporated 2016
Share capital NOK 91,000

Signals

1 flags
  • Nylig endring 2026-05-31 Adresseendring registrert 2026-05-31.

UGLEM HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 917144729. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2016. Registered share capital is NOK 91,000, divided into 91 shares. The company's stated purpose is: “Eie, utvikle og gjøre seg interessert i foretak som utvikler renovasjonsløsninger, samt andre aktiviteter forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 20,000
Equity
NOK 1.1m
Est. value
NOK 801,000

Financial health · 2024

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

Who owns UGLEM HOLDING AS?

ERLEND UGLEM
UGLEM HOLDING AS
NOK 0 rev. · NOK 20,000 profit

UGLEM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UGLEM HOLDING AS own?

UGLEM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about UGLEM HOLDING AS

Who owns UGLEM HOLDING AS?

ERLEND UGLEM is the largest registered owner, with 100.0%.

What is the revenue of UGLEM HOLDING AS?

UGLEM HOLDING AS had revenue of NOK 0 in 2024.

Where is UGLEM HOLDING AS based?

UGLEM HOLDING AS has its business address in Ranheim.

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.