BIZTRAC BETA
Other health services

HELSEINKUBATOR AS

Org. no. 920023509 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 0
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-15 Adresseendring registrert 2026-06-15.

HELSEINKUBATOR AS is registered as a limited company in Oslo, Oslo with organisation number 920023509. The business is classified under other health services (NACE 86.993). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Utvikle egne og andres helsetilbud og -prosjekter ved å tilby helsetjenester, veiledning, nettverk, administrasjon og lokaler i samarbeid med offentlige og private aktører og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 0

Financial health · 2024

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

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

Who owns HELSEINKUBATOR AS?

STIAN LARSSEN
HELSEINKUBATOR AS
NOK 0 rev. · NOK 0 profit

HELSEINKUBATOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELSEINKUBATOR AS

Who owns HELSEINKUBATOR AS?

STIAN LARSSEN is the largest registered owner, with 100.0%.

What is the revenue of HELSEINKUBATOR AS?

HELSEINKUBATOR AS had revenue of NOK 0 in 2024.

Who is the general manager of HELSEINKUBATOR AS?

Stian Larssen is registered as general manager of HELSEINKUBATOR AS.

Where is HELSEINKUBATOR AS based?

HELSEINKUBATOR 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.