BIZTRAC BETA
General medical practice activities

GARNES MJØS AS

Org. no. 914065429 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 287,000
Operating profit NOK −11,000
Equity NOK 55,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

GARNES MJØS AS is registered as a limited company in Bergen, Vestland with organisation number 914065429. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av legetjenester. Selskapet vil også drive med foto- og videooppdrag og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 287,000 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 287,000
Operating profit
NOK −11,000
Equity
NOK 55,000
Est. value
NOK 266,000

Financial health · 2024

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

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

Who owns GARNES MJØS AS?

HÅKON GARNES MJØS
GARNES MJØS AS
NOK 287,000 rev. · NOK −11,000 profit

GARNES MJØS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GARNES MJØS AS

Who owns GARNES MJØS AS?

HÅKON GARNES MJØS is the largest registered owner, with 100.0%.

What is the revenue of GARNES MJØS AS?

GARNES MJØS AS had revenue of NOK 287,000 in 2024.

Who is the general manager of GARNES MJØS AS?

Håkon Garnes Mjøs is registered as general manager of GARNES MJØS AS.

Where is GARNES MJØS AS based?

GARNES MJØS AS has its business address in Bergen.

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.