BIZTRAC BETA
Other captive investment companies

HIGH LATITUDE HOLDINGS AS

Org. no. 921585799 Limited company (AS) Asker Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −22,000
Equity NOK 2.8m
Incorporated 2018
Share capital NOK 50,000

Signals

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

HIGH LATITUDE HOLDINGS AS is registered as a limited company in Asker, Akershus with organisation number 921585799. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Investeringer i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 2.8m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns HIGH LATITUDE HOLDINGS AS?

ROBERT JONATHAN SMALLSHIRE
HIGH LATITUDE HOLDINGS AS
NOK 0 rev. · NOK −22,000 profit

HIGH LATITUDE HOLDINGS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HIGH LATITUDE HOLDINGS AS own?

HIGH LATITUDE HOLDINGS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HIGH LATITUDE HOLDINGS AS

Who owns HIGH LATITUDE HOLDINGS AS?

ROBERT JONATHAN SMALLSHIRE is the largest registered owner, with 100.0%.

What is the revenue of HIGH LATITUDE HOLDINGS AS?

HIGH LATITUDE HOLDINGS AS had revenue of NOK 0 in 2024.

Where is HIGH LATITUDE HOLDINGS AS based?

HIGH LATITUDE HOLDINGS AS has its business address in Heggedal.

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.