BIZTRAC BETA
Other education activities

TEAM TRUCKSERVICE AS

Org. no. 954379442 Limited company (AS) Tønsberg Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 770,000
Operating profit NOK −102,000
Equity NOK 330,000
Incorporated 1989
Share capital NOK 100,000

Signals

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

TEAM TRUCKSERVICE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 954379442. The business is classified under other education activities (NACE 85.597). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Sikkerhetsopplæring i bruk av arbeidsutstyr og konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 770,000 in revenue and NOK −102,000 in operating profit.

Key figures · 2025

Revenue
NOK 770,000
Operating profit
NOK −102,000
Equity
NOK 330,000
Est. value
NOK 842,000

Financial health · 2025

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

Who owns TEAM TRUCKSERVICE AS?

BJØRN ALMAR ROLSTAD JOHANSEN
TEAM TRUCKSERVICE AS
NOK 770,000 rev. · NOK −102,000 profit

TEAM TRUCKSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TEAM TRUCKSERVICE AS

Who owns TEAM TRUCKSERVICE AS?

BJØRN ALMAR ROLSTAD JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of TEAM TRUCKSERVICE AS?

TEAM TRUCKSERVICE AS had revenue of NOK 770,000 in 2025.

Who is the general manager of TEAM TRUCKSERVICE AS?

Bjørn Almar Rolstad Johansen is registered as general manager of TEAM TRUCKSERVICE AS.

Where is TEAM TRUCKSERVICE AS based?

TEAM TRUCKSERVICE AS has its business address in Sem.

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.