BIZTRAC BETA
COMPANY REGISTER PROFILE
826017112 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

NEAT HOLDINGS AS

Org. no. 826017112 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −851,000
Equity NOK 39.6m
Incorporated 2020
Share capital NOK 100,000

Signals

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

NEAT HOLDINGS AS is registered as a limited company in Bærum, Akershus with organisation number 826017112. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 5017762 shares. The company's stated purpose is: “Holdingselskap for Neatframe-eide selskaper.”.

Former names: NFH 201131 AS

Key figures · 2025

Operating profit
NOK −851,000
▼ −129 %
Equity
NOK 39.6m
▼ −72 %
Est. value
NOK 46.6m

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.9%
Not satisfactory
Return on total assets
Solidity
99.5%
Very good
Equity as a share of total capital

Who owns NEAT HOLDINGS AS?

NEAT HOLDINGS AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about NEAT HOLDINGS AS

Who owns NEAT HOLDINGS AS?

VISI INVEST AS is the largest registered owner, with 12.0%.

Where is NEAT HOLDINGS AS based?

NEAT HOLDINGS AS has its business address in Fornebu.

Property

Business address Martin Linges vei 25, 1364 Fornebu
Cadastral unit 3201-41/779/0/0
Building Kontor- og administrasjonsbygning, rådhus · 4 units

192 companies are registered at this address.

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.