BIZTRAC BETA
Support services to forestry

HEGGERUDSTAD MASKIN AS

Org. no. 920286364 Limited company (AS) Ringerike Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 13.7m
Operating profit NOK 720,000
Equity NOK 3.9m
Incorporated 2018
Employees 12
Share capital NOK 100,000

HEGGERUDSTAD MASKIN AS is registered as a limited company in Ringerike, Buskerud with organisation number 920286364. The business is classified under support services to forestry (NACE 02.400). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Maskinentreprenærvirksomhet med hovedtyngde i skogrelatert næring samt annet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 13.7m in revenue and NOK 720,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.7m
Operating profit
NOK 720,000
Equity
NOK 3.9m
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns HEGGERUDSTAD MASKIN AS?

HEGGERUDSTAD AS
HEGGERUDSTAD MASKIN AS
NOK 13.7m rev. · NOK 720,000 profit

HEGGERUDSTAD MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEGGERUDSTAD MASKIN AS

Who owns HEGGERUDSTAD MASKIN AS?

HEGGERUDSTAD AS is the largest registered owner, with 100.0%.

What is the revenue of HEGGERUDSTAD MASKIN AS?

HEGGERUDSTAD MASKIN AS had revenue of NOK 13.7m in 2024.

Who is the general manager of HEGGERUDSTAD MASKIN AS?

Harry Heggerudstad is registered as general manager of HEGGERUDSTAD MASKIN AS.

Where is HEGGERUDSTAD MASKIN AS based?

HEGGERUDSTAD MASKIN AS has its business address in Nes I Ådal.

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.