BIZTRAC BETA
Site preparation

ÅGE HAVERSTAD AS

Org. no. 989063030 Limited company (AS) Nord-Fron Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 113.0m
Operating profit NOK 4.2m
Equity NOK 17.7m
Incorporated 2005
Employees 55
Share capital NOK 192,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅGE HAVERSTAD AS is registered as a limited company in Nord-Fron, Innlandet with organisation number 989063030. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005 and has 55 registered employees. Registered share capital is NOK 192,000, divided into 192 shares. The company's stated purpose is: “Virksomhet som maskinentreprenør og virksomhet forbundet med dette, samt ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 113.0m in revenue and NOK 4.2m in operating profit.

Key figures · 2025

Revenue
NOK 113.0m
Operating profit
NOK 4.2m
Equity
NOK 17.7m
Est. value
NOK 21.9m

Financial health · 2025

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

Who owns ÅGE HAVERSTAD AS?

OPPKJØP AS
ÅGE HAVERSTAD AS
NOK 113.0m rev. · NOK 4.2m profit

ÅGE HAVERSTAD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ÅGE HAVERSTAD AS er morselskap for 2 datterselskaper:

Frequently asked questions about ÅGE HAVERSTAD AS

Who owns ÅGE HAVERSTAD AS?

OPPKJØP AS is the largest registered owner, with 100.0%.

What is the revenue of ÅGE HAVERSTAD AS?

ÅGE HAVERSTAD AS had revenue of NOK 113.0m in 2025.

Where is ÅGE HAVERSTAD AS based?

ÅGE HAVERSTAD AS has its business address in Vinstra.

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.