BIZTRAC BETA
Radio broadcasting and audio distribution activities

TROMSØ MEDIA AS

Org. no. 996593037 Limited company (AS) Tromsø Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 135,000
Operating profit NOK −272,000
Equity NOK −1.7m
Incorporated 2011
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,7 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−272k kr).

TROMSØ MEDIA AS is registered as a limited company in Tromsø, Troms with organisation number 996593037. The business is classified under radio broadcasting and audio distribution activities (NACE 60.100). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive radiokringkasting, samt deltakelse i andre virksomheter, og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 135,000 in revenue and NOK −272,000 in operating profit.

Key figures · 2024

Revenue
NOK 135,000
Operating profit
NOK −272,000
Equity
NOK −1.7m

Financial health · 2024

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

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

Who owns TROMSØ MEDIA AS?

JOHNSEN EIENDOM AS
TROMSØ MEDIA AS
NOK 135,000 rev. · NOK −272,000 profit

TROMSØ MEDIA AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TROMSØ MEDIA AS

Who owns TROMSØ MEDIA AS?

JOHNSEN EIENDOM AS is the largest registered owner, with 47.0%.

What is the revenue of TROMSØ MEDIA AS?

TROMSØ MEDIA AS had revenue of NOK 135,000 in 2024.

Where is TROMSØ MEDIA AS based?

TROMSØ MEDIA AS has its business address in Tromsø.

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.