BIZTRAC BETA
Service activities incidental to water transportation

TSP SERVICES AS

Org. no. 927213656 Limited company (AS) Stavanger Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 11,000
Operating profit NOK −25,000
Equity NOK 64,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

TSP SERVICES AS is registered as a limited company in Stavanger, Rogaland with organisation number 927213656. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av servicetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 11,000 in revenue and NOK −25,000 in operating profit.

Key figures · 2025

Revenue
NOK 11,000
Operating profit
NOK −25,000
Equity
NOK 64,000
Est. value
NOK 38,000

Financial health · 2024

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

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

Who owns TSP SERVICES AS?

TORSTEIN SKAAREN PEDERSEN
TSP SERVICES AS
NOK 11,000 rev. · NOK −25,000 profit

TSP SERVICES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TSP SERVICES AS

Who owns TSP SERVICES AS?

TORSTEIN SKAAREN PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TSP SERVICES AS?

TSP SERVICES AS had revenue of NOK 11,000 in 2025.

Who is the general manager of TSP SERVICES AS?

Torstein Skaaren Pedersen is registered as general manager of TSP SERVICES AS.

Where is TSP SERVICES AS based?

TSP SERVICES AS has its business address in Mosterøy.

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.