BIZTRAC BETA
Computer consultancy and computer facilities management activities

ARCTIC MEDIA GROUP AS

Org. no. 932739453 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 13.7m
Operating profit NOK 6.5m
Equity NOK 5.2m
Incorporated 2023
Employees 7
Share capital NOK 30,000

ARCTIC MEDIA GROUP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932739453. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.7m in revenue and NOK 6.5m in operating profit.

Key figures · 2024

Revenue
NOK 13.7m
Operating profit
NOK 6.5m
Equity
NOK 5.2m
Est. value
NOK 25.2m

Financial health · 2024

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

Who owns ARCTIC MEDIA GROUP AS?

HOVEDKVARTER AS
ARCTIC MEDIA GROUP AS
NOK 13.7m rev. · NOK 6.5m profit

ARCTIC MEDIA GROUP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARCTIC MEDIA GROUP AS

Who owns ARCTIC MEDIA GROUP AS?

HOVEDKVARTER AS is the largest registered owner, with 50.0%.

What is the revenue of ARCTIC MEDIA GROUP AS?

ARCTIC MEDIA GROUP AS had revenue of NOK 13.7m in 2024.

Who is the general manager of ARCTIC MEDIA GROUP AS?

Trond Adrian Frost is registered as general manager of ARCTIC MEDIA GROUP AS.

Where is ARCTIC MEDIA GROUP AS based?

ARCTIC MEDIA GROUP AS has its business address in Skjetten.

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.