BIZTRAC BETA
Other technical consultancy

NATERSTAD CONSULTING AS

Org. no. 990048975 Limited company (AS) Kvinnherad Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 5.9m
Incorporated 2006
Share capital NOK 30,000

Signals

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

NATERSTAD CONSULTING AS is registered as a limited company in Kvinnherad, Vestland with organisation number 990048975. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet rettet mot oljeindustrien samt alt som naturlig står i forbindelse med dette, derunder investeringer og deltagelse i andre selskaper, herunder lånefinansierte investeringer i verdipapirer og valuta.”.

Key figures · 2025

Operating profit
NOK −18,000
Equity
NOK 5.9m
Est. value
NOK 9.5m

Financial health · 2025

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

Who owns NATERSTAD CONSULTING AS?

VIDAR NATERSTAD
NATERSTAD CONSULTING AS
· NOK −18,000 profit

NATERSTAD CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NATERSTAD CONSULTING AS own?

NATERSTAD CONSULTING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NATERSTAD CONSULTING AS

Who owns NATERSTAD CONSULTING AS?

VIDAR NATERSTAD is the largest registered owner, with 100.0%.

Who is the general manager of NATERSTAD CONSULTING AS?

Vidar Naterstad is registered as general manager of NATERSTAD CONSULTING AS.

Where is NATERSTAD CONSULTING AS based?

NATERSTAD CONSULTING AS has its business address in Seimsfoss.

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.