BIZTRAC BETA
Business and other management consultancy activities

SOROBON INVEST AS

Org. no. 823202822 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 310,000
Operating profit NOK 192,000
Equity NOK 143,000
Incorporated 2019
Share capital NOK 30,000

SOROBON INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 823202822. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, samt å tilby konsulenttjenester innen teknologi, innovasjon og forretningsrådgivning. Selskapet kan også eie og forvalte eiendom og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 310,000 in revenue and NOK 192,000 in operating profit.

Key figures · 2025

Revenue
NOK 310,000
Operating profit
NOK 192,000
Equity
NOK 143,000
Est. value
NOK 546,000

Financial health · 2025

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

Who owns SOROBON INVEST AS?

MARIUS OLSEN
SOROBON INVEST AS
NOK 310,000 rev. · NOK 192,000 profit

SOROBON INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOROBON INVEST AS own?

SOROBON INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SOROBON INVEST AS

Who owns SOROBON INVEST AS?

MARIUS OLSEN is the largest registered owner, with 100.0%.

What is the revenue of SOROBON INVEST AS?

SOROBON INVEST AS had revenue of NOK 310,000 in 2025.

Where is SOROBON INVEST AS based?

SOROBON INVEST AS has its business address in Oslo.

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

Report a problem

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