BIZTRAC BETA
Uoppgitt

IGLO INVEST AS

Org. no. 915310737 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 3.8m
Incorporated 2015
Share capital NOK 30,000

Signals

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

IGLO INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 915310737. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Alminnelig investeringsvirksomhet, herunder investeringer i aksjer og fast eiendom, samt annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 3.8m
Est. value
NOK 11.1m

Financial health · 2025

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

Who owns IGLO INVEST AS?

VEGARD EIDSÅ ANDERSEN
IGLO INVEST AS
NOK 0 rev. · NOK −10,000 profit

IGLO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does IGLO INVEST AS own?

IGLO INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about IGLO INVEST AS

Who owns IGLO INVEST AS?

VEGARD EIDSÅ ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of IGLO INVEST AS?

IGLO INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of IGLO INVEST AS?

Vegard Eidså Andersen is registered as general manager of IGLO INVEST AS.

Where is IGLO INVEST AS based?

IGLO INVEST AS has its business address in Oslo.

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.