BIZTRAC BETA
Preventive health care activities

URKRAFT HEALER RIITTA HELEN JOHANSEN AS

Org. no. 927162512 Limited company (AS) Sør-Varanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 333,000
Operating profit NOK 9,000
Equity NOK 32,000
Incorporated 2021
Share capital NOK 30,000

URKRAFT HEALER RIITTA HELEN JOHANSEN AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 927162512. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Veilede og hjelpe andre til en positiv utvikling.”. The most recent filed accounts, for the 2025 financial year, show NOK 333,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 333,000
Operating profit
NOK 9,000
Equity
NOK 32,000
Est. value
NOK 59,000

Financial health · 2024

Liquidity
1.52
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.2%
Weak
Equity as a share of total capital

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

Who owns URKRAFT HEALER RIITTA HELEN JOHANSEN AS?

RIITTA HELEN JOHANSEN
URKRAFT HEALER RIITTA HELEN JOHANSEN AS
NOK 333,000 rev. · NOK 9,000 profit

URKRAFT HEALER RIITTA HELEN JOHANSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about URKRAFT HEALER RIITTA HELEN JOHANSEN AS

Who owns URKRAFT HEALER RIITTA HELEN JOHANSEN AS?

RIITTA HELEN JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of URKRAFT HEALER RIITTA HELEN JOHANSEN AS?

URKRAFT HEALER RIITTA HELEN JOHANSEN AS had revenue of NOK 333,000 in 2025.

Where is URKRAFT HEALER RIITTA HELEN JOHANSEN AS based?

URKRAFT HEALER RIITTA HELEN JOHANSEN AS has its business address in Hesseng.

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.