BIZTRAC BETA
Motion picture, video and television programme production activities

HOVENG MEDIA AS

Org. no. 997904516 Limited company (AS) Rennebu Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2012
Share capital NOK 50,000

HOVENG MEDIA AS is registered as a limited company in Rennebu, Trøndelag with organisation number 997904516. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Produksjon av film, video og fjernsynsprogrammer. Etterarbeid knyttet til produksjon av film, video og fjernsynsprogrammer, med dertil tilhørende virksomhet. Videresalg av foto-, video-, lyd- og lysutstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns HOVENG MEDIA AS?

JON OLAV VOLL
HOVENG MEDIA AS
NOK 0 rev. · NOK 0 profit

HOVENG MEDIA AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOVENG MEDIA AS

Who owns HOVENG MEDIA AS?

JON OLAV VOLL is the largest registered owner, with 51.0%.

What is the revenue of HOVENG MEDIA AS?

HOVENG MEDIA AS had revenue of NOK 0 in 2024.

Who is the general manager of HOVENG MEDIA AS?

Jon Olav Voll is registered as general manager of HOVENG MEDIA AS.

Where is HOVENG MEDIA AS based?

HOVENG MEDIA AS has its business address in Rennebu.

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.