BIZTRAC BETA
Plumbing installation

UHREN HOLDING AS

Org. no. 831144602 Limited company (AS) Nannestad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK 18,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

UHREN HOLDING AS is registered as a limited company in Nannestad, Akershus with organisation number 831144602. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Deltakelse i andre selskaper og kjøp, eie og salg av aksjer og andre verdipapirer og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 18,000
Est. value
NOK 19,000

Financial health · 2024

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

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

Who owns UHREN HOLDING AS?

SEBASTIAN UHREN
UHREN HOLDING AS
NOK 0 rev. · NOK −12,000 profit

UHREN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UHREN HOLDING AS own?

UHREN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about UHREN HOLDING AS

Who owns UHREN HOLDING AS?

SEBASTIAN UHREN is the largest registered owner, with 100.0%.

What is the revenue of UHREN HOLDING AS?

UHREN HOLDING AS had revenue of NOK 0 in 2024.

Where is UHREN HOLDING AS based?

UHREN HOLDING AS has its business address in Maura.

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.