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

MIDTSTØL BULK AS

Org. no. 880544322 Limited company (AS) Arendal Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 1.2m
Equity NOK 3.9m
Incorporated 1999
Share capital NOK 100,000

MIDTSTØL BULK AS is registered as a limited company in Arendal, Agder with organisation number 880544322. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Logistikk og transport, herunder bulktransport, og annet som ligger i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 1.2m in operating profit.

Former names: DAG MALMQUIST TRANSPORT AS, MALMQUIST TRANSPORT AS

Key figures · 2025

Revenue
NOK 4.8m
▼ −57 %
Operating profit
NOK 1.2m
▲ +253 %
Equity
NOK 3.9m
▲ +24 %
Est. value
NOK 3.9m

Financial health · 2025

Liquidity
6.91
Very good
Current assets ÷ current liabilities
Profitability
25.8%
Very good
Return on total assets
Solidity
89.2%
Very good
Equity as a share of total capital

Who owns MIDTSTØL BULK AS?

MIDTSTØL BULK AS
NOK 4.8m rev. · NOK 1.2m profit

MIDTSTØL BULK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MIDTSTØL BULK AS

Who owns MIDTSTØL BULK AS?

MIDTSTØL TRANSPORT AS is the largest registered owner, with 100.0%.

What is the revenue of MIDTSTØL BULK AS?

MIDTSTØL BULK AS had revenue of NOK 4.8m in 2025.

Who is the general manager of MIDTSTØL BULK AS?

Rune Midtstøl is registered as general manager of MIDTSTØL BULK AS.

Where is MIDTSTØL BULK AS based?

MIDTSTØL BULK AS has its business address in Arendal.

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.