BIZTRAC BETA
Freight transport by road

ØSTHAGEN MILJØTRANSPORT AS

Org. no. 920450695 Limited company (AS) Elverum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK 652,000
Equity NOK 642,000
Incorporated 2018
Share capital NOK 100,000

ØSTHAGEN MILJØTRANSPORT AS is registered as a limited company in Elverum, Innlandet with organisation number 920450695. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transportvirksomhet og annen virksomhet i forbindelse med dette, herunder deltagelse i andre selskap med samme eller lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK 652,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK 652,000
Equity
NOK 642,000
Est. value
NOK 2.2m

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.4%
Good
Equity as a share of total capital

Who owns ØSTHAGEN MILJØTRANSPORT AS?

KNUT TONY ØSTHAGEN
ØSTHAGEN MILJØTRANSPORT AS
NOK 5.3m rev. · NOK 652,000 profit

ØSTHAGEN MILJØTRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØSTHAGEN MILJØTRANSPORT AS

Who owns ØSTHAGEN MILJØTRANSPORT AS?

KNUT TONY ØSTHAGEN is the largest registered owner, with 70.0%.

What is the revenue of ØSTHAGEN MILJØTRANSPORT AS?

ØSTHAGEN MILJØTRANSPORT AS had revenue of NOK 5.3m in 2025.

Who is the general manager of ØSTHAGEN MILJØTRANSPORT AS?

Knut Tony Østhagen is registered as general manager of ØSTHAGEN MILJØTRANSPORT AS.

Where is ØSTHAGEN MILJØTRANSPORT AS based?

ØSTHAGEN MILJØTRANSPORT AS has its business address in Elverum.

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.