BIZTRAC BETA
Wholesale of other household goods

UHLMANNS AS

Org. no. 977302013 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 55,000
Operating profit NOK 55,000
Equity NOK −196,000
Incorporated 1997
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−196k kr).

UHLMANNS AS is registered as a limited company in Oslo, Oslo with organisation number 977302013. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 1997. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Import og eksport primært til glass- og ramme- bransjen. Deltakelse i andre selskaper og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 55,000 in revenue and NOK 55,000 in operating profit.

Key figures · 2025

Revenue
NOK 55,000
Operating profit
NOK 55,000
Equity
NOK −196,000
Est. value
NOK 289,000

Financial health · 2025

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

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

Who owns UHLMANNS AS?

KIRSTI KUBICA HAMMERØ UHLMANN
UHLMANNS AS
NOK 55,000 rev. · NOK 55,000 profit

UHLMANNS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about UHLMANNS AS

Who owns UHLMANNS AS?

KIRSTI KUBICA HAMMERØ UHLMANN is the largest registered owner, with 80.0%.

What is the revenue of UHLMANNS AS?

UHLMANNS AS had revenue of NOK 55,000 in 2025.

Who is the general manager of UHLMANNS AS?

Kirsti Kubica Hammerø Uhlmann is registered as general manager of UHLMANNS AS.

Where is UHLMANNS AS based?

UHLMANNS AS has its business address in Oslo.

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.