BIZTRAC BETA
Painting and glazing

U&M HOLDING AS

Org. no. 827857882 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 489,000
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−24k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

U&M HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 827857882. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 500 shares. The company's stated purpose is: “Investeringer i verdipapirer, fast eiendom, samt annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 489,000
Est. value
NOK 501,000

Financial health · 2024

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

Who owns U&M HOLDING AS?

PE MADSEN HOLDING AS
U&M HOLDING AS
NOK 0 rev. · NOK −24,000 profit

U&M HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does U&M HOLDING AS own?

U&M HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about U&M HOLDING AS

Who owns U&M HOLDING AS?

PE MADSEN HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of U&M HOLDING AS?

U&M HOLDING AS had revenue of NOK 0 in 2024.

Where is U&M HOLDING AS based?

U&M HOLDING AS has its business address in Skodje.

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.