biztrac. BETA
COMPANY REGISTER PROFILE
937649916 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠ST HOLDING AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Activities of financing conduits

ST HOLDING AS

Org. no. 937649916 Limited company (AS) Drammen Incorporated 1985 In liquidation
Ownership graph ↗
Operating profit NOK −80,000
Equity NOK 11.9m
Incorporated 1985
Share capital NOK 581,000

Signals

3 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−80k kr).
  • Nylig endring 2026-10-07 Under avvikling registrert 2026-10-07.

ST HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 937649916. The business is classified under activities of financing conduits (NACE 64.220). The company was incorporated in 1985. Registered share capital is NOK 581,000, divided into 5805 shares. The company's stated purpose is: “Erverv og drift av fast eiendom, handel og alt som står i forbindelse med ette, herunder deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −80,000
▼ −7 %
Equity
NOK 11.9m
▲ +1 %
Est. value
NOK 6.9m

Financial health · 2025

Liquidity
231.22
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
99.7%
Very good
Equity as a share of total capital

Who owns ST HOLDING AS?

ST HOLDING AS
· NOK −80,000 profit

ST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ST HOLDING AS

Who owns ST HOLDING AS?

Jørgen Lauritz Thorsen is the largest registered owner, with 100.0%.

Who is the general manager of ST HOLDING AS?

Jørgen Lauritz Thorsen is registered as general manager of ST HOLDING AS.

Where is ST HOLDING AS based?

ST HOLDING AS has its business address in Drammen.

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.