biztrac. BETA
COMPANY REGISTER PROFILE
989024833 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

UGLE HOLDING AS

Org. no. 989024833 Limited company (AS) Larvik Incorporated 2005 Active
Revenue 2025 NOK 16,000
Operating profit NOK −6,000
Equity NOK 408,000
Incorporated 2005
Share capital NOK 30,000

Signals

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

UGLE HOLDING AS is registered as a limited company in Larvik, Vestfold with organisation number 989024833. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 6000 shares. The company's stated purpose is: “Investering i aksjer og andeler, rådgivning og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 16,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 16,000
▲ +3 %
Operating profit
NOK −6,000
▲ +86 %
Equity
NOK 408,000
▲ +47 %
Est. value
NOK 957,000

Financial health · 2025

Liquidity
100.91
Very good
Current assets ÷ current liabilities
Profitability
65.2%
Very good
Return on total assets
Solidity
99.3%
Very good
Equity as a share of total capital

Who owns UGLE HOLDING AS?

UGLE HOLDING AS
NOK 16,000 rev. · NOK −6,000 profit

UGLE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does UGLE HOLDING AS own?

UGLE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about UGLE HOLDING AS

Who owns UGLE HOLDING AS?

Frode Henry is the largest registered owner, with 100.0%.

What is the revenue of UGLE HOLDING AS?

UGLE HOLDING AS had revenue of NOK 16,000 in 2025.

Where is UGLE HOLDING AS based?

UGLE HOLDING AS has its business address in Larvik.

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

Report a problem

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