BIZTRAC BETA
Other captive investment companies

FBG INVEST AS

Org. no. 916688768 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −1.0m
Equity NOK 72.6m
Incorporated 2016
Share capital NOK 148,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,0 mill kr).

FBG INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 916688768. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 148,000, divided into 1000 shares. The company's stated purpose is: “Å foreta/forvalte investeringer i verdipapirer, handels- og industrivirksomhet, tjenesteytende virksomhet, fast eiendom samt hva hermed står i forbindelse, herunder å delta i selskaper med lignende eller annen virksomhet, enten direkte eller via datterselskap, gjennom eierskap, lån, garantistillelser eller annen måte.”.

Key figures · 2024

Operating profit
NOK −1.0m
Equity
NOK 72.6m
Est. value
NOK 54.6m

Financial health · 2024

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

Who owns FBG INVEST AS?

FRODE BØE GULLIKSEN
FBG INVEST AS
· NOK −1.0m profit

FBG INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FBG INVEST AS own?

FBG INVEST AS holds stakes in 10 companies:

See the full ownership structure →

Frequently asked questions about FBG INVEST AS

Who owns FBG INVEST AS?

FRODE BØE GULLIKSEN is the largest registered owner, with 100.0%.

Who is the general manager of FBG INVEST AS?

Frode Bøe Gulliksen is registered as general manager of FBG INVEST AS.

Where is FBG INVEST AS based?

FBG INVEST AS has its business address in Hundvåg.

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.