BIZTRAC BETA
Business and other management consultancy activities

GBHJ AS

Org. no. 930735345 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 32,000
Operating profit NOK 26,000
Equity NOK 52,000
Incorporated 2022
Share capital NOK 30,000

GBHJ AS is registered as a limited company in Bærum, Akershus with organisation number 930735345. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tilby rådgivning innenfor markedsføring, strategi og ledelse og enhver art som står i forbindelse. Selskapet skal også drive investeringsvirksomhet, herunder å eie og forvalte aksjer, verdipapirer, fast eiendom og andre formuesverdier, deltagelse i andre selskaper og hva herved står i forbindelse, samt å gi støtte til veldedige og allmennyttige formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 32,000 in revenue and NOK 26,000 in operating profit.

Key figures · 2025

Revenue
NOK 32,000
Operating profit
NOK 26,000
Equity
NOK 52,000
Est. value
NOK 118,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GBHJ AS?

GUNN BERIT HOEL JOMAAS
GBHJ AS
NOK 32,000 rev. · NOK 26,000 profit

GBHJ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GBHJ AS

Who owns GBHJ AS?

GUNN BERIT HOEL JOMAAS is the largest registered owner, with 100.0%.

What is the revenue of GBHJ AS?

GBHJ AS had revenue of NOK 32,000 in 2025.

Where is GBHJ AS based?

GBHJ AS has its business address in Jar.

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.