BIZTRAC BETA
Business and other management consultancy activities

GUSTEN INVEST AS

Org. no. 993407054 Limited company (AS) Bergen Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 4.4m
Operating profit NOK 2.3m
Equity NOK 2.0m
Incorporated 2008
Share capital NOK 100,000

GUSTEN INVEST AS is registered as a limited company in Bergen, Vestland with organisation number 993407054. 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 100,000, divided into 100 shares. The company's stated purpose is: “Konsulentvirksomhet innen forretningsdrift samt investeringer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.4m in revenue and NOK 2.3m in operating profit.

Key figures · 2025

Revenue
NOK 4.4m
Operating profit
NOK 2.3m
Equity
NOK 2.0m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns GUSTEN INVEST AS?

FABIAN EMIL STANG
GUSTEN INVEST AS
NOK 4.4m rev. · NOK 2.3m profit

GUSTEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GUSTEN INVEST AS own?

GUSTEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GUSTEN INVEST AS

Who owns GUSTEN INVEST AS?

FABIAN EMIL STANG is the largest registered owner, with 100.0%.

What is the revenue of GUSTEN INVEST AS?

GUSTEN INVEST AS had revenue of NOK 4.4m in 2025.

Who is the general manager of GUSTEN INVEST AS?

Fabian Emil Stang is registered as general manager of GUSTEN INVEST AS.

Where is GUSTEN INVEST AS based?

GUSTEN INVEST AS has its business address in Bergen.

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.