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

HELLERUD'S TRANSPORT AS

Org. no. 922661650 Limited company (AS) Indre Østfold Incorporated 2019 Active
Revenue 2025 NOK 575,000
Operating profit NOK −98,000
Equity NOK −465,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−465k kr).

HELLERUD'S TRANSPORT AS is registered as a limited company in Indre Østfold, Østfold with organisation number 922661650. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Vi mener å skape arbeidsplasser.”. The most recent filed accounts, for the 2025 financial year, show NOK 575,000 in revenue and NOK −98,000 in operating profit.

Key figures · 2025

Revenue
NOK 575,000
▼ −42 %
Operating profit
NOK −98,000
▼ −214 %
Equity
NOK −465,000
▼ −43 %

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
-11.0%
Not satisfactory
Return on total assets
Solidity
-60.1%
Weak
Equity as a share of total capital

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

Who owns HELLERUD'S TRANSPORT AS?

HELLERUD'S TRANSPORT AS
NOK 575,000 rev. · NOK −98,000 profit

HELLERUD'S TRANSPORT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELLERUD'S TRANSPORT AS

Who owns HELLERUD'S TRANSPORT AS?

John Arild Hellerud is the largest registered owner, with 60.0%.

What is the revenue of HELLERUD'S TRANSPORT AS?

HELLERUD'S TRANSPORT AS had revenue of NOK 575,000 in 2025.

Where is HELLERUD'S TRANSPORT AS based?

HELLERUD'S TRANSPORT AS has its business address in Trøgstad.

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.