BIZTRAC BETA
Beverage serving activities

SBT SERVICE AS

Org. no. 998362393 Limited company (AS) Harstad Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 10.2m
Operating profit NOK −636,000
Equity NOK 11,000
Incorporated 2012
Employees 36
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−636k kr).

SBT SERVICE AS is registered as a limited company in Harstad, Troms with organisation number 998362393. The business is classified under beverage serving activities (NACE 56.300). The company was incorporated in 2012 and has 36 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive bar og serveringsvirksomhet, samt alt som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.2m in revenue and NOK −636,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.2m
Operating profit
NOK −636,000
Equity
NOK 11,000
Est. value
NOK 6.9m

Financial health · 2024

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

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

Who owns SBT SERVICE AS?

STÅLE BRÆCK
SBT SERVICE AS
NOK 10.2m rev. · NOK −636,000 profit

SBT SERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SBT SERVICE AS

Who owns SBT SERVICE AS?

STÅLE BRÆCK is the largest registered owner, with 33.3%.

What is the revenue of SBT SERVICE AS?

SBT SERVICE AS had revenue of NOK 10.2m in 2024.

Who is the general manager of SBT SERVICE AS?

Toni Alexandra Lindeberg Eriksen is registered as general manager of SBT SERVICE AS.

Where is SBT SERVICE AS based?

SBT SERVICE AS has its business address in Harstad.

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.