BIZTRAC BETA
COMPANY REGISTER PROFILE
922423954 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Scheduled long distance passenger transport in coastal waters

NANOQ HOLDINGS II AS

Org. no. 922423954 Limited company (AS) Stavanger Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −85,000
Equity NOK 3.1bn
Incorporated 2019
Share capital NOK 2.1m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−85k kr).
  • Nylig endring 2026-05-21 Aksjekapital registrert 2026-05-21.

NANOQ HOLDINGS II AS is registered as a limited company in Stavanger, Rogaland with organisation number 922423954. The business is classified under scheduled long distance passenger transport in coastal waters (NACE 50.102). The company was incorporated in 2019. Registered share capital is NOK 2.1m, divided into 1000 shares. The company's stated purpose is: “Utvikling og investering i andre selskaper og alt som står i forbindelse hermed, inkludert eie aksjer i andre selskaper.”.

Former names: ATHOMSTART INVEST 373 AS

Key figures · 2025

Operating profit
NOK −85,000
▼ −181 %
Equity
NOK 3.1bn
▲ +16 %
Est. value
NOK 3.3bn

Financial health · 2025

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns NANOQ HOLDINGS II AS?

NANOQ HOLDINGS II AS
· NOK −85,000 profit

NANOQ HOLDINGS II AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NANOQ HOLDINGS II AS own?

NANOQ HOLDINGS II AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NANOQ HOLDINGS II AS

Who owns NANOQ HOLDINGS II AS?

NANOQ NEWCO AS is the largest registered owner, with 100.0%.

Where is NANOQ HOLDINGS II AS based?

NANOQ HOLDINGS II AS has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.