BIZTRAC BETA
Freight transport by road

TRANSIGO AS

Org. no. 835655032 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 390,000
Operating profit NOK −154,000
Equity NOK −92,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−92k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−154k kr).

TRANSIGO AS is registered as a limited company in Drammen, Buskerud with organisation number 835655032. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Transport av gods og varer, samt drive med oppdragsbaserte jobber, flyttehjelp og tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 390,000 in revenue and NOK −154,000 in operating profit.

Key figures · 2025

Revenue
NOK 390,000
Operating profit
NOK −154,000
Equity
NOK −92,000

Financial health · 2025

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

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

Who owns TRANSIGO AS?

Faizan Sarwar
TRANSIGO AS
NOK 390,000 rev. · NOK −154,000 profit

TRANSIGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRANSIGO AS

Who owns TRANSIGO AS?

Faizan Sarwar is the largest registered owner, with 100.0%.

What is the revenue of TRANSIGO AS?

TRANSIGO AS had revenue of NOK 390,000 in 2025.

Who is the general manager of TRANSIGO AS?

Faizan Sarwar is registered as general manager of TRANSIGO AS.

Where is TRANSIGO AS based?

TRANSIGO AS has its business address in Drammen.

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.