BIZTRAC BETA
Other captive investment companies

ELCO INVEST AS

Org. no. 952824724 Limited company (AS) Bærum Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 895,000
Equity NOK 13.0m
Incorporated 1989
Share capital NOK 600,000

ELCO INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 952824724. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1989. Registered share capital is NOK 600,000, divided into 3000 shares. The company's stated purpose is: “Forretningsvirksomhet av enhver art samt del- tagelse i slik virksomhet gjennom aksjebesittelse eller på annen måte, samt forvaltning av egne midler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 895,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 895,000
Equity
NOK 13.0m
Est. value
NOK 9.9m

Financial health · 2025

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

Who owns ELCO INVEST AS?

ELCO INVEST AS
ELCO INVEST AS
NOK 1.1m rev. · NOK 895,000 profit

ELCO INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ELCO INVEST AS own?

ELCO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ELCO INVEST AS

Who owns ELCO INVEST AS?

ELCO INVEST AS is the largest registered owner, with 47.7%.

What is the revenue of ELCO INVEST AS?

ELCO INVEST AS had revenue of NOK 1.1m in 2025.

Who is the general manager of ELCO INVEST AS?

Jens Emil Rynning is registered as general manager of ELCO INVEST AS.

Where is ELCO INVEST AS based?

ELCO INVEST AS has its business address in Snarøya.

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.