BIZTRAC BETA
Freight transport by road

I & G HOLDING AS

Org. no. 915553710 Limited company (AS) Bergen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 289,000
Equity NOK −2.1m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,1 mill kr).

I & G HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 915553710. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Investering i aksjer, samt konsulenttjenester innen off- og onshore virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 289,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 289,000
Equity
NOK −2.1m
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
0.74
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-129.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns I & G HOLDING AS?

No shareholders are registered for I & G HOLDING AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does I & G HOLDING AS own?

I & G HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about I & G HOLDING AS

What is the revenue of I & G HOLDING AS?

I & G HOLDING AS had revenue of NOK 2.7m in 2024.

Who is the general manager of I & G HOLDING AS?

Inge Sigurd Gustafsson is registered as general manager of I & G HOLDING AS.

Where is I & G HOLDING AS based?

I & G HOLDING AS has its business address in Nesttun.

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.