BIZTRAC BETA
Silviculture and other forestry activities

HAKKESPETT TREPLEIE AS

Org. no. 832092592 Limited company (AS) Nittedal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 293,000
Operating profit NOK 8,000
Equity NOK 36,000
Incorporated 2023
Share capital NOK 30,000

HAKKESPETT TREPLEIE AS is registered as a limited company in Nittedal, Akershus with organisation number 832092592. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Arboristtjenester; trefelling, trevurdering, beskjæring, beplantning og rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 293,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 293,000
Operating profit
NOK 8,000
Equity
NOK 36,000
Est. value
NOK 50,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HAKKESPETT TREPLEIE AS?

RAGNAR SCHØNHEYDER
HAKKESPETT TREPLEIE AS
NOK 293,000 rev. · NOK 8,000 profit

HAKKESPETT TREPLEIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAKKESPETT TREPLEIE AS

Who owns HAKKESPETT TREPLEIE AS?

RAGNAR SCHØNHEYDER is the largest registered owner, with 100.0%.

What is the revenue of HAKKESPETT TREPLEIE AS?

HAKKESPETT TREPLEIE AS had revenue of NOK 293,000 in 2025.

Who is the general manager of HAKKESPETT TREPLEIE AS?

Ragnar Schønheyder is registered as general manager of HAKKESPETT TREPLEIE AS.

Where is HAKKESPETT TREPLEIE AS based?

HAKKESPETT TREPLEIE AS has its business address in Hakadal.

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.