BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

SBS TECHNOLOGY AS

Org. no. 821689422 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 11.9m
Operating profit NOK 11.5m
Equity NOK 143,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SBS TECHNOLOGY AS is registered as a limited company in Bergen, Vestland with organisation number 821689422. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utvikle, kjøpe og selge produkter til bruk i olje og gass utvinning, herunder også direkte eller indirekte eie i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.9m in revenue and NOK 11.5m in operating profit.

Key figures · 2024

Revenue
NOK 11.9m
Operating profit
NOK 11.5m
Equity
NOK 143,000
Est. value
NOK 35.4m

Financial health · 2024

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

Who owns SBS TECHNOLOGY AS?

ENTECH SOLUTIONS AS
SBS TECHNOLOGY AS
NOK 11.9m rev. · NOK 11.5m profit

SBS TECHNOLOGY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SBS TECHNOLOGY AS

Who owns SBS TECHNOLOGY AS?

ENTECH SOLUTIONS AS is the largest registered owner, with 100.0%.

What is the revenue of SBS TECHNOLOGY AS?

SBS TECHNOLOGY AS had revenue of NOK 11.9m in 2024.

Where is SBS TECHNOLOGY AS based?

SBS TECHNOLOGY AS has its business address in Indre Arna.

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.