BIZTRAC BETA
Traditional, complementary and alternative medicine activities

LCS HOLDING AS

Org. no. 918116680 Limited company (AS) Arendal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 993,000
Operating profit NOK 162,000
Equity NOK 1.8m
Incorporated 2016
Share capital NOK 80,000

LCS HOLDING AS is registered as a limited company in Arendal, Agder with organisation number 918116680. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2016. Registered share capital is NOK 80,000, divided into 80 shares. The company's stated purpose is: “Praksis som kiropraktor. Utleie av personell og annet som naturlig faller inn herunder. Holdingselskap, eie, omsetning og investering i aksjer og i andre selskaper og annet som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 993,000 in revenue and NOK 162,000 in operating profit.

Key figures · 2025

Revenue
NOK 993,000
Operating profit
NOK 162,000
Equity
NOK 1.8m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns LCS HOLDING AS?

LARS-CHRISTIAN STIG
LCS HOLDING AS
NOK 993,000 rev. · NOK 162,000 profit

LCS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LCS HOLDING AS own?

LCS HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LCS HOLDING AS

Who owns LCS HOLDING AS?

LARS-CHRISTIAN STIG is the largest registered owner, with 100.0%.

What is the revenue of LCS HOLDING AS?

LCS HOLDING AS had revenue of NOK 993,000 in 2025.

Where is LCS HOLDING AS based?

LCS HOLDING AS has its business address in Arendal.

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.