BIZTRAC BETA
Buying and selling of own real estate

ACO HOLDING AS

Org. no. 994632825 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 48,000
Operating profit NOK 40,000
Equity NOK −5.1m
Incorporated 2009
Share capital NOK 100,000

Signals

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

ACO HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 994632825. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investeringer i eiendom, verdipapirer og andre selskaper, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 48,000 in revenue and NOK 40,000 in operating profit.

Key figures · 2024

Revenue
NOK 48,000
Operating profit
NOK 40,000
Equity
NOK −5.1m
Est. value
NOK 308,000

Financial health · 2024

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

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

Who owns ACO HOLDING AS?

ARNE GIERTSEN
ACO HOLDING AS
NOK 48,000 rev. · NOK 40,000 profit

ACO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ACO HOLDING AS own?

ACO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ACO HOLDING AS

Who owns ACO HOLDING AS?

ARNE GIERTSEN is the largest registered owner, with 100.0%.

What is the revenue of ACO HOLDING AS?

ACO HOLDING AS had revenue of NOK 48,000 in 2024.

Where is ACO HOLDING AS based?

ACO HOLDING AS has its business address in Bergen.

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.