BIZTRAC BETA
Other technical consultancy

NESHAUGEN ENGINEERING AS

Org. no. 945833122 Limited company (AS) Bergen Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 521,000
Operating profit NOK 8,000
Equity NOK 183,000
Incorporated 1987
Share capital NOK 100,000

NESHAUGEN ENGINEERING AS is registered as a limited company in Bergen, Vestland with organisation number 945833122. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 500 shares. The company's stated purpose is: “Konsulentvirksomhet, utleie, kjøp og salg av mas- kiner og utstyr og hva dermed står i forbindelse, samt å interessere seg i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 521,000 in revenue and NOK 8,000 in operating profit.

Key figures · 2025

Revenue
NOK 521,000
Operating profit
NOK 8,000
Equity
NOK 183,000
Est. value
NOK 132,000

Financial health · 2025

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

Who owns NESHAUGEN ENGINEERING AS?

SIGURD ROGNSVÅG
NESHAUGEN ENGINEERING AS
NOK 521,000 rev. · NOK 8,000 profit

NESHAUGEN ENGINEERING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NESHAUGEN ENGINEERING AS

Who owns NESHAUGEN ENGINEERING AS?

SIGURD ROGNSVÅG is the largest registered owner, with 65.0%.

What is the revenue of NESHAUGEN ENGINEERING AS?

NESHAUGEN ENGINEERING AS had revenue of NOK 521,000 in 2025.

Who is the general manager of NESHAUGEN ENGINEERING AS?

Sigurd Rognsvåg is registered as general manager of NESHAUGEN ENGINEERING AS.

Where is NESHAUGEN ENGINEERING AS based?

NESHAUGEN ENGINEERING AS has its business address in Nesttun.

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.