BIZTRAC BETA
Retail sale of information and communication equipment

RADIO- OG TV-TEKNIKK AS

Org. no. 989289780 Limited company (AS) Arendal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 13.7m
Operating profit NOK 515,000
Equity NOK 3.8m
Incorporated 2005
Employees 10
Share capital NOK 400,000

RADIO- OG TV-TEKNIKK AS is registered as a limited company in Arendal, Agder with organisation number 989289780. The business is classified under retail sale of information and communication equipment (NACE 47.400). The company was incorporated in 2005 and has 10 registered employees. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Handel og annen økonomisk virksomhet. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.7m in revenue and NOK 515,000 in operating profit.

Key figures · 2025

Revenue
NOK 13.7m
Operating profit
NOK 515,000
Equity
NOK 3.8m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns RADIO- OG TV-TEKNIKK AS?

TOM ARILD SELL
RADIO- OG TV-TEKNIKK AS
NOK 13.7m rev. · NOK 515,000 profit

RADIO- OG TV-TEKNIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RADIO- OG TV-TEKNIKK AS

Who owns RADIO- OG TV-TEKNIKK AS?

TOM ARILD SELL is the largest registered owner, with 50.0%.

What is the revenue of RADIO- OG TV-TEKNIKK AS?

RADIO- OG TV-TEKNIKK AS had revenue of NOK 13.7m in 2025.

Who is the general manager of RADIO- OG TV-TEKNIKK AS?

Tom Arild Sell is registered as general manager of RADIO- OG TV-TEKNIKK AS.

Where is RADIO- OG TV-TEKNIKK AS based?

RADIO- OG TV-TEKNIKK AS has its business address in Arendal.

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.