BIZTRAC BETA
COMPANY REGISTER PROFILE
919256915 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

NEA 1 AS

Org. no. 919256915 Limited company (AS) Bærum Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 5.6m
Incorporated 2017
Share capital NOK 111,000

Signals

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

NEA 1 AS is registered as a limited company in Bærum, Akershus with organisation number 919256915. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 111,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp og salg av aksjer og deltagelse i eiendomsprosjekter.”.

Key figures · 2025

Operating profit
NOK −18,000
Equity
NOK 5.6m
Est. value
NOK 3.6m

Financial health · 2025

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

Who owns NEA 1 AS?

NEA 1 AS
· NOK −18,000 profit

NEA 1 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NEA 1 AS own?

NEA 1 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NEA 1 AS

Who owns NEA 1 AS?

SUNNIVA SIEM is the largest registered owner, with 100.0%.

Where is NEA 1 AS based?

NEA 1 AS has its business address in Jar.

Property

Business address Vollsveien 26B, 1358 Jar
Cadastral unit 3201-40/191/0/0
Building Enebolig m/hybel/sokkelleil. · 2 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.