biztrac. BETA
COMPANY REGISTER PROFILE
830845992 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other postal and courier activities

KOCAK TRANSPORT AS

Org. no. 830845992 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 145,000
Equity NOK 194,000
Incorporated 2023
Share capital NOK 30,000

KOCAK TRANSPORT AS is registered as a limited company in Oslo, Oslo with organisation number 830845992. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøring av gods varer på vei.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 145,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▲ +6 %
Operating profit
NOK 145,000
▼ −6 %
Equity
NOK 194,000
▲ +27 %
Est. value
NOK 470,000

Financial health · 2025

Liquidity
2.35
Very good
Current assets ÷ current liabilities
Profitability
17.9%
Very good
Return on total assets
Solidity
24.0%
Good
Equity as a share of total capital

Who owns KOCAK TRANSPORT AS?

KOCAK TRANSPORT AS
NOK 1.4m rev. · NOK 145,000 profit

KOCAK TRANSPORT AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about KOCAK TRANSPORT AS

Who owns KOCAK TRANSPORT AS?

Nebi Kocak is the largest registered owner, with 100.0%.

What is the revenue of KOCAK TRANSPORT AS?

KOCAK TRANSPORT AS had revenue of NOK 1.4m in 2025.

Who is the general manager of KOCAK TRANSPORT AS?

Nebi Kocak is registered as general manager of KOCAK TRANSPORT AS.

Where is KOCAK TRANSPORT AS based?

KOCAK TRANSPORT 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.