BIZTRAC BETA
Computer programming activities

THORSVOLL MEDIA AS

Org. no. 930775428 Limited company (AS) Røros Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK 864
Equity NOK 14,000
Incorporated 2022
Share capital NOK 30,000

THORSVOLL MEDIA AS is registered as a limited company in Røros, Trøndelag with organisation number 930775428. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen webdesign - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK 864 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
Operating profit
NOK 864
Equity
NOK 14,000
Est. value
NOK 14,000

Financial health · 2025

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

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

Who owns THORSVOLL MEDIA AS?

HENNING THORSVOLL
THORSVOLL MEDIA AS
NOK 6,000 rev. · NOK 864 profit

THORSVOLL MEDIA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about THORSVOLL MEDIA AS

Who owns THORSVOLL MEDIA AS?

HENNING THORSVOLL is the largest registered owner, with 83.3%.

What is the revenue of THORSVOLL MEDIA AS?

THORSVOLL MEDIA AS had revenue of NOK 6,000 in 2025.

Who is the general manager of THORSVOLL MEDIA AS?

Henning Thorsvoll is registered as general manager of THORSVOLL MEDIA AS.

Where is THORSVOLL MEDIA AS based?

THORSVOLL MEDIA AS has its business address in Brekkebygd.

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.