BIZTRAC BETA
Business and other management consultancy activities

NESTE STEG AS

Org. no. 987478276 Limited company (AS) Bærum Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 442,000
Operating profit NOK −99,000
Equity NOK 11.2m
Incorporated 2004
Share capital NOK 100,000

Signals

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

NESTE STEG AS is registered as a limited company in Bærum, Akershus with organisation number 987478276. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2004. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forretningsmessig tjenesteyting samt direkte eller indirekte deltakelse i selskaper med lignende eller annet formål herunder finansielle investeringer.”. The most recent filed accounts, for the 2024 financial year, show NOK 442,000 in revenue and NOK −99,000 in operating profit.

Key figures · 2024

Revenue
NOK 442,000
Operating profit
NOK −99,000
Equity
NOK 11.2m
Est. value
NOK 10.3m

Financial health · 2024

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

Who owns NESTE STEG AS?

LISE VINDE ROTH
NESTE STEG AS
NOK 442,000 rev. · NOK −99,000 profit

NESTE STEG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NESTE STEG AS own?

NESTE STEG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NESTE STEG AS

Who owns NESTE STEG AS?

LISE VINDE ROTH is the largest registered owner, with 100.0%.

What is the revenue of NESTE STEG AS?

NESTE STEG AS had revenue of NOK 442,000 in 2024.

Where is NESTE STEG AS based?

NESTE STEG AS has its business address in Lysaker.

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.