BIZTRAC BETA
Repair and maintenance of machinery

EV SERVICE BERGEN AS

Org. no. 826800232 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 8.4m
Operating profit NOK 599,000
Equity NOK 1.2m
Incorporated 2021
Employees 8
Share capital NOK 30,000

EV SERVICE BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 826800232. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2021 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Verksteddrift, herunder kjøp og salg av deler som naturlig tilhører dette. Selskapet kan også engasjere seg i andre foretak med lignende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.4m in revenue and NOK 599,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.4m
Operating profit
NOK 599,000
Equity
NOK 1.2m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns EV SERVICE BERGEN AS?

SKANDIA INVEST AS
EV SERVICE BERGEN AS
NOK 8.4m rev. · NOK 599,000 profit

EV SERVICE BERGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EV SERVICE BERGEN AS

Who owns EV SERVICE BERGEN AS?

SKANDIA INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of EV SERVICE BERGEN AS?

EV SERVICE BERGEN AS had revenue of NOK 8.4m in 2024.

Who is the general manager of EV SERVICE BERGEN AS?

Bjørn-Kåre Monsen is registered as general manager of EV SERVICE BERGEN AS.

Where is EV SERVICE BERGEN AS based?

EV SERVICE BERGEN AS has its business address in Kokstad.

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.