BIZTRAC BETA
COMPANY REGISTER PROFILE
994416537 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

UTHUS HOLDING AS

Org. no. 994416537 Limited company (AS) Luster Incorporated 2009 Active
Ownership graph ↗
Operating profit NOK −494,000
Equity NOK 6.8m
Incorporated 2009
Share capital NOK 100,000

Signals

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

UTHUS HOLDING AS is registered as a limited company in Luster, Vestland with organisation number 994416537. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer, andeler og andre verdipapirer, samt kjøp, salg og forvaltning av fast eiendom og deltakelse i selskap med lignende formål.”.

Former names: ELLEVILT AS

Key figures · 2025

Operating profit
NOK −494,000
▲ +68 %
Equity
NOK 6.8m
▲ +17 %
Est. value
NOK 11.7m

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
17.2%
Very good
Return on total assets
Solidity
32.3%
Good
Equity as a share of total capital

Who owns UTHUS HOLDING AS?

UTHUS HOLDING AS
· NOK −494,000 profit

UTHUS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does UTHUS HOLDING AS own?

UTHUS HOLDING AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about UTHUS HOLDING AS

Who owns UTHUS HOLDING AS?

OLE JONNY UTHUS is the largest registered owner, with 70.0%.

Who is the general manager of UTHUS HOLDING AS?

Morten Hole Uthus is registered as general manager of UTHUS HOLDING AS.

Where is UTHUS HOLDING AS based?

UTHUS HOLDING AS has its business address in Gaupne.

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

Report a problem

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