BIZTRAC BETA
Freight transport by road

SMIDSRØD TRANSPORT AS

Org. no. 977274567 Limited company (AS) Tønsberg Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 7.5m
Operating profit NOK 834,000
Equity NOK 964,000
Incorporated 1997
Share capital NOK 112,000

SMIDSRØD TRANSPORT AS is registered as a limited company in Tønsberg, Vestfold with organisation number 977274567. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1997. Registered share capital is NOK 112,000, divided into 14000 shares. The company's stated purpose is: “Drive innenlands og utenlands transportvirksomhet, samt virksomhet som står i forbindelse hermed, herunder deltagelse i andre selskaper som aksjonærer eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.5m in revenue and NOK 834,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.5m
Operating profit
NOK 834,000
Equity
NOK 964,000
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns SMIDSRØD TRANSPORT AS?

JON GUNNAR SMIDSRØD
SMIDSRØD TRANSPORT AS
NOK 7.5m rev. · NOK 834,000 profit

SMIDSRØD TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SMIDSRØD TRANSPORT AS

Who owns SMIDSRØD TRANSPORT AS?

JON GUNNAR SMIDSRØD is the largest registered owner, with 100.0%.

What is the revenue of SMIDSRØD TRANSPORT AS?

SMIDSRØD TRANSPORT AS had revenue of NOK 7.5m in 2025.

Who is the general manager of SMIDSRØD TRANSPORT AS?

Jon Gunnar Smidsrød is registered as general manager of SMIDSRØD TRANSPORT AS.

Where is SMIDSRØD TRANSPORT AS based?

SMIDSRØD TRANSPORT AS has its business address in Ramnes.

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.