BIZTRAC BETA
Other postal and courier activities

HARMANKAYA TRANSPORT AS

Org. no. 932993279 Limited company (AS) Trondheim Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 33,000
Equity NOK 29,000
Incorporated 2023
Share capital NOK 30,000

HARMANKAYA TRANSPORT AS is registered as a limited company in Trondheim, Trøndelag with organisation number 932993279. 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 1000 shares. The company's stated purpose is: “Transport og budservice av enhver art, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 33,000
Equity
NOK 29,000
Est. value
NOK 107,000

Financial health · 2025

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

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

Who owns HARMANKAYA TRANSPORT AS?

SAIP HARMANKAYA
HARMANKAYA TRANSPORT AS
NOK 1.0m rev. · NOK 33,000 profit

HARMANKAYA TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HARMANKAYA TRANSPORT AS

Who owns HARMANKAYA TRANSPORT AS?

SAIP HARMANKAYA is the largest registered owner, with 100.0%.

What is the revenue of HARMANKAYA TRANSPORT AS?

HARMANKAYA TRANSPORT AS had revenue of NOK 1.0m in 2025.

Who is the general manager of HARMANKAYA TRANSPORT AS?

Saip Harmankaya is registered as general manager of HARMANKAYA TRANSPORT AS.

Where is HARMANKAYA TRANSPORT AS based?

HARMANKAYA TRANSPORT AS has its business address in Trondheim.

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.