biztrac. BETA
COMPANY REGISTER PROFILE
829270102 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer consultancy and computer facilities management activities

MYKA-INVEST AS

Org. no. 829270102 Limited company (AS) Drammen Incorporated 2022 Active
Revenue 2025 NOK 10,000
Operating profit NOK −179,000
Equity NOK −181,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

MYKA-INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 829270102. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og videresalg av profilklær og arbeidsklær. Kjøp og salg.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK −179,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
▼ −74 %
Operating profit
NOK −179,000
▼ −654 %
Equity
NOK −181,000
▼ −3071 %

Financial health · 2025

Liquidity
0.47
Not satisfactory
Current assets ÷ current liabilities
Profitability
-388.4%
Not satisfactory
Return on total assets
Solidity
-246.4%
Weak
Equity as a share of total capital

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

Who owns MYKA-INVEST AS?

MYKA-INVEST AS
NOK 10,000 rev. · NOK −179,000 profit

MYKA-INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MYKA-INVEST AS

Who owns MYKA-INVEST AS?

Herman Kathrud Bekkenes is the largest registered owner, with 50.0%.

What is the revenue of MYKA-INVEST AS?

MYKA-INVEST AS had revenue of NOK 10,000 in 2025.

Where is MYKA-INVEST AS based?

MYKA-INVEST AS has its business address in Solbergelva.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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