BIZTRAC BETA
Rental and operating of own or leased real estate

NETEKS NORGE AS

Org. no. 960564146 Limited company (AS) Oslo Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK −3.3m
Equity NOK 4.2m
Incorporated 1991
Employees 7
Share capital NOK 500,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3,3 mill kr).

NETEKS NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 960564146. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1991 and has 7 registered employees. Registered share capital is NOK 500,000, divided into 50 shares. The company's stated purpose is: “Import, agenturvirksomhet, handel og alt som har forbindelse med dette, samt oppføring, utleie og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK −3.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK −3.3m
Equity
NOK 4.2m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns NETEKS NORGE AS?

AINA HAGEN STOMPERUD
NETEKS NORGE AS
NOK 1.2m rev. · NOK −3.3m profit

NETEKS NORGE AS has 5 registered shareholders:

All shareholders and roles →

Which companies does NETEKS NORGE AS own?

NETEKS NORGE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NETEKS NORGE AS

Who owns NETEKS NORGE AS?

AINA HAGEN STOMPERUD is the largest registered owner, with 50.0%.

What is the revenue of NETEKS NORGE AS?

NETEKS NORGE AS had revenue of NOK 1.2m in 2024.

Where is NETEKS NORGE AS based?

NETEKS NORGE 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.