BIZTRAC BETA
Motion picture, video and television programme production activities

POINT OF VIEW VEST AS

Org. no. 924479922 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −28,000
Equity NOK −38,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−38k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−28k kr).

POINT OF VIEW VEST AS is registered as a limited company in Bergen, Vestland with organisation number 924479922. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Produksjon av film, video og fjernsynsprogram. Snekkerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −28,000
Equity
NOK −38,000

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-14.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns POINT OF VIEW VEST AS?

INGVAR KOLBJØRNSEN
POINT OF VIEW VEST AS
NOK 1.8m rev. · NOK −28,000 profit

POINT OF VIEW VEST AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about POINT OF VIEW VEST AS

Who owns POINT OF VIEW VEST AS?

INGVAR KOLBJØRNSEN is the largest registered owner, with 40.0%.

What is the revenue of POINT OF VIEW VEST AS?

POINT OF VIEW VEST AS had revenue of NOK 1.8m in 2025.

Where is POINT OF VIEW VEST AS based?

POINT OF VIEW VEST AS has its business address in Ulset.

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.