biztrac. BETA
COMPANY REGISTER PROFILE
984755961 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Radio broadcasting and audio distribution activities

RADIO RJUKAN AS

Org. no. 984755961 Limited company (AS) Tinn Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 132,000
Equity NOK 106,000
Incorporated 2002
Share capital NOK 186,000

RADIO RJUKAN AS is registered as a limited company in Tinn, Telemark with organisation number 984755961. The business is classified under radio broadcasting and audio distribution activities (NACE 60.100). The company was incorporated in 2002. Registered share capital is NOK 186,000, divided into 186 shares. The company's stated purpose is: “Kringkasting innenfor konsesjonsvilkårene.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 132,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▼ −3 %
Operating profit
NOK 132,000
▲ +181 %
Equity
NOK 106,000
▲ +451 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
38.1%
Very good
Return on total assets
Solidity
37.5%
Good
Equity as a share of total capital

Who owns RADIO RJUKAN AS?

RADIO RJUKAN AS has 6 registered shareholders:

All shareholders and roles →

Which companies does RADIO RJUKAN AS own?

RADIO RJUKAN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RADIO RJUKAN AS

Who owns RADIO RJUKAN AS?

RADIO VEST TELEMARK AS is the largest registered owner, with 80.6%.

What is the revenue of RADIO RJUKAN AS?

RADIO RJUKAN AS had revenue of NOK 1.9m in 2025.

Who is the general manager of RADIO RJUKAN AS?

Ole Jon Tveito is registered as general manager of RADIO RJUKAN AS.

Where is RADIO RJUKAN AS based?

RADIO RJUKAN AS has its business address in Rjukan.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.