BIZTRAC BETA
Civil engineering activities

SIGVALD HØYE PROSJEKT AS

Org. no. 983503063 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.4m
Equity NOK 5.5m
Incorporated 2001
Share capital NOK 100,000

SIGVALD HØYE PROSJEKT AS is registered as a limited company in Oslo, Oslo with organisation number 983503063. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2001. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drive administrativ bistand rettet mot prosjektstyring og prosjektledelse hovedsaklig rettet mot bygg- og anleggsbransjen, samt ivestering i verdipapirer, eiendom og i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.4m
Equity
NOK 5.5m
Est. value
NOK 8.1m

Financial health · 2024

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

Who owns SIGVALD HØYE PROSJEKT AS?

SIGVALD HØYE
SIGVALD HØYE PROSJEKT AS
NOK 2.6m rev. · NOK 1.4m profit

SIGVALD HØYE PROSJEKT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGVALD HØYE PROSJEKT AS

Who owns SIGVALD HØYE PROSJEKT AS?

SIGVALD HØYE is the largest registered owner, with 100.0%.

What is the revenue of SIGVALD HØYE PROSJEKT AS?

SIGVALD HØYE PROSJEKT AS had revenue of NOK 2.6m in 2025.

Who is the general manager of SIGVALD HØYE PROSJEKT AS?

Sigvald Høye is registered as general manager of SIGVALD HØYE PROSJEKT AS.

Where is SIGVALD HØYE PROSJEKT AS based?

SIGVALD HØYE PROSJEKT AS has its business address in Oslo.

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.