BIZTRAC BETA
Repair and maintenance of motor vehicles

KORK HOLDING AS

Org. no. 814870812 Limited company (AS) Nord-Fron Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −24,000
Equity NOK 15.3m
Incorporated 2015
Share capital NOK 290,000

Signals

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

KORK HOLDING AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 814870812. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2015. Registered share capital is NOK 290,000, divided into 30 shares. The company's stated purpose is: “Deltagelse i andre selskaper gjennom eie av aksjer og verdipapirer, samt forvaltning av avkastningen av dette i annen investerings- eller næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 15.3m
Est. value
NOK 11.9m

Financial health · 2024

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

Who owns KORK HOLDING AS?

KRISTIAN OPSAHL
KORK HOLDING AS
NOK 0 rev. · NOK −24,000 profit

KORK HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does KORK HOLDING AS own?

KORK HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KORK HOLDING AS

Who owns KORK HOLDING AS?

KRISTIAN OPSAHL is the largest registered owner, with 60.0%.

What is the revenue of KORK HOLDING AS?

KORK HOLDING AS had revenue of NOK 0 in 2024.

Where is KORK HOLDING AS based?

KORK HOLDING AS has its business address in Vinstra.

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.