BIZTRAC BETA
Building of civilian ships and floating structures

NEGAS INVEST AS

Org. no. 992053399 Limited company (AS) Vestnes Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −29,000
Equity NOK 10.9m
Incorporated 2007
Share capital NOK 180,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−29k kr).

NEGAS INVEST AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 992053399. The business is classified under building of civilian ships and floating structures (NACE 30.110). The company was incorporated in 2007. Registered share capital is NOK 180,000, divided into 180 shares. The company's stated purpose is: “Investering i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 10.9m
Est. value
NOK 11.6m

Financial health · 2024

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

Who owns NEGAS INVEST AS?

STIG SAGEN
NEGAS INVEST AS
NOK 0 rev. · NOK −29,000 profit

NEGAS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NEGAS INVEST AS own?

NEGAS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NEGAS INVEST AS

Who owns NEGAS INVEST AS?

STIG SAGEN is the largest registered owner, with 100.0%.

What is the revenue of NEGAS INVEST AS?

NEGAS INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of NEGAS INVEST AS?

Stig Sagen is registered as general manager of NEGAS INVEST AS.

Where is NEGAS INVEST AS based?

NEGAS INVEST AS has its business address in Tomrefjord.

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.