BIZTRAC BETA
Other captive investment companies

ARNE C. ELLINGSEN INVEST AS

Org. no. 989177613 Limited company (AS) Sortland Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK 11.9m
Incorporated 2005
Share capital NOK 101,000

Signals

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

ARNE C. ELLINGSEN INVEST AS is registered as a limited company in Sortland, Nordland with organisation number 989177613. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 101,000, divided into 100 shares. The company's stated purpose is: “Erverve og forvalte eierinteresser i andre selskap, samt annen virksomhet som naturlig faller inn under disse områdene.”.

Key figures · 2024

Operating profit
NOK −14,000
Equity
NOK 11.9m
Est. value
NOK 8.4m

Financial health · 2024

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

Who owns ARNE C. ELLINGSEN INVEST AS?

ARNE CHRISTOFFER ELLINGSEN
ARNE C. ELLINGSEN INVEST AS
· NOK −14,000 profit

ARNE C. ELLINGSEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARNE C. ELLINGSEN INVEST AS own?

ARNE C. ELLINGSEN INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ARNE C. ELLINGSEN INVEST AS

Who owns ARNE C. ELLINGSEN INVEST AS?

ARNE CHRISTOFFER ELLINGSEN is the largest registered owner, with 100.0%.

Who is the general manager of ARNE C. ELLINGSEN INVEST AS?

Arne Christoffer Ellingsen is registered as general manager of ARNE C. ELLINGSEN INVEST AS.

Where is ARNE C. ELLINGSEN INVEST AS based?

ARNE C. ELLINGSEN INVEST AS has its business address in Sortland.

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.