BIZTRAC BETA
Site preparation

TRØNDELAG MONTASJE AS

Org. no. 931953346 Limited company (AS) Melhus Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 261,000
Equity NOK 503,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

TRØNDELAG MONTASJE AS is registered as a limited company in Melhus, Trøndelag with organisation number 931953346. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Montering, demontering, vedlikehold og reparasjon av plasthaller og stålbygg og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 261,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 261,000
Equity
NOK 503,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns TRØNDELAG MONTASJE AS?

BREDE HANSEN BRUBAKK
TRØNDELAG MONTASJE AS
NOK 2.7m rev. · NOK 261,000 profit

TRØNDELAG MONTASJE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRØNDELAG MONTASJE AS

Who owns TRØNDELAG MONTASJE AS?

BREDE HANSEN BRUBAKK is the largest registered owner, with 100.0%.

What is the revenue of TRØNDELAG MONTASJE AS?

TRØNDELAG MONTASJE AS had revenue of NOK 2.7m in 2025.

Who is the general manager of TRØNDELAG MONTASJE AS?

Brede Hansen Brubakk is registered as general manager of TRØNDELAG MONTASJE AS.

Where is TRØNDELAG MONTASJE AS based?

TRØNDELAG MONTASJE AS has its business address in Ler.

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.