BIZTRAC BETA
Rental and operating of own or leased real estate

ST JOSEPH HELSEHUS AS

Org. no. 868454652 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 7.0m
Operating profit NOK 4.1m
Equity NOK 8.7m
Incorporated 1993
Share capital NOK 1.2m

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-19 Adresseendring registrert 2026-06-19.

ST JOSEPH HELSEHUS AS is registered as a limited company in Oslo, Oslo with organisation number 868454652. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 1.2m, divided into 1240 shares. The company's stated purpose is: “Erverv og drift av fast eiendom, og alt som står i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.0m in revenue and NOK 4.1m in operating profit.

Key figures · 2024

Revenue
NOK 7.0m
Operating profit
NOK 4.1m
Equity
NOK 8.7m
Est. value
NOK 15.4m

Financial health · 2024

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
60.5%
Very good
Equity as a share of total capital

Who owns ST JOSEPH HELSEHUS AS?

NIKI AS
ST JOSEPH HELSEHUS AS
NOK 7.0m rev. · NOK 4.1m profit

ST JOSEPH HELSEHUS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ST JOSEPH HELSEHUS AS

Who owns ST JOSEPH HELSEHUS AS?

NIKI AS is the largest registered owner, with 100.0%.

What is the revenue of ST JOSEPH HELSEHUS AS?

ST JOSEPH HELSEHUS AS had revenue of NOK 7.0m in 2024.

Where is ST JOSEPH HELSEHUS AS based?

ST JOSEPH HELSEHUS AS has its business address in Oslo.

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.