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

SGO INVEST AS

Org. no. 989264699 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 1.8m
Incorporated 2005
Share capital NOK 100,000

Signals

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

SGO INVEST AS is registered as a limited company in Kristiansand, Agder with organisation number 989264699. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Eie andeler i PricewaterhouseCoopers IS, i tillegg til at selskapet kan inneha andre finansielle eiendeler.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK 1.8m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns SGO INVEST AS?

SGO INVEST AS
· NOK −6,000 profit

SGO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SGO INVEST AS

Who owns SGO INVEST AS?

SVEIN GUNNAR OLSEN is the largest registered owner, with 100.0%.

Where is SGO INVEST AS based?

SGO INVEST AS has its business address in Kristiansand S.

Property

Business address Løvika 45, 4623 Kristiansand S
Cadastral unit 4204-9/401/0/0
Building Enebolig · 1 unit

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.