BIZTRAC BETA
Freight transport by road

SØRENSEN TRANSPORT AS

Org. no. 925132624 Limited company (AS) Ringsaker Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 386,000
Operating profit NOK 126,000
Equity NOK 9,000
Incorporated 2020
Share capital NOK 30,000

SØRENSEN TRANSPORT AS is registered as a limited company in Ringsaker, Innlandet with organisation number 925132624. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Transport av grus og masser og andre produkter/tjenester som naturlig hører sammen med dette, samt utleie av maskiner.”. The most recent filed accounts, for the 2025 financial year, show NOK 386,000 in revenue and NOK 126,000 in operating profit.

Key figures · 2025

Revenue
NOK 386,000
Operating profit
NOK 126,000
Equity
NOK 9,000
Est. value
NOK 347,000

Financial health · 2024

Liquidity
0.65
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.4%
Weak
Equity as a share of total capital

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

Who owns SØRENSEN TRANSPORT AS?

KJETIL SØRENSEN
SØRENSEN TRANSPORT AS
NOK 386,000 rev. · NOK 126,000 profit

SØRENSEN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SØRENSEN TRANSPORT AS

Who owns SØRENSEN TRANSPORT AS?

KJETIL SØRENSEN is the largest registered owner, with 100.0%.

What is the revenue of SØRENSEN TRANSPORT AS?

SØRENSEN TRANSPORT AS had revenue of NOK 386,000 in 2025.

Who is the general manager of SØRENSEN TRANSPORT AS?

Kjetil Sørensen is registered as general manager of SØRENSEN TRANSPORT AS.

Where is SØRENSEN TRANSPORT AS based?

SØRENSEN TRANSPORT AS has its business address in Brumunddal.

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.