BIZTRAC BETA
Coating of metals

VIKEN INDUSTRILAKK AS

Org. no. 921434278 Limited company (AS) Halden Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.6m
Operating profit NOK −25,000
Equity NOK 492,000
Incorporated 2018
Employees 9
Share capital NOK 35,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).

VIKEN INDUSTRILAKK AS is registered as a limited company in Halden, Østfold with organisation number 921434278. The business is classified under coating of metals (NACE 25.510). The company was incorporated in 2018 and has 9 registered employees. Registered share capital is NOK 35,000, divided into 350 shares. The company's stated purpose is: “Drift og produksjon av lakkeringsanlegg samt beslektet virksomhet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 7.6m in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.6m
Operating profit
NOK −25,000
Equity
NOK 492,000
Est. value
NOK 4.3m

Financial health · 2024

Liquidity
0.55
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.6%
Satisfactory
Equity as a share of total capital

Who owns VIKEN INDUSTRILAKK AS?

TOR KJETIL HANSEN LINDBLAD
VIKEN INDUSTRILAKK AS
NOK 7.6m rev. · NOK −25,000 profit

VIKEN INDUSTRILAKK AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIKEN INDUSTRILAKK AS

Who owns VIKEN INDUSTRILAKK AS?

TOR KJETIL HANSEN LINDBLAD is the largest registered owner, with 33.4%.

What is the revenue of VIKEN INDUSTRILAKK AS?

VIKEN INDUSTRILAKK AS had revenue of NOK 7.6m in 2024.

Who is the general manager of VIKEN INDUSTRILAKK AS?

Tor Kjetil Hansen Lindblad is registered as general manager of VIKEN INDUSTRILAKK AS.

Where is VIKEN INDUSTRILAKK AS based?

VIKEN INDUSTRILAKK AS has its business address in Tistedal.

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.