biztrac. BETA
COMPANY REGISTER PROFILE
912274195 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of motor vehicles

BROEN VERKSTED AS

Org. no. 912274195 Limited company (AS) Røros Incorporated 2013 Active
Revenue 2025 NOK 629,000
Operating profit NOK 72,000
Equity NOK 269,000
Incorporated 2013
Share capital NOK 55,000

BROEN VERKSTED AS is registered as a limited company in Røros, Trøndelag with organisation number 912274195. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2013. Registered share capital is NOK 55,000, divided into 1000 shares. The company's stated purpose is: “Rep. og restaurering av gamle og nye kjøretøyer. Sensor og konsulentvirksomhet. Rep.og restaurering av motorer, gamle og nye redskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 629,000 in revenue and NOK 72,000 in operating profit.

Key figures · 2025

Revenue
NOK 629,000
▲ +41 %
Operating profit
NOK 72,000
▲ +56 %
Equity
NOK 269,000
▲ +26 %
Est. value
NOK 414,000

Financial health · 2025

Liquidity
2.18
Very good
Current assets ÷ current liabilities
Profitability
19.7%
Very good
Return on total assets
Solidity
64.6%
Very good
Equity as a share of total capital

Who owns BROEN VERKSTED AS?

BROEN VERKSTED AS
NOK 629,000 rev. · NOK 72,000 profit

BROEN VERKSTED AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROEN VERKSTED AS

Who owns BROEN VERKSTED AS?

Bjørn Broen is the largest registered owner, with 100.0%.

What is the revenue of BROEN VERKSTED AS?

BROEN VERKSTED AS had revenue of NOK 629,000 in 2025.

Who is the general manager of BROEN VERKSTED AS?

Bjørn Broen is registered as general manager of BROEN VERKSTED AS.

Where is BROEN VERKSTED AS based?

BROEN VERKSTED 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.