BIZTRAC BETA
Computer programming activities

QG CONSULTING AS

Org. no. 929038614 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 938,000
Operating profit NOK 683,000
Equity NOK 1.9m
Incorporated 2022
Share capital NOK 30,000

QG CONSULTING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 929038614. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen rågivning og konsulenttjenester, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 938,000 in revenue and NOK 683,000 in operating profit.

Key figures · 2024

Revenue
NOK 938,000
Operating profit
NOK 683,000
Equity
NOK 1.9m
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns QG CONSULTING AS?

QUINTON RAJ YOGESWARAN GREGORY
QG CONSULTING AS
NOK 938,000 rev. · NOK 683,000 profit

QG CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about QG CONSULTING AS

Who owns QG CONSULTING AS?

QUINTON RAJ YOGESWARAN GREGORY is the largest registered owner, with 100.0%.

What is the revenue of QG CONSULTING AS?

QG CONSULTING AS had revenue of NOK 938,000 in 2024.

Who is the general manager of QG CONSULTING AS?

Quinton Raj Yogeswaran Gregory is registered as general manager of QG CONSULTING AS.

Where is QG CONSULTING AS based?

QG CONSULTING AS has its business address in Skedsmokorset.

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.