BIZTRAC BETA
COMPANY REGISTER PROFILE
932602156 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

UH HOLDING AS

Org. no. 932602156 Limited company (AS) Narvik Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −86,000
Equity NOK 2.3m
Incorporated 2023
Share capital NOK 30,000

Signals

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

UH HOLDING AS is registered as a limited company in Narvik, Nordland with organisation number 932602156. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 5 shares. The company's stated purpose is: “Investering i andre selskaper med økonomisk formål.”.

Key figures · 2025

Operating profit
NOK −86,000
Equity
NOK 2.3m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns UH HOLDING AS?

UH HOLDING AS
· NOK −86,000 profit

UH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about UH HOLDING AS

Who owns UH HOLDING AS?

ULF ANDERS HØIEM is the largest registered owner, with 100.0%.

Who is the general manager of UH HOLDING AS?

Ulf Anders Høiem is registered as general manager of UH HOLDING AS.

Where is UH HOLDING AS based?

UH HOLDING AS has its business address in Narvik.

Property

Business address c/o Ulf Høiem Selsbanes gate 59, 8514 Narvik
Cadastral unit 1806-40/435/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.