BIZTRAC BETA
Motion picture, video and television programme production activities

VISION QUEST AS

Org. no. 924421053 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 451,000
Equity NOK 413,000
Incorporated 2020
Share capital NOK 30,000

VISION QUEST AS is registered as a limited company in Oslo, Oslo with organisation number 924421053. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulenttjenster og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 451,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 451,000
Equity
NOK 413,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns VISION QUEST AS?

PAUL LEONARD WHITE
VISION QUEST AS
NOK 1.8m rev. · NOK 451,000 profit

VISION QUEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VISION QUEST AS own?

VISION QUEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VISION QUEST AS

Who owns VISION QUEST AS?

PAUL LEONARD WHITE is the largest registered owner, with 100.0%.

What is the revenue of VISION QUEST AS?

VISION QUEST AS had revenue of NOK 1.8m in 2025.

Who is the general manager of VISION QUEST AS?

Paul Leonard White is registered as general manager of VISION QUEST AS.

Where is VISION QUEST AS based?

VISION QUEST AS has its business address in Oslo.

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.