BIZTRAC BETA
Computer programming activities

LØKEN MEDIA AS

Org. no. 925243965 Limited company (AS) Fredrikstad Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 287,000
Operating profit NOK 17,000
Equity NOK −197,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−197k kr).

LØKEN MEDIA AS is registered as a limited company in Fredrikstad, Østfold with organisation number 925243965. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Totalleverandør av webutvikling, grafisk design og digital markedsføring.”. The most recent filed accounts, for the 2025 financial year, show NOK 287,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2025

Revenue
NOK 287,000
Operating profit
NOK 17,000
Equity
NOK −197,000
Est. value
NOK 129,000

Financial health · 2025

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

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

Who owns LØKEN MEDIA AS?

CARL FREDRIK GRØTVEDT LØKEN
LØKEN MEDIA AS
NOK 287,000 rev. · NOK 17,000 profit

LØKEN MEDIA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LØKEN MEDIA AS

Who owns LØKEN MEDIA AS?

CARL FREDRIK GRØTVEDT LØKEN is the largest registered owner, with 100.0%.

What is the revenue of LØKEN MEDIA AS?

LØKEN MEDIA AS had revenue of NOK 287,000 in 2025.

Who is the general manager of LØKEN MEDIA AS?

Carl Fredrik Grøtvedt Løken is registered as general manager of LØKEN MEDIA AS.

Where is LØKEN MEDIA AS based?

LØKEN MEDIA AS has its business address in Torp.

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.