BIZTRAC BETA
Rental and operating of own or leased real estate

NETOR HOLDING AS

Org. no. 916454325 Limited company (AS) Oppdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 31,000
Operating profit NOK −91,000
Equity NOK 1.9m
Incorporated 2015
Share capital NOK 30,000

Signals

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

NETOR HOLDING AS is registered as a limited company in Oppdal, Trøndelag with organisation number 916454325. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av aksjer, prosjektledelse, konsulenttjenester, drift og eie av fast eiendom, samt beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 31,000 in revenue and NOK −91,000 in operating profit.

Key figures · 2025

Revenue
NOK 31,000
Operating profit
NOK −91,000
Equity
NOK 1.9m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns NETOR HOLDING AS?

MORTEN ROTEN
NETOR HOLDING AS
NOK 31,000 rev. · NOK −91,000 profit

NETOR HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NETOR HOLDING AS own?

NETOR HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NETOR HOLDING AS

Who owns NETOR HOLDING AS?

MORTEN ROTEN is the largest registered owner, with 100.0%.

What is the revenue of NETOR HOLDING AS?

NETOR HOLDING AS had revenue of NOK 31,000 in 2025.

Where is NETOR HOLDING AS based?

NETOR HOLDING AS has its business address in Oppdal.

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.