BIZTRAC BETA
Computer consultancy and computer facilities management activities

NEMETH CONSULTING AS

Org. no. 998291186 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −35,000
Equity NOK 18.4m
Incorporated 2012
Share capital NOK 30,000

Signals

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

NEMETH CONSULTING AS is registered as a limited company in Oslo, Oslo with organisation number 998291186. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet tilknyttet informasjonsteknologi, management for hire, kjøp og salg av verdipapirer, delta som aksjonær i andre foretak samt annet som hermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −35,000
Equity
NOK 18.4m
Est. value
NOK 33.3m

Financial health · 2024

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

Who owns NEMETH CONSULTING AS?

PETTER TVETER-NEMETH
NEMETH CONSULTING AS
· NOK −35,000 profit

NEMETH CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NEMETH CONSULTING AS own?

NEMETH CONSULTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NEMETH CONSULTING AS

Who owns NEMETH CONSULTING AS?

PETTER TVETER-NEMETH is the largest registered owner, with 100.0%.

Who is the general manager of NEMETH CONSULTING AS?

Petter Tveter-Nemeth is registered as general manager of NEMETH CONSULTING AS.

Where is NEMETH CONSULTING AS based?

NEMETH CONSULTING 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.