BIZTRAC BETA
Other health services

BERGEN HELSEPERSONELL AS

Org. no. 925894354 Limited company (AS) Alver Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 60,000
Equity NOK 15,000
Incorporated 2020
Share capital NOK 30,000

BERGEN HELSEPERSONELL AS is registered as a limited company in Alver, Vestland with organisation number 925894354. The business is classified under other health services (NACE 86.993). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Helsefaglig undervisning . Utførelse av helsetjenester «on og offshore» samt sykepleiertjenester til privat og offentlig sektor.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 60,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 60,000
Equity
NOK 15,000
Est. value
NOK 285,000

Financial health · 2024

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.6%
Weak
Equity as a share of total capital

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

Who owns BERGEN HELSEPERSONELL AS?

FRODE BØE
BERGEN HELSEPERSONELL AS
NOK 1.2m rev. · NOK 60,000 profit

BERGEN HELSEPERSONELL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGEN HELSEPERSONELL AS

Who owns BERGEN HELSEPERSONELL AS?

FRODE BØE is the largest registered owner, with 100.0%.

What is the revenue of BERGEN HELSEPERSONELL AS?

BERGEN HELSEPERSONELL AS had revenue of NOK 1.2m in 2024.

Who is the general manager of BERGEN HELSEPERSONELL AS?

Frode Bøe is registered as general manager of BERGEN HELSEPERSONELL AS.

Where is BERGEN HELSEPERSONELL AS based?

BERGEN HELSEPERSONELL AS has its business address in Rossland.

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.