BIZTRAC BETA
Uoppgitt

UGGLA HOLDING AS

Org. no. 922885214 Limited company (AS) Øvre Eiker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11,000
Equity NOK −17,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−17k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).

UGGLA HOLDING AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 922885214. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, eiendom og andre eierandeler, samt tilsvarende og annen type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −17,000

Financial health · 2025

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

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

Who owns UGGLA HOLDING AS?

Lars Kristian Uggla
UGGLA HOLDING AS
NOK 0 rev. · NOK −11,000 profit

UGGLA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UGGLA HOLDING AS own?

UGGLA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about UGGLA HOLDING AS

Who owns UGGLA HOLDING AS?

Lars Kristian Uggla is the largest registered owner, with 100.0%.

What is the revenue of UGGLA HOLDING AS?

UGGLA HOLDING AS had revenue of NOK 0 in 2025.

Where is UGGLA HOLDING AS based?

UGGLA HOLDING AS has its business address in Hokksund.

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.