BIZTRAC BETA
Rental and operating of own or leased real estate

MEDIVERSE AS

Org. no. 976144228 Limited company (AS) Stryn Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK −323,000
Operating profit NOK −2.2m
Equity NOK 21.0m
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,2 mill kr).

MEDIVERSE AS is registered as a limited company in Stryn, Vestland with organisation number 976144228. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forvalte egen aktiva i finansmarkedet.”. The most recent filed accounts, for the 2024 financial year, show NOK −323,000 in revenue and NOK −2.2m in operating profit.

Key figures · 2024

Revenue
NOK −323,000
Operating profit
NOK −2.2m
Equity
NOK 21.0m
Est. value
NOK 19.1m

Financial health · 2024

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

Who owns MEDIVERSE AS?

JARAND GJESTLAND
MEDIVERSE AS
NOK −323,000 rev. · NOK −2.2m profit

MEDIVERSE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MEDIVERSE AS own?

MEDIVERSE AS holds stakes in 18 companies:

See the full ownership structure →

Frequently asked questions about MEDIVERSE AS

Who owns MEDIVERSE AS?

JARAND GJESTLAND is the largest registered owner, with 100.0%.

What is the revenue of MEDIVERSE AS?

MEDIVERSE AS had revenue of NOK −323,000 in 2024.

Who is the general manager of MEDIVERSE AS?

Jarand Gjestland is registered as general manager of MEDIVERSE AS.

Where is MEDIVERSE AS based?

MEDIVERSE AS has its business address in Stryn.

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.