BIZTRAC BETA
Other education activities

JU-HELSE AS

Org. no. 931416723 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 12,000
Operating profit NOK −21,000
Equity NOK 3,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

JU-HELSE AS is registered as a limited company in Bærum, Akershus with organisation number 931416723. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Opplæring og kurs innen helsesektoren, konsulentvirksomhet, foredrag og forebyggende trening og alt som naturlig står i forbindelse med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 12,000 in revenue and NOK −21,000 in operating profit.

Key figures · 2024

Revenue
NOK 12,000
Operating profit
NOK −21,000
Equity
NOK 3,000
Est. value
NOK 12,000

Financial health · 2024

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

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

Who owns JU-HELSE AS?

GEIR OLA ÅSTORP
JU-HELSE AS
NOK 12,000 rev. · NOK −21,000 profit

JU-HELSE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about JU-HELSE AS

Who owns JU-HELSE AS?

GEIR OLA ÅSTORP is the largest registered owner, with 25.0%.

What is the revenue of JU-HELSE AS?

JU-HELSE AS had revenue of NOK 12,000 in 2024.

Who is the general manager of JU-HELSE AS?

Geir Ola Åstorp is registered as general manager of JU-HELSE AS.

Where is JU-HELSE AS based?

JU-HELSE AS has its business address in Blommenholm.

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.