BIZTRAC BETA
Business and other management consultancy activities

JSM GROUP AS

Org. no. 932097761 Limited company (AS) Lillestrøm Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 291,000
Operating profit NOK 261,000
Equity NOK 596,000
Incorporated 2023
Share capital NOK 30,000

JSM GROUP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 932097761. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulent og rådgiving innenfor serveringsbransjen, samt investering, eierskap, deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 291,000 in revenue and NOK 261,000 in operating profit.

Key figures · 2024

Revenue
NOK 291,000
Operating profit
NOK 261,000
Equity
NOK 596,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns JSM GROUP AS?

HAFIZ MEER FAWAD
JSM GROUP AS
NOK 291,000 rev. · NOK 261,000 profit

JSM GROUP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JSM GROUP AS own?

JSM GROUP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JSM GROUP AS

Who owns JSM GROUP AS?

HAFIZ MEER FAWAD is the largest registered owner, with 100.0%.

What is the revenue of JSM GROUP AS?

JSM GROUP AS had revenue of NOK 291,000 in 2024.

Who is the general manager of JSM GROUP AS?

Hafiz Meer Fawad is registered as general manager of JSM GROUP AS.

Where is JSM GROUP AS based?

JSM GROUP AS has its business address in Frogner.

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.