BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

BERGEN COIN AS

Org. no. 980387836 Limited company (AS) Bergen Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 15.3m
Operating profit NOK 2.7m
Equity NOK 5.7m
Incorporated 1998
Share capital NOK 620,000

BERGEN COIN AS is registered as a limited company in Bergen, Vestland with organisation number 980387836. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 1998. Registered share capital is NOK 620,000, divided into 6200 shares. The company's stated purpose is: “Drift, service, kjøp og salg av betalingsautomater samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.3m in revenue and NOK 2.7m in operating profit.

Key figures · 2024

Revenue
NOK 15.3m
Operating profit
NOK 2.7m
Equity
NOK 5.7m
Est. value
NOK 12.3m

Financial health · 2024

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

Who owns BERGEN COIN AS?

ÅSTVEIT ENTERTAINMENT AS
BERGEN COIN AS
NOK 15.3m rev. · NOK 2.7m profit

BERGEN COIN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BERGEN COIN AS own?

BERGEN COIN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BERGEN COIN AS

Who owns BERGEN COIN AS?

ÅSTVEIT ENTERTAINMENT AS is the largest registered owner, with 80.4%.

What is the revenue of BERGEN COIN AS?

BERGEN COIN AS had revenue of NOK 15.3m in 2024.

Who is the general manager of BERGEN COIN AS?

Kjetil Lien is registered as general manager of BERGEN COIN AS.

Where is BERGEN COIN AS based?

BERGEN COIN 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.