BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ARNE I BERGLY AS

Org. no. 964386749 Limited company (AS) Eidsvoll Incorporated 1992 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 4.0m
Incorporated 1992
Share capital NOK 615,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

ARNE I BERGLY AS is registered as a limited company in Eidsvoll, Akershus with organisation number 964386749. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 1992. Registered share capital is NOK 615,000, divided into 615 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”.

Key figures · 2024

Operating profit
NOK −21,000
Equity
NOK 4.0m
Est. value
NOK 25.5m

Financial health · 2024

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

Who owns ARNE I BERGLY AS?

TOM ARNE BERGLY
ARNE I BERGLY AS
· NOK −21,000 profit

ARNE I BERGLY AS has 3 registered shareholders:

All shareholders and roles →

Which companies does ARNE I BERGLY AS own?

ARNE I BERGLY AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ARNE I BERGLY AS er morselskap for 1 datterselskap:

Frequently asked questions about ARNE I BERGLY AS

Who owns ARNE I BERGLY AS?

TOM ARNE BERGLY is the largest registered owner, with 87.0%.

Who is the general manager of ARNE I BERGLY AS?

Arne Ingar Bergly is registered as general manager of ARNE I BERGLY AS.

Where is ARNE I BERGLY AS based?

ARNE I BERGLY AS has its business address in Råholt.

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.