biztrac. BETA
COMPANY REGISTER PROFILE
921598793 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

TRANSPORTSENTER LARVIK AS

Org. no. 921598793 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 34.0m
Operating profit NOK −534,000
Equity NOK 1.2m
Incorporated 2018
Employees 11
Share capital NOK 240,000

Signals

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

TRANSPORTSENTER LARVIK AS is registered as a limited company in Larvik, Vestfold with organisation number 921598793. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2018 and has 11 registered employees. Registered share capital is NOK 240,000, divided into 30 shares. The company's stated purpose is: “Transportformidling og dertil beslektede virkeområder.”. The most recent filed accounts, for the 2025 financial year, show NOK 34.0m in revenue and NOK −534,000 in operating profit.

Key figures · 2025

Revenue
NOK 34.0m
▲ +13 %
Operating profit
NOK −534,000
▲ +25 %
Equity
NOK 1.2m
▼ −35 %
Est. value
NOK 15.9m

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
-8.4%
Not satisfactory
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns TRANSPORTSENTER LARVIK AS?

TRANSPORTSENTER LARVIK AS
NOK 34.0m rev. · NOK −534,000 profit

TRANSPORTSENTER LARVIK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRANSPORTSENTER LARVIK AS

Who owns TRANSPORTSENTER LARVIK AS?

GA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TRANSPORTSENTER LARVIK AS?

TRANSPORTSENTER LARVIK AS had revenue of NOK 34.0m in 2025.

Where is TRANSPORTSENTER LARVIK AS based?

TRANSPORTSENTER LARVIK AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.