biztrac. BETA
COMPANY REGISTER PROFILE
917247781 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Other publishing activities, except software publishing

DISRUPT SA

Org. no. 917247781 Co-operation (SA) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 73
Operating profit NOK −2,000
Equity NOK 6,000
Incorporated 2016

Signals

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

DISRUPT SA is registered as a co-operation in Stavanger, Rogaland with organisation number 917247781. The business is classified under other publishing activities, except software publishing (NACE 58.190). The company was incorporated in 2016. The company's stated purpose is: “Forlags-, innovasjons- og konsulentvirksomhet. Foretaket har til formål å fremme medlemmenes økonomiske interesser gjennom deres deltakelse i virksomheten som leverandører av varer/tjenester til foretaket.”. The most recent filed accounts, for the 2025 financial year, show NOK 73 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 73
▲ +135 %
Operating profit
NOK −2,000
▼ −5 %
Equity
NOK 6,000
▼ −25 %
Est. value
NOK 11,000

Financial health · 2025

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

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

Who owns DISRUPT SA?

No shareholders are registered for DISRUPT SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Which companies does DISRUPT SA own?

DISRUPT SA holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DISRUPT SA

What is the revenue of DISRUPT SA?

DISRUPT SA had revenue of NOK 73 in 2025.

Where is DISRUPT SA based?

DISRUPT SA has its business address in Stavanger.

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

Report a problem

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