BIZTRAC BETA
Specialised construction activities in civil engineering

PER STÅLE AARSTAD INVEST AS

Org. no. 915056466 Limited company (AS) Melhus Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −30,000
Equity NOK 9.4m
Incorporated 2014
Share capital NOK 32,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).

PER STÅLE AARSTAD INVEST AS is registered as a limited company in Melhus, Trøndelag with organisation number 915056466. The business is classified under specialised construction activities in civil engineering (NACE 43.500). The company was incorporated in 2014. Registered share capital is NOK 32,000, divided into 80 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer, samt hva som naturlig står i forbindelse med dette”.

Key figures · 2025

Operating profit
NOK −30,000
Equity
NOK 9.4m
Est. value
NOK 20.2m

Financial health · 2025

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

Who owns PER STÅLE AARSTAD INVEST AS?

PER STÅLE STAVRUM AARSTAD
PER STÅLE AARSTAD INVEST AS
· NOK −30,000 profit

PER STÅLE AARSTAD INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER STÅLE AARSTAD INVEST AS own?

PER STÅLE AARSTAD INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about PER STÅLE AARSTAD INVEST AS

Who owns PER STÅLE AARSTAD INVEST AS?

PER STÅLE STAVRUM AARSTAD is the largest registered owner, with 100.0%.

Who is the general manager of PER STÅLE AARSTAD INVEST AS?

Per Ståle Stavrum Aarstad is registered as general manager of PER STÅLE AARSTAD INVEST AS.

Where is PER STÅLE AARSTAD INVEST AS based?

PER STÅLE AARSTAD INVEST 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.