BIZTRAC BETA
Civil engineering activities

BYGGTEKNISK RÅDGIVNING AS

Org. no. 891787812 Limited company (AS) Trondheim Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 353,000
Equity NOK 1.6m
Incorporated 2007
Share capital NOK 100,000

BYGGTEKNISK RÅDGIVNING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 891787812. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive byggteknisk rådgivning og det som faller naturlig inn under dette, herunder deltakelse i andre foretak med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 353,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 353,000
Equity
NOK 1.6m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns BYGGTEKNISK RÅDGIVNING AS?

ASBJØRN FLASNES
BYGGTEKNISK RÅDGIVNING AS
NOK 1.9m rev. · NOK 353,000 profit

BYGGTEKNISK RÅDGIVNING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BYGGTEKNISK RÅDGIVNING AS own?

BYGGTEKNISK RÅDGIVNING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BYGGTEKNISK RÅDGIVNING AS

Who owns BYGGTEKNISK RÅDGIVNING AS?

ASBJØRN FLASNES is the largest registered owner, with 60.0%.

What is the revenue of BYGGTEKNISK RÅDGIVNING AS?

BYGGTEKNISK RÅDGIVNING AS had revenue of NOK 1.9m in 2025.

Where is BYGGTEKNISK RÅDGIVNING AS based?

BYGGTEKNISK RÅDGIVNING AS has its business address in Trondheim.

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.