BIZTRAC BETA
Business and other management consultancy activities

GNIST HOLDING AS

Org. no. 893061312 Limited company (AS) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 649,000
Operating profit NOK 43,000
Equity NOK 7.4m
Incorporated 2008
Share capital NOK 150,000

GNIST HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 893061312. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2008. Registered share capital is NOK 150,000, divided into 1000000 shares. The company's stated purpose is: “Drive forskning og utvikling innen ledelses/konsulentvirkomshet, eiendomsvirksomhet og forvaltning, båtimport og utleie, investeringer, import av husholdingsartikler til forbruker og bygg.”. The most recent filed accounts, for the 2024 financial year, show NOK 649,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 649,000
Operating profit
NOK 43,000
Equity
NOK 7.4m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns GNIST HOLDING AS?

RICHARD STUART GODFREY
GNIST HOLDING AS
NOK 649,000 rev. · NOK 43,000 profit

GNIST HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GNIST HOLDING AS

Who owns GNIST HOLDING AS?

RICHARD STUART GODFREY is the largest registered owner, with 100.0%.

What is the revenue of GNIST HOLDING AS?

GNIST HOLDING AS had revenue of NOK 649,000 in 2024.

Who is the general manager of GNIST HOLDING AS?

Richard Stuart Godfrey is registered as general manager of GNIST HOLDING AS.

Where is GNIST HOLDING AS based?

GNIST HOLDING AS has its business address in Hjellestad.

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.