BIZTRAC BETA
Rental and operating of own or leased real estate

LKS HOLDING AS

Org. no. 989098748 Limited company (AS) Sandnes Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 26,000
Operating profit NOK −48,000
Equity NOK 4.6m
Incorporated 2005
Share capital NOK 1.0m

Signals

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

LKS HOLDING AS is registered as a limited company in Sandnes, Rogaland with organisation number 989098748. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1010 shares. The company's stated purpose is: “Kjøp og salg av aksjer og verdipapirer, herunder deltakelse i andre selskaper for utøvelse av aktivt eierskap, bobilutleie samt kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 26,000 in revenue and NOK −48,000 in operating profit.

Key figures · 2025

Revenue
NOK 26,000
Operating profit
NOK −48,000
Equity
NOK 4.6m
Est. value
NOK 3.8m

Financial health · 2025

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

Who owns LKS HOLDING AS?

LARS KÅRE SKÅR
LKS HOLDING AS
NOK 26,000 rev. · NOK −48,000 profit

LKS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LKS HOLDING AS own?

LKS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LKS HOLDING AS

Who owns LKS HOLDING AS?

LARS KÅRE SKÅR is the largest registered owner, with 100.0%.

What is the revenue of LKS HOLDING AS?

LKS HOLDING AS had revenue of NOK 26,000 in 2025.

Where is LKS HOLDING AS based?

LKS HOLDING AS has its business address in Sandnes.

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.