biztrac. BETA
COMPANY REGISTER PROFILE
823242832 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
All other professional, scientific and technical activities n.e.c.

YM CONSULT AS

Org. no. 823242832 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK 1.4m
Equity NOK 1.8m
Incorporated 2019
Share capital NOK 30,000

YM CONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 823242832. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Yte konsulenttjenester innenfor ytremiljø som miljøkartlegging av bygg, miljøtekniske grunnundersøkelser, avfallsplaner og sluttdokumentasjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 1.4m in operating profit.

Former names: ØST MILJØRÅDGIVNING AS

Key figures · 2025

Revenue
NOK 7.9m
▲ +33 %
Operating profit
NOK 1.4m
▲ +319 %
Equity
NOK 1.8m
▲ +138 %
Est. value
NOK 6.7m

Financial health · 2025

Liquidity
2.05
Very good
Current assets ÷ current liabilities
Profitability
55.7%
Very good
Return on total assets
Solidity
60.2%
Very good
Equity as a share of total capital

Who owns YM CONSULT AS?

YM CONSULT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about YM CONSULT AS

Who owns YM CONSULT AS?

Said Moqim Bani Hashem is the largest registered owner, with 51.0%.

What is the revenue of YM CONSULT AS?

YM CONSULT AS had revenue of NOK 7.9m in 2025.

Who is the general manager of YM CONSULT AS?

Said Moqim Bani Hashem is registered as general manager of YM CONSULT AS.

Where is YM CONSULT AS based?

YM CONSULT AS has its business address in Oslo.

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.