BIZTRAC BETA
Rental and operating of own or leased real estate

BERGENS AUTO AS

Org. no. 990525838 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 19.8m
Operating profit NOK 1.2m
Equity NOK −1.0m
Incorporated 2006
Share capital NOK 250,000

Signals

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

BERGENS AUTO AS is registered as a limited company in Bergen, Vestland with organisation number 990525838. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2006. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Erverv og drift av fast eiendom og det som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 19.8m
Operating profit
NOK 1.2m
Equity
NOK −1.0m
Est. value
NOK 9.4m

Financial health · 2024

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

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

Who owns BERGENS AUTO AS?

CHRISTER WERNER HALVORSEN
BERGENS AUTO AS
NOK 19.8m rev. · NOK 1.2m profit

BERGENS AUTO AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGENS AUTO AS

Who owns BERGENS AUTO AS?

CHRISTER WERNER HALVORSEN is the largest registered owner, with 32.4%.

What is the revenue of BERGENS AUTO AS?

BERGENS AUTO AS had revenue of NOK 19.8m in 2024.

Who is the general manager of BERGENS AUTO AS?

Tom Erik Riisnes Nesse is registered as general manager of BERGENS AUTO AS.

Where is BERGENS AUTO AS based?

BERGENS AUTO 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.