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

SOLBØ INVEST AS

Org. no. 915045413 Limited company (AS) Drammen Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 29,000
Incorporated 2015
Share capital NOK 30,000

SOLBØ INVEST AS is registered as a limited company in Drammen, Buskerud with organisation number 915045413. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer, samt investere i virksomheter av enhver art.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 29,000
▲ +0 %
Est. value
NOK 16,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SOLBØ INVEST AS?

SOLBØ INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOLBØ INVEST AS own?

SOLBØ INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLBØ INVEST AS

Who owns SOLBØ INVEST AS?

STIG FLATEBØ is the largest registered owner, with 50.0%.

Where is SOLBØ INVEST AS based?

SOLBØ INVEST AS has its business address in Drammen.

Property

Business address Fredlihavna 32, 3031 Drammen
Cadastral unit 3301-81/348/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.