BIZTRAC BETA
Uoppgitt

SRJ HOLDING AS

Org. no. 927612623 Limited company (AS) Sola Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2021
Share capital NOK 30,000

SRJ HOLDING AS is registered as a limited company in Sola, Rogaland with organisation number 927612623. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selskapets virksomhet skal kunne være - direkte og/eller indirekte - å kjøpe, eie og selge aksjer, obligasjoner og andre finansielle instrumenter og alt som er beslektet eller står i forbindelse med dette. Videre skal selskapets virksomhet kunne være - direkte og/eller indirekte - å anskaffe, prosjektere, utbygge, eie, drive, leie ut og selge fast eiendom og alt som er beslektet eller står i forbindelse med slik virksomhet. Selskapet skal også kunne eie - helt eller delvis - eller delta i selskaper eller næringsforetak som driver annen virksomhet.”.

Key figures · 2025

Operating profit
NOK 0
Equity
NOK 30,000
Est. value
NOK 35,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 SRJ HOLDING AS?

STIAN RUDE JACOBSEN
SRJ HOLDING AS
· NOK 0 profit

SRJ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SRJ HOLDING AS own?

SRJ HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SRJ HOLDING AS

Who owns SRJ HOLDING AS?

STIAN RUDE JACOBSEN is the largest registered owner, with 100.0%.

Where is SRJ HOLDING AS based?

SRJ HOLDING AS has its business address in Tananger.

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.