BIZTRAC BETA
Computer programming activities

LONGSHIRE AS

Org. no. 918632050 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 2.9m
Incorporated 2017
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

LONGSHIRE AS is registered as a limited company in Bærum, Akershus with organisation number 918632050. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 200,000, divided into 200000 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer utstedt av utenlandske og norske selskaper, samt alt som hører naturlig dertil, herunder deltagelse i andre selskaper, samt å fremme slik virksomhet gjennom analysevirksomhet, konsulentvirksomhet, rådgivning, forfattervirksomhet, undervisning og foredragsvirksomhet, samt å bidra til kunnskapsbygging i samfunnet gjennom gaver og bistand til prosjekter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 2.9m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns LONGSHIRE AS?

MOAT HOLDING AS
LONGSHIRE AS
NOK 0 rev. · NOK −17,000 profit

LONGSHIRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LONGSHIRE AS

Who owns LONGSHIRE AS?

MOAT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LONGSHIRE AS?

LONGSHIRE AS had revenue of NOK 0 in 2025.

Where is LONGSHIRE AS based?

LONGSHIRE AS has its business address in Haslum.

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.