BIZTRAC BETA
Retail sale of medical and orthopaedic goods

LAUVLAND HOLDING AS

Org. no. 989298364 Limited company (AS) Grimstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 2.3m
Equity NOK 11.4m
Incorporated 2005
Share capital NOK 100,000

LAUVLAND HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 989298364. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringer og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 2.3m
Equity
NOK 11.4m
Est. value
NOK 14.5m

Financial health · 2024

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

Who owns LAUVLAND HOLDING AS?

KOLBJØRN LAUVLAND
LAUVLAND HOLDING AS
NOK 2.4m rev. · NOK 2.3m profit

LAUVLAND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LAUVLAND HOLDING AS own?

LAUVLAND HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LAUVLAND HOLDING AS

Who owns LAUVLAND HOLDING AS?

KOLBJØRN LAUVLAND is the largest registered owner, with 100.0%.

What is the revenue of LAUVLAND HOLDING AS?

LAUVLAND HOLDING AS had revenue of NOK 2.4m in 2024.

Who is the general manager of LAUVLAND HOLDING AS?

Kolbjørn Lauvland is registered as general manager of LAUVLAND HOLDING AS.

Where is LAUVLAND HOLDING AS based?

LAUVLAND HOLDING AS has its business address in Grimstad.

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.