BIZTRAC BETA
Freight transport by road

JAN-ERIK RAFOSS TRANSPORT AS

Org. no. 917546037 Limited company (AS) Kvinesdal Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 16.4m
Operating profit NOK 1.1m
Equity NOK 4.7m
Incorporated 2016
Employees 10
Share capital NOK 30,000

JAN-ERIK RAFOSS TRANSPORT AS is registered as a limited company in Kvinesdal, Agder with organisation number 917546037. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2016 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Godstransport på vei, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.4m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 16.4m
Operating profit
NOK 1.1m
Equity
NOK 4.7m
Est. value
NOK 6.5m

Financial health · 2025

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

Who owns JAN-ERIK RAFOSS TRANSPORT AS?

JAN-ERIK RAFOSS
JAN-ERIK RAFOSS TRANSPORT AS
NOK 16.4m rev. · NOK 1.1m profit

JAN-ERIK RAFOSS TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JAN-ERIK RAFOSS TRANSPORT AS

Who owns JAN-ERIK RAFOSS TRANSPORT AS?

JAN-ERIK RAFOSS is the largest registered owner, with 100.0%.

What is the revenue of JAN-ERIK RAFOSS TRANSPORT AS?

JAN-ERIK RAFOSS TRANSPORT AS had revenue of NOK 16.4m in 2025.

Who is the general manager of JAN-ERIK RAFOSS TRANSPORT AS?

Jan-Erik Rafoss is registered as general manager of JAN-ERIK RAFOSS TRANSPORT AS.

Where is JAN-ERIK RAFOSS TRANSPORT AS based?

JAN-ERIK RAFOSS TRANSPORT AS has its business address in Kvinesdal.

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.