biztrac. BETA
COMPANY REGISTER PROFILE
964434670 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

SST DRIFT & TERMINAL AS

Org. no. 964434670 Limited company (AS) Stange Incorporated 1992 Active
Ownership graph ↗
Operating profit NOK −11,000
Equity NOK 458,000
Incorporated 1992
Share capital NOK 1.1m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SST DRIFT & TERMINAL AS is registered as a limited company in Stange, Innlandet with organisation number 964434670. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1992. Registered share capital is NOK 1.1m, divided into 1050 shares. The company's stated purpose is: “Transport og transportformidling, samt deltagelse i annen virksomhet med samme eller lignende formål.”.

Former names: THORE M WIKEN TRANSPORT AS

Key figures · 2025

Operating profit
NOK −11,000
▲ +29 %
Equity
NOK 458,000
▲ +19 %
Est. value
NOK 633,000

Financial health · 2025

Liquidity
268.84
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 SST DRIFT & TERMINAL AS?

SST DRIFT & TERMINAL AS
· NOK −11,000 profit

SST DRIFT & TERMINAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SST DRIFT & TERMINAL AS own?

SST DRIFT & TERMINAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SST DRIFT & TERMINAL AS

Who owns SST DRIFT & TERMINAL AS?

WEENSVANGEN VED AS is the largest registered owner, with 100.0%.

Where is SST DRIFT & TERMINAL AS based?

SST DRIFT & TERMINAL AS has its business address in Espa.

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.