BIZTRAC BETA
Motion picture, video and television programme production activities

MYKE BLIKK AS

Org. no. 930578525 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 480,000
Operating profit NOK 368,000
Equity NOK 300,000
Incorporated 2022
Share capital NOK 30,000

MYKE BLIKK AS is registered as a limited company in Asker, Akershus with organisation number 930578525. The business is classified under motion picture, video and television programme production activities (NACE 59.110). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen filmproduksjon - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 480,000 in revenue and NOK 368,000 in operating profit.

Key figures · 2024

Revenue
NOK 480,000
Operating profit
NOK 368,000
Equity
NOK 300,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns MYKE BLIKK AS?

FRANCISKA SEIFERT ELIASSEN
MYKE BLIKK AS
NOK 480,000 rev. · NOK 368,000 profit

MYKE BLIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MYKE BLIKK AS

Who owns MYKE BLIKK AS?

FRANCISKA SEIFERT ELIASSEN is the largest registered owner, with 100.0%.

What is the revenue of MYKE BLIKK AS?

MYKE BLIKK AS had revenue of NOK 480,000 in 2024.

Who is the general manager of MYKE BLIKK AS?

Franciska Seifert Eliassen is registered as general manager of MYKE BLIKK AS.

Where is MYKE BLIKK AS based?

MYKE BLIKK AS has its business address in Asker.

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.