BIZTRAC BETA
Other health services

HELSESYKEPLEIEREN AS

Org. no. 925872679 Limited company (AS) Bodø Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 304,000
Operating profit NOK 21,000
Equity NOK 162,000
Incorporated 2020
Share capital NOK 30,000

HELSESYKEPLEIEREN AS is registered as a limited company in Bodø, Nordland with organisation number 925872679. 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 2000 shares. The company's stated purpose is: “Råd, veiledning og undervisning innenfor helsefremmende og forebyggende helsearbeid. Forøvrig det som naturlig faller inn under virksomheten til en helsesykepleier. Salg av produkter som faller naturlig innunder dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 304,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 304,000
Operating profit
NOK 21,000
Equity
NOK 162,000
Est. value
NOK 226,000

Financial health · 2025

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

Who owns HELSESYKEPLEIEREN AS?

KIRSTIN HANSEN
HELSESYKEPLEIEREN AS
NOK 304,000 rev. · NOK 21,000 profit

HELSESYKEPLEIEREN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HELSESYKEPLEIEREN AS own?

HELSESYKEPLEIEREN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HELSESYKEPLEIEREN AS

Who owns HELSESYKEPLEIEREN AS?

KIRSTIN HANSEN is the largest registered owner, with 100.0%.

What is the revenue of HELSESYKEPLEIEREN AS?

HELSESYKEPLEIEREN AS had revenue of NOK 304,000 in 2025.

Where is HELSESYKEPLEIEREN AS based?

HELSESYKEPLEIEREN AS has its business address in Bodø.

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.