BIZTRAC BETA
Residential care activities for persons living with or having a diagnosis of a mental illness and/or substance abuse

BUPA AS

Org. no. 912402223 Limited company (AS) Nesna Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 98.0m
Operating profit NOK 7.7m
Equity NOK 15.2m
Incorporated 2013
Employees 146
Share capital NOK 30,000

BUPA AS is registered as a limited company in Nesna, Nordland with organisation number 912402223. The business is classified under residential care activities for persons living with or having a diagnosis of a mental illness and/or substance abuse (NACE 87.201). The company was incorporated in 2013 and has 146 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Å drive formidling og salg av omsorgstjenester og barnevernstjenester, herunder rådgivning og avlastningstjenester, samt deltakelse i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 98.0m in revenue and NOK 7.7m in operating profit.

Key figures · 2024

Revenue
NOK 98.0m
Operating profit
NOK 7.7m
Equity
NOK 15.2m
Est. value
NOK 46.0m

Financial health · 2024

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

Who owns BUPA AS?

LETS EIENDOM II AS
BUPA AS
NOK 98.0m rev. · NOK 7.7m profit

BUPA AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BUPA AS

Who owns BUPA AS?

LETS EIENDOM II AS is the largest registered owner, with 35.0%.

What is the revenue of BUPA AS?

BUPA AS had revenue of NOK 98.0m in 2024.

Who is the general manager of BUPA AS?

Kjell Arne Grøntjernet is registered as general manager of BUPA AS.

Where is BUPA AS based?

BUPA AS has its business address in Nesna.

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.