BIZTRAC BETA
COMPANY REGISTER PROFILE
988838225 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Buying and selling of own real estate

LARS HOLDING AS

Org. no. 988838225 Limited company (AS) Hol Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 150,000
Operating profit NOK 65,000
Equity NOK 8.8m
Incorporated 2005
Share capital NOK 774,000

LARS HOLDING AS is registered as a limited company in Hol, Buskerud with organisation number 988838225. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 774,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av fast eiendom, eierskap og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 150,000 in revenue and NOK 65,000 in operating profit.

Key figures · 2025

Revenue
NOK 150,000
Operating profit
NOK 65,000
Equity
NOK 8.8m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns LARS HOLDING AS?

LARS HOLDING AS
NOK 150,000 rev. · NOK 65,000 profit

LARS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LARS HOLDING AS own?

LARS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LARS HOLDING AS

Who owns LARS HOLDING AS?

LARS UTHUS is the largest registered owner, with 100.0%.

What is the revenue of LARS HOLDING AS?

LARS HOLDING AS had revenue of NOK 150,000 in 2025.

Who is the general manager of LARS HOLDING AS?

Lars Uthus is registered as general manager of LARS HOLDING AS.

Where is LARS HOLDING AS based?

LARS HOLDING AS has its business address in Geilo.

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.