BIZTRAC BETA
Motion picture, video and television programme production activities

VISJONER AS

Org. no. 991937498 Limited company (AS) Stavanger Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 394,000
Operating profit NOK −60,000
Equity NOK 117,000
Incorporated 2007
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−60k kr).

VISJONER AS is registered as a limited company in Stavanger, Rogaland with organisation number 991937498. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kunstnerisk virksomhet innen filmproduksjon og alt som står i forbindelse med dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 394,000 in revenue and NOK −60,000 in operating profit.

Key figures · 2025

Revenue
NOK 394,000
Operating profit
NOK −60,000
Equity
NOK 117,000
Est. value
NOK 718,000

Financial health · 2024

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

Who owns VISJONER AS?

KRISTOFFER JONER
VISJONER AS
NOK 394,000 rev. · NOK −60,000 profit

VISJONER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VISJONER AS

Who owns VISJONER AS?

KRISTOFFER JONER is the largest registered owner, with 100.0%.

What is the revenue of VISJONER AS?

VISJONER AS had revenue of NOK 394,000 in 2025.

Who is the general manager of VISJONER AS?

Kristoffer Joner is registered as general manager of VISJONER AS.

Where is VISJONER AS based?

VISJONER AS has its business address in Stavanger.

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.