BIZTRAC BETA
Rental and operating of own or leased real estate

JK VISION AS

Org. no. 989035053 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −97,000
Equity NOK 8.9m
Incorporated 2005
Share capital NOK 217,000

Signals

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

JK VISION AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989035053. 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 217,000, divided into 21680 shares. The company's stated purpose is: “Selskapets virksomhet skal være leverandør av tjenester og produkter knyttet til teknologibasert produktutvikling, konsulentvirksomhet, forskning og utvikling samt alt hva herunder står i forbindelse. Selskapet kan ved aksjeinnskudd eller på annen måte delta i andre virksomheter. Selskapet kan også forestå investeringer i fast eiendom så lenge dette står i naturlig sammenheng med selskapets virksomhet. ”.

Key figures · 2024

Operating profit
NOK −97,000
Equity
NOK 8.9m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns JK VISION AS?

JOHN ODDVAR KLEPSVIK
JK VISION AS
· NOK −97,000 profit

JK VISION AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JK VISION AS own?

JK VISION AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JK VISION AS

Who owns JK VISION AS?

JOHN ODDVAR KLEPSVIK is the largest registered owner, with 100.0%.

Where is JK VISION AS based?

JK VISION AS has its business address in Flatåsen.

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.