BIZTRAC BETA
Freight transport by road

HBP TRANSPORT AS

Org. no. 926451111 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 595,000
Operating profit NOK −37,000
Equity NOK −59,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−59k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−37k kr).

HBP TRANSPORT AS is registered as a limited company in Oslo, Oslo with organisation number 926451111. 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: “Godstransport på vei, budtjenester, transport av varer og gods. Logistikk og herunder å kunne delta i selskap med lignende virksomhet, samt kjøp og salg av aksjer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 595,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2024

Revenue
NOK 595,000
Operating profit
NOK −37,000
Equity
NOK −59,000

Financial health · 2024

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

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

Who owns HBP TRANSPORT AS?

GWTYAR SIWALY
HBP TRANSPORT AS
NOK 595,000 rev. · NOK −37,000 profit

HBP TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HBP TRANSPORT AS

Who owns HBP TRANSPORT AS?

GWTYAR SIWALY is the largest registered owner, with 100.0%.

What is the revenue of HBP TRANSPORT AS?

HBP TRANSPORT AS had revenue of NOK 595,000 in 2024.

Where is HBP TRANSPORT AS based?

HBP 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 15.06.2026.

Report a problem

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