biztrac. BETA
COMPANY REGISTER PROFILE
938054819 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of mining, construction and civil engineering machinery

G S CONSULT AS

Org. no. 938054819 Limited company (AS) Bærum Incorporated 1985 Active
Ownership graph ↗
Revenue 2025 NOK 39.2m
Operating profit NOK 4.1m
Equity NOK 4.8m
Incorporated 1985
Share capital NOK 100,000

G S CONSULT AS is registered as a limited company in Bærum, Akershus with organisation number 938054819. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1985. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Konsulentvirksomhet og handel særlig med sikte på produkter og service for off-shore industrien og alt som står i forbindelse med det samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.2m in revenue and NOK 4.1m in operating profit.

Key figures · 2025

Revenue
NOK 39.2m
▲ +14 %
Operating profit
NOK 4.1m
▲ +659 %
Equity
NOK 4.8m
▲ +160 %
Est. value
NOK 12.7m

Financial health · 2025

Liquidity
1.58
Good
Current assets ÷ current liabilities
Profitability
47.8%
Very good
Return on total assets
Solidity
38.0%
Good
Equity as a share of total capital

Who owns G S CONSULT AS?

G S CONSULT AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about G S CONSULT AS

Who owns G S CONSULT AS?

Gudmund Risvig Stenersen is the largest registered owner, with 84.0%.

What is the revenue of G S CONSULT AS?

G S CONSULT AS had revenue of NOK 39.2m in 2025.

Who is the general manager of G S CONSULT AS?

Gudmund Risvig Stenersen is registered as general manager of G S CONSULT AS.

Where is G S CONSULT AS based?

G S CONSULT AS has its business address in Østerås.

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.