BIZTRAC BETA
Traditional, complementary and alternative medicine activities

MIGHTYBEARS HOLDING AS

Org. no. 918578072 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 4.7m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

MIGHTYBEARS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 918578072. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Helserelatert virksomhet, kiropraktisk behandling, utredning og kurs, samt det som naturlig står i forbindelse med dette. Selskapet skal i tillegg kunne eie aksjer i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −21,000
Equity
NOK 4.7m
Est. value
NOK 16.3m

Financial health · 2024

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

Who owns MIGHTYBEARS HOLDING AS?

BJØRNAR KNUTSEN
MIGHTYBEARS HOLDING AS
· NOK −21,000 profit

MIGHTYBEARS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MIGHTYBEARS HOLDING AS own?

MIGHTYBEARS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MIGHTYBEARS HOLDING AS

Who owns MIGHTYBEARS HOLDING AS?

BJØRNAR KNUTSEN is the largest registered owner, with 100.0%.

Who is the general manager of MIGHTYBEARS HOLDING AS?

Bjørnar Knutsen is registered as general manager of MIGHTYBEARS HOLDING AS.

Where is MIGHTYBEARS HOLDING AS based?

MIGHTYBEARS HOLDING AS has its business address in Kokstad.

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.