BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

OSLO MASKIN AS

Org. no. 921591020 Limited company (AS) Nannestad Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 56.6m
Operating profit NOK 4.9m
Equity NOK 14.6m
Incorporated 2018
Employees 10
Share capital NOK 30,000

OSLO MASKIN AS is registered as a limited company in Nannestad, Akershus with organisation number 921591020. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Import og eksport, kjøp og salg av anleggsmaskiner og utstyr.”. The most recent filed accounts, for the 2024 financial year, show NOK 56.6m in revenue and NOK 4.9m in operating profit.

Key figures · 2024

Revenue
NOK 56.6m
Operating profit
NOK 4.9m
Equity
NOK 14.6m
Est. value
NOK 26.5m

Financial health · 2024

Liquidity
6.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
88.7%
Very good
Equity as a share of total capital

Who owns OSLO MASKIN AS?

NESRIN ZABET
OSLO MASKIN AS
NOK 56.6m rev. · NOK 4.9m profit

OSLO MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OSLO MASKIN AS own?

OSLO MASKIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OSLO MASKIN AS

Who owns OSLO MASKIN AS?

NESRIN ZABET is the largest registered owner, with 100.0%.

What is the revenue of OSLO MASKIN AS?

OSLO MASKIN AS had revenue of NOK 56.6m in 2024.

Who is the general manager of OSLO MASKIN AS?

Ihab Ezzeldine is registered as general manager of OSLO MASKIN AS.

Where is OSLO MASKIN AS based?

OSLO MASKIN AS has its business address in Nannestad.

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.