BIZTRAC BETA
COMPANY REGISTER PROFILE
989034510 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SANS INVEST AS

Org. no. 989034510 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −2.0m
Equity NOK 76.5m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−2,0 mill kr).

SANS INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 989034510. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Generell investeringsvirksomhet, herunder investering i verdipapirer, valuta, eiendommer, andeler etc. samt delta i eller eie selskaper med beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −2.0m in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −2.0m
▼ −711 %
Equity
NOK 76.5m
▲ +5 %
Est. value
NOK 82.4m

Financial health · 2025

Liquidity
11.69
Very good
Current assets ÷ current liabilities
Profitability
13.5%
Good
Return on total assets
Solidity
91.4%
Very good
Equity as a share of total capital

Who owns SANS INVEST AS?

SANS INVEST AS
NOK 0 rev. · NOK −2.0m profit

SANS INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SANS INVEST AS own?

SANS INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SANS INVEST AS

Who owns SANS INVEST AS?

GEORG WILHELM BJØRNESTAD is the largest registered owner, with 100.0%.

What is the revenue of SANS INVEST AS?

SANS INVEST AS had revenue of NOK 0 in 2025.

Where is SANS INVEST AS based?

SANS INVEST AS has its business address in Østerås.

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

Report a problem

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