BIZTRAC BETA
Business and other management consultancy activities

SOBRAX AS

Org. no. 916665776 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −66,000
Equity NOK −15,000
Incorporated 2016
Share capital NOK 106,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−15k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−66k kr).

SOBRAX AS is registered as a limited company in Stavanger, Rogaland with organisation number 916665776. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 106,000, divided into 1000 shares. The company's stated purpose is: “Etablere selskaper med fokus på teknologi og tjeneste leveranser til et globalt marked. Etablere aktivitet innehåndtering av LNG (Flytende Natur Gas) og alle tilstøtende tjenester. Fronte implementering og bruk av teknologi innenfor energi distribusjon. Tilrettelegge for annen tilstøtende aktivitet og virksomhet gjennom selskapets ulike etableringer og tilstedeværelser. ”.

Key figures · 2024

Operating profit
NOK −66,000
Equity
NOK −15,000

Financial health · 2024

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

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

Who owns SOBRAX AS?

COD AS
SOBRAX AS
· NOK −66,000 profit

SOBRAX AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOBRAX AS

Who owns SOBRAX AS?

COD AS is the largest registered owner, with 45.0%.

Who is the general manager of SOBRAX AS?

Oddvar Skjæveland is registered as general manager of SOBRAX AS.

Where is SOBRAX AS based?

SOBRAX AS has its business address in Stavanger.

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.