BIZTRAC BETA
Business and other management consultancy activities

INDIGO HOLDING AS

Org. no. 914280230 Limited company (AS) Sarpsborg Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 67,000
Operating profit NOK −1.6m
Equity NOK 42.9m
Incorporated 2014
Share capital NOK 70,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).

INDIGO HOLDING AS is registered as a limited company in Sarpsborg, Østfold with organisation number 914280230. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 70,000, divided into 1000 shares. The company's stated purpose is: “Konsulenttjenester, eie aksjer og andeler i andre selskaper, samt virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 67,000 in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 67,000
Operating profit
NOK −1.6m
Equity
NOK 42.9m
Est. value
NOK 21.0m

Financial health · 2024

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

Who owns INDIGO HOLDING AS?

JULIAN BERGER
INDIGO HOLDING AS
NOK 67,000 rev. · NOK −1.6m profit

INDIGO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does INDIGO HOLDING AS own?

INDIGO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about INDIGO HOLDING AS

Who owns INDIGO HOLDING AS?

JULIAN BERGER is the largest registered owner, with 100.0%.

What is the revenue of INDIGO HOLDING AS?

INDIGO HOLDING AS had revenue of NOK 67,000 in 2024.

Where is INDIGO HOLDING AS based?

INDIGO HOLDING AS has its business address in Skjeberg.

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.