biztrac. BETA
COMPANY REGISTER PROFILE
989214594 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Processing and finishing of plastic products

LOK HOLDING AS

Org. no. 989214594 Limited company (AS) Stryn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 1.1m
Equity NOK 6.7m
Incorporated 2005
Share capital NOK 2.1m

LOK HOLDING AS is registered as a limited company in Stryn, Vestland with organisation number 989214594. The business is classified under processing and finishing of plastic products (NACE 22.250). The company was incorporated in 2005. Registered share capital is NOK 2.1m, divided into 890 shares. The company's stated purpose is: “Kjøp, sal og forvaltning av aksjar og fast eigedom og dessutan utøve dei funksjonane som normalt ligg under rolla som holdingselskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▼ −68 %
Operating profit
NOK 1.1m
▼ −69 %
Equity
NOK 6.7m
▼ −0 %
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns LOK HOLDING AS?

LOK HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does LOK HOLDING AS own?

LOK HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

LOK HOLDING AS er morselskap for 2 datterselskaper:

Frequently asked questions about LOK HOLDING AS

Who owns LOK HOLDING AS?

Sigmund Kjøsnes is the largest registered owner, with 30.0%.

What is the revenue of LOK HOLDING AS?

LOK HOLDING AS had revenue of NOK 1.1m in 2025.

Where is LOK HOLDING AS based?

LOK HOLDING AS has its business address in Stryn.

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

Report a problem

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