BIZTRAC BETA
Civil engineering activities

SIV ING ARNE VASLAG AS

Org. no. 948072130 Limited company (AS) Melhus Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 8.0m
Operating profit NOK 776,000
Equity NOK 2.4m
Incorporated 1988
Employees 5
Share capital NOK 100,000

SIV ING ARNE VASLAG AS is registered as a limited company in Melhus, Trøndelag with organisation number 948072130. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1988 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Planlegge, prosjektere og administrere utbyggings- prosjekter samt annen virksomhet som har til- knytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.0m in revenue and NOK 776,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.0m
Operating profit
NOK 776,000
Equity
NOK 2.4m
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns SIV ING ARNE VASLAG AS?

ANDREAS NORDHEIM HOLDING AS
SIV ING ARNE VASLAG AS
NOK 8.0m rev. · NOK 776,000 profit

SIV ING ARNE VASLAG AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIV ING ARNE VASLAG AS

Who owns SIV ING ARNE VASLAG AS?

ANDREAS NORDHEIM HOLDING AS is the largest registered owner, with 45.0%.

What is the revenue of SIV ING ARNE VASLAG AS?

SIV ING ARNE VASLAG AS had revenue of NOK 8.0m in 2024.

Who is the general manager of SIV ING ARNE VASLAG AS?

Andreas Nordheim is registered as general manager of SIV ING ARNE VASLAG AS.

Where is SIV ING ARNE VASLAG AS based?

SIV ING ARNE VASLAG AS has its business address in Melhus.

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.