BIZTRAC BETA
Retail sale of automotive fuel

BERGSTADEN SERVICESENTER AS

Org. no. 922707170 Limited company (AS) Røros Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 274,000
Equity NOK 1.9m
Incorporated 2019
Employees 9
Share capital NOK 30,000

BERGSTADEN SERVICESENTER AS is registered as a limited company in Røros, Trøndelag with organisation number 922707170. The business is classified under retail sale of automotive fuel (NACE 47.300). The company was incorporated in 2019 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å selge mat og bensin/diesel, samt det som måtte stå i den forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 274,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 274,000
Equity
NOK 1.9m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns BERGSTADEN SERVICESENTER AS?

ELI ENGAN LIEN
BERGSTADEN SERVICESENTER AS
NOK 7.1m rev. · NOK 274,000 profit

BERGSTADEN SERVICESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BERGSTADEN SERVICESENTER AS

Who owns BERGSTADEN SERVICESENTER AS?

ELI ENGAN LIEN is the largest registered owner, with 100.0%.

What is the revenue of BERGSTADEN SERVICESENTER AS?

BERGSTADEN SERVICESENTER AS had revenue of NOK 7.1m in 2024.

Who is the general manager of BERGSTADEN SERVICESENTER AS?

Eli Engan Lien is registered as general manager of BERGSTADEN SERVICESENTER AS.

Where is BERGSTADEN SERVICESENTER AS based?

BERGSTADEN SERVICESENTER AS has its business address in Røros.

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.