BIZTRAC BETA
Research and experimental development on natural sciences and engineering

NETOPP EIENDOM AS

Org. no. 996793206 Limited company (AS) Bamble Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 460,000
Operating profit NOK 297,000
Equity NOK 531,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NETOPP EIENDOM AS is registered as a limited company in Bamble, Telemark with organisation number 996793206. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Deltagelse i andre virksomheter, investeringer i fast eiendom, samt annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 460,000 in revenue and NOK 297,000 in operating profit.

Key figures · 2024

Revenue
NOK 460,000
Operating profit
NOK 297,000
Equity
NOK 531,000
Est. value
NOK 723,000

Financial health · 2024

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

Who owns NETOPP EIENDOM AS?

NETOPP HOLDING AS
NETOPP EIENDOM AS
NOK 460,000 rev. · NOK 297,000 profit

NETOPP EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NETOPP EIENDOM AS

Who owns NETOPP EIENDOM AS?

NETOPP HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NETOPP EIENDOM AS?

NETOPP EIENDOM AS had revenue of NOK 460,000 in 2024.

Where is NETOPP EIENDOM AS based?

NETOPP EIENDOM AS has its business address in Stathelle.

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.