biztrac. BETA
COMPANY REGISTER PROFILE
826201592 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

RASK LEVERINGSTJENESTE AS

Org. no. 826201592 Limited company (AS) Oslo Incorporated 2020 Active
Revenue 2025 NOK 1.5m
Operating profit NOK 70,000
Equity NOK 312,000
Incorporated 2020
Share capital NOK 30,000

RASK LEVERINGSTJENESTE AS is registered as a limited company in Oslo, Oslo with organisation number 826201592. 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 100 shares. The company's stated purpose is: “Drift av gods- og varetransport. Alt er i forbindelse med gods- og varetransport.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 70,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
▼ −56 %
Operating profit
NOK 70,000
▼ −79 %
Equity
NOK 312,000
▼ −31 %
Est. value
NOK 529,000

Financial health · 2025

Liquidity
2.77
Very good
Current assets ÷ current liabilities
Profitability
5.0%
Weak
Return on total assets
Solidity
23.4%
Good
Equity as a share of total capital

Who owns RASK LEVERINGSTJENESTE AS?

RASK LEVERINGSTJENESTE AS
NOK 1.5m rev. · NOK 70,000 profit

RASK LEVERINGSTJENESTE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RASK LEVERINGSTJENESTE AS

Who owns RASK LEVERINGSTJENESTE AS?

Kovan Qader Saleh is the largest registered owner, with 100.0%.

What is the revenue of RASK LEVERINGSTJENESTE AS?

RASK LEVERINGSTJENESTE AS had revenue of NOK 1.5m in 2025.

Who is the general manager of RASK LEVERINGSTJENESTE AS?

Kovan Qader Saleh is registered as general manager of RASK LEVERINGSTJENESTE AS.

Where is RASK LEVERINGSTJENESTE AS based?

RASK LEVERINGSTJENESTE AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.