BIZTRAC BETA
Other support activities for transportation

SARPSBORG SPEDISJON AS

Org. no. 951118419 Limited company (AS) Sarpsborg Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 256,000
Equity NOK 822,000
Incorporated 1989
Share capital NOK 30,000

SARPSBORG SPEDISJON AS is registered as a limited company in Sarpsborg, Østfold with organisation number 951118419. The business is classified under other support activities for transportation (NACE 52.260). The company was incorporated in 1989. Registered share capital is NOK 30,000, divided into 102 shares. The company's stated purpose is: “Spedisjon og hva hermed står i forbindelse her- under delta i selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 256,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 256,000
Equity
NOK 822,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns SARPSBORG SPEDISJON AS?

SHIPPING PARTNER SARPSBORG HOLDING AS
SARPSBORG SPEDISJON AS
NOK 5.6m rev. · NOK 256,000 profit

SARPSBORG SPEDISJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SARPSBORG SPEDISJON AS

Who owns SARPSBORG SPEDISJON AS?

SHIPPING PARTNER SARPSBORG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SARPSBORG SPEDISJON AS?

SARPSBORG SPEDISJON AS had revenue of NOK 5.6m in 2025.

Who is the general manager of SARPSBORG SPEDISJON AS?

Justine Annette Rude Tangen is registered as general manager of SARPSBORG SPEDISJON AS.

Where is SARPSBORG SPEDISJON AS based?

SARPSBORG SPEDISJON AS has its business address in Sarpsborg.

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.