BIZTRAC BETA
Preventive health care activities

EPIVITY HEALTH AS

Org. no. 932136759 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −176,000
Equity NOK 2.1m
Incorporated 2023
Share capital NOK 1.3m

Signals

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

EPIVITY HEALTH AS is registered as a limited company in Oslo, Oslo with organisation number 932136759. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2023. Registered share capital is NOK 1.3m, divided into 1251892 shares. The company's stated purpose is: “Skal investere i virksomheter som arbeider med behandlinger, gi innsikt i, og som har som mål å bremse ned eller reversere biologisk aldring og leve et bedre, lengre og friskere liv. Selskapet skal også investere i forskning innen området epigenetikk og virkemidler som bidrar til å bremse og reversere biologisk aldring.”.

Key figures · 2024

Operating profit
NOK −176,000
Equity
NOK 2.1m
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns EPIVITY HEALTH AS?

BIBADUM AS
EPIVITY HEALTH AS
· NOK −176,000 profit

EPIVITY HEALTH AS has 9 registered shareholders:

All shareholders and roles →

Which companies does EPIVITY HEALTH AS own?

EPIVITY HEALTH AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EPIVITY HEALTH AS

Who owns EPIVITY HEALTH AS?

BIBADUM AS is the largest registered owner, with 81.8%.

Who is the general manager of EPIVITY HEALTH AS?

Morten Sandberg is registered as general manager of EPIVITY HEALTH AS.

Where is EPIVITY HEALTH AS based?

EPIVITY HEALTH AS has its business address in Oslo.

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.