BIZTRAC BETA
Publishing of newspapers

RJUKAN ARBEIDERBLAD AS

Org. no. 952587110 Limited company (AS) Tinn Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 9.8m
Operating profit NOK 1.4m
Equity NOK 21.5m
Incorporated 1989
Employees 6
Share capital NOK 653,000

RJUKAN ARBEIDERBLAD AS is registered as a limited company in Tinn, Telemark with organisation number 952587110. The business is classified under publishing of newspapers (NACE 58.120). The company was incorporated in 1989 and has 6 registered employees. Registered share capital is NOK 653,000. The company's stated purpose is: “Utgi avisen Rjukan Arbeiderblad, herunder delta i aktiviteter forbunden med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 9.8m
Operating profit
NOK 1.4m
Equity
NOK 21.5m
Est. value
NOK 21.8m

Financial health · 2024

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

Who owns RJUKAN ARBEIDERBLAD AS?

AMEDIA NORGE AS
RJUKAN ARBEIDERBLAD AS
NOK 9.8m rev. · NOK 1.4m profit

RJUKAN ARBEIDERBLAD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RJUKAN ARBEIDERBLAD AS er morselskap for 74 datterselskaper:

Frequently asked questions about RJUKAN ARBEIDERBLAD AS

Who owns RJUKAN ARBEIDERBLAD AS?

AMEDIA NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of RJUKAN ARBEIDERBLAD AS?

RJUKAN ARBEIDERBLAD AS had revenue of NOK 9.8m in 2024.

Who is the general manager of RJUKAN ARBEIDERBLAD AS?

Egil Stensrud is registered as general manager of RJUKAN ARBEIDERBLAD AS.

Where is RJUKAN ARBEIDERBLAD AS based?

RJUKAN ARBEIDERBLAD 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 15.06.2026.

Report a problem

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