BIZTRAC BETA
Freight transport by road

CARGO LINE AS

Org. no. 931042297 Limited company (AS) Melhus Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 107,000
Operating profit NOK 12,000
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

CARGO LINE AS is registered as a limited company in Melhus, Trøndelag with organisation number 931042297. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Transport av varer på vei med bil. Kjøp, salg og utleie av campingvogner. Formidling og utleie av arbeidskraft - som gjelder begge kjønn. Drive renholdsservice både for industri, kontor, husholdninger og butikker. I forbindelse med renhold: salg av alle typer renholdsutstyr. Investeringer i aksjer og hva som herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 107,000 in revenue and NOK 12,000 in operating profit.

Key figures · 2024

Revenue
NOK 107,000
Operating profit
NOK 12,000
Equity
NOK 30,000
Est. value
NOK 50,000

Financial health · 2024

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

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

Who owns CARGO LINE AS?

ROLF KONRAD LUND
CARGO LINE AS
NOK 107,000 rev. · NOK 12,000 profit

CARGO LINE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about CARGO LINE AS

Who owns CARGO LINE AS?

ROLF KONRAD LUND is the largest registered owner, with 51.0%.

What is the revenue of CARGO LINE AS?

CARGO LINE AS had revenue of NOK 107,000 in 2024.

Where is CARGO LINE AS based?

CARGO LINE AS has its business address in Melhus.

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.