BIZTRAC BETA
Civil engineering activities

BRAUTE KONSTRUKSJON AS

Org. no. 977244714 Limited company (AS) Ålesund Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 4.7m
Operating profit NOK −169,000
Equity NOK 1.9m
Incorporated 1996
Share capital NOK 150,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−169k kr).

BRAUTE KONSTRUKSJON AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 977244714. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1996. Registered share capital is NOK 150,000. The company's stated purpose is: “Teknisk bistand, prosjektering, tegning og konstruksjon. Import, kjøp og salg av varer. Utleie av varer og eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.7m in revenue and NOK −169,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.7m
Operating profit
NOK −169,000
Equity
NOK 1.9m
Est. value
NOK 5.8m

Financial health · 2024

Liquidity
1.12
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.9%
Satisfactory
Equity as a share of total capital

Who owns BRAUTE KONSTRUKSJON AS?

TORALF BRAUTE
BRAUTE KONSTRUKSJON AS
NOK 4.7m rev. · NOK −169,000 profit

BRAUTE KONSTRUKSJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRAUTE KONSTRUKSJON AS

Who owns BRAUTE KONSTRUKSJON AS?

TORALF BRAUTE is the largest registered owner, with 100.0%.

What is the revenue of BRAUTE KONSTRUKSJON AS?

BRAUTE KONSTRUKSJON AS had revenue of NOK 4.7m in 2024.

Who is the general manager of BRAUTE KONSTRUKSJON AS?

Toralf Braute is registered as general manager of BRAUTE KONSTRUKSJON AS.

Where is BRAUTE KONSTRUKSJON AS based?

BRAUTE KONSTRUKSJON AS has its business address in Ørskog.

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.