BIZTRAC BETA
Motion picture, video and television programme production activities

TRONTV AS

Org. no. 827492442 Limited company (AS) Alvdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 324,000
Operating profit NOK −21,000
Equity NOK 87,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

TRONTV AS is registered as a limited company in Alvdal, Innlandet with organisation number 827492442. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Film, lyd og medieproduksjon samt investering i aksjer, eiendom og andre eierandeler samt tilsvarende og annen type virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 324,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2025

Revenue
NOK 324,000
Operating profit
NOK −21,000
Equity
NOK 87,000
Est. value
NOK 586,000

Financial health · 2025

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.5%
Weak
Equity as a share of total capital

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

Who owns TRONTV AS?

RUNE SKOGHEIM
TRONTV AS
NOK 324,000 rev. · NOK −21,000 profit

TRONTV AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONTV AS

Who owns TRONTV AS?

RUNE SKOGHEIM is the largest registered owner, with 100.0%.

What is the revenue of TRONTV AS?

TRONTV AS had revenue of NOK 324,000 in 2025.

Who is the general manager of TRONTV AS?

Rune Skogheim is registered as general manager of TRONTV AS.

Where is TRONTV AS based?

TRONTV AS has its business address in Alvdal.

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.