BIZTRAC BETA
Repair and maintenance of machinery

TRUCK & MARINE SERVICE AS

Org. no. 991310789 Limited company (AS) Bamble Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 327,000
Equity NOK 767,000
Incorporated 2007
Employees 5
Share capital NOK 100,000

TRUCK & MARINE SERVICE AS is registered as a limited company in Bamble, Telemark with organisation number 991310789. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2007 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Salg/service og reparasjon av trucker og marinemotorer.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 327,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 327,000
Equity
NOK 767,000
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.46
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
23.8%
Good
Equity as a share of total capital

Who owns TRUCK & MARINE SERVICE AS?

PANCOM MANAGEMENT AS
TRUCK & MARINE SERVICE AS
NOK 6.9m rev. · NOK 327,000 profit

TRUCK & MARINE SERVICE AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRUCK & MARINE SERVICE AS

Who owns TRUCK & MARINE SERVICE AS?

PANCOM MANAGEMENT AS is the largest registered owner, with 35.0%.

What is the revenue of TRUCK & MARINE SERVICE AS?

TRUCK & MARINE SERVICE AS had revenue of NOK 6.9m in 2025.

Who is the general manager of TRUCK & MARINE SERVICE AS?

Stephan Philip Hercher is registered as general manager of TRUCK & MARINE SERVICE AS.

Where is TRUCK & MARINE SERVICE AS based?

TRUCK & MARINE SERVICE AS has its business address in Stathelle.

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.