BIZTRAC BETA
Site preparation

ØYER MASKIN OG TRANSPORT AS

Org. no. 929522966 Limited company (AS) Øyer Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 7.1m
Operating profit NOK 30,000
Equity NOK 184,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-29 Adresseendring registrert 2026-06-29.

ØYER MASKIN OG TRANSPORT AS is registered as a limited company in Øyer, Innlandet with organisation number 929522966. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Graving og massetransport. Anleggsvirksomhet. Kjøp og salg i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.1m in revenue and NOK 30,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.1m
Operating profit
NOK 30,000
Equity
NOK 184,000
Est. value
NOK 155,000

Financial health · 2024

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

Who owns ØYER MASKIN OG TRANSPORT AS?

MAGNUS ODDEN
ØYER MASKIN OG TRANSPORT AS
NOK 7.1m rev. · NOK 30,000 profit

ØYER MASKIN OG TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØYER MASKIN OG TRANSPORT AS

Who owns ØYER MASKIN OG TRANSPORT AS?

MAGNUS ODDEN is the largest registered owner, with 50.0%.

What is the revenue of ØYER MASKIN OG TRANSPORT AS?

ØYER MASKIN OG TRANSPORT AS had revenue of NOK 7.1m in 2024.

Who is the general manager of ØYER MASKIN OG TRANSPORT AS?

Magnus Odden is registered as general manager of ØYER MASKIN OG TRANSPORT AS.

Where is ØYER MASKIN OG TRANSPORT AS based?

ØYER MASKIN OG TRANSPORT AS has its business address in Øyer.

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.