BIZTRAC BETA
COMPANY REGISTER PROFILE
998475929 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Quarrying of ornamental stone, limestone, gypsum, slate and other stone

BRH ANLEGG AS

Org. no. 998475929 Limited company (AS) Hitra Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 7.0m
Operating profit NOK 327,000
Equity NOK 3.2m
Incorporated 2012
Employees 5
Share capital NOK 150,000

BRH ANLEGG AS is registered as a limited company in Hitra, Trøndelag with organisation number 998475929. The business is classified under quarrying of ornamental stone, limestone, gypsum, slate and other stone (NACE 08.110). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Pukkverk- og anleggsvirksomhet, samt tilhørende aktiviteter som naturlig faller sammen med dette. Selskapet kan delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.0m in revenue and NOK 327,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.0m
Operating profit
NOK 327,000
Equity
NOK 3.2m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns BRH ANLEGG AS?

BRH ANLEGG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRH ANLEGG AS

Who owns BRH ANLEGG AS?

STEINAR CEDOLF HEGGELUND HANSSEN is the largest registered owner, with 33.3%.

What is the revenue of BRH ANLEGG AS?

BRH ANLEGG AS had revenue of NOK 7.0m in 2025.

Who is the general manager of BRH ANLEGG AS?

Aksel Einar Hanssen is registered as general manager of BRH ANLEGG AS.

Where is BRH ANLEGG AS based?

BRH ANLEGG AS has its business address in Sandstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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