BIZTRAC BETA
Freight transport by road

STEINAR KJÆR TRANSPORT AS

Org. no. 979474504 Limited company (AS) Kristiansand Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 10.6m
Operating profit NOK 266,000
Equity NOK 1.3m
Incorporated 1997
Employees 11
Share capital NOK 120,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STEINAR KJÆR TRANSPORT AS is registered as a limited company in Kristiansand, Agder with organisation number 979474504. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1997 and has 11 registered employees. Registered share capital is NOK 120,000, divided into 120 shares. The company's stated purpose is: “Transportvirksomhet og hva dermed står i forbindelse, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.6m in revenue and NOK 266,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.6m
Operating profit
NOK 266,000
Equity
NOK 1.3m
Est. value
NOK 1.5m

Financial health · 2025

Liquidity
1.83
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
40.0%
Good
Equity as a share of total capital

Who owns STEINAR KJÆR TRANSPORT AS?

TRITO HOLDING AS
STEINAR KJÆR TRANSPORT AS
NOK 10.6m rev. · NOK 266,000 profit

STEINAR KJÆR TRANSPORT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STEINAR KJÆR TRANSPORT AS

Who owns STEINAR KJÆR TRANSPORT AS?

TRITO HOLDING AS is the largest registered owner, with 66.7%.

What is the revenue of STEINAR KJÆR TRANSPORT AS?

STEINAR KJÆR TRANSPORT AS had revenue of NOK 10.6m in 2025.

Where is STEINAR KJÆR TRANSPORT AS based?

STEINAR KJÆR TRANSPORT AS has its business address in Kristiansand S.

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.