BIZTRAC BETA
Civil engineering activities

HØYDAL PROSJEKTERING AS

Org. no. 847990392 Limited company (AS) Trondheim Incorporated 1988 Active
Ownership graph ↗
Revenue 2025 NOK 277,000
Operating profit NOK −44,000
Equity NOK 22,000
Incorporated 1988
Share capital NOK 700,000

Signals

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

HØYDAL PROSJEKTERING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 847990392. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 1988. Registered share capital is NOK 700,000, divided into 340 shares. The company's stated purpose is: “Byggteknisk konsulentvirksomhet og utvikling av næringseiendommer, foreta investeringer i aksjer, verdipapirer samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 277,000 in revenue and NOK −44,000 in operating profit.

Key figures · 2025

Revenue
NOK 277,000
Operating profit
NOK −44,000
Equity
NOK 22,000
Est. value
NOK 302,000

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.3%
Weak
Equity as a share of total capital

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

Who owns HØYDAL PROSJEKTERING AS?

JARLE HOLDING AS
HØYDAL PROSJEKTERING AS
NOK 277,000 rev. · NOK −44,000 profit

HØYDAL PROSJEKTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HØYDAL PROSJEKTERING AS

Who owns HØYDAL PROSJEKTERING AS?

JARLE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HØYDAL PROSJEKTERING AS?

HØYDAL PROSJEKTERING AS had revenue of NOK 277,000 in 2025.

Where is HØYDAL PROSJEKTERING AS based?

HØYDAL PROSJEKTERING AS has its business address in Trondheim.

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.