BIZTRAC BETA
Motion picture, video and television programme post-production activities

VIZWORK AS

Org. no. 989972588 Limited company (AS) Trondheim Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −130,000
Equity NOK 192,000
Incorporated 2006
Share capital NOK 100,000

Signals

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

VIZWORK AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989972588. The business is classified under motion picture, video and television programme post-production activities (NACE 59.120). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive med design, film, videoproduksjon og webutvikling, samt hva som hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −130,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −130,000
Equity
NOK 192,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns VIZWORK AS?

ROGER NYHEIM
VIZWORK AS
NOK 1.0m rev. · NOK −130,000 profit

VIZWORK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VIZWORK AS

Who owns VIZWORK AS?

ROGER NYHEIM is the largest registered owner, with 100.0%.

What is the revenue of VIZWORK AS?

VIZWORK AS had revenue of NOK 1.0m in 2025.

Who is the general manager of VIZWORK AS?

Roger Nyheim is registered as general manager of VIZWORK AS.

Where is VIZWORK AS based?

VIZWORK AS has its business address in Trondheim.

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.